Software maintenance and support that keeps what is already live healthy
Centricone Technologies takes on running systems — including ones we did not build. Monitoring, patching, dependency upgrades, bug fixes, and an escalation path with a named engineer, so the software your business depends on stops being a risk nobody owns.
Taking over someone else's codebase starts with an audit, not a promise. You get an honest read on what you have before either side signs anything.
support coverage across US and Canada time zones
of code reviewed, tested, and documented before release
The system is running and nobody is looking after it
The people who built it have gone
No documentation, no tests, and dependencies years out of date. Every change starts with an archaeology dig, so changes stop happening.
Security patches are behind
Frameworks and libraries have moved on, the upgrade keeps being deferred as too risky, and the gap grows in exactly one direction.
Outages are discovered by customers
Monitoring is thin or noisy, there is no on-call rota, and the first signal that something broke is a support ticket.
for systems that have to keep working
Centricone covers the whole of keeping software alive: monitoring and response, patching and upgrades, small changes, and the documentation that should have existed.
Deliverables
What you get
- A written audit of the system as it is today
- Monitoring and alerting you can see
- A named engineer and a documented escalation path
- A patching and upgrade schedule
- Runbooks and architecture documentation
- A monthly report of what changed and what is at risk
How a support engagement starts
Audit
A short, paid-for-by-us read of the code, infrastructure, and deployment path, ending in a written risk list.
Stabilize
Backups, secrets, monitoring, and the most exposed dependencies — the work that reduces risk fastest.
Agree the shape of the cover
Hours, response times, on-call expectations, and what counts as a change rather than a project. Written down before it starts.
Run it
Patching on schedule, changes each month, and a report you can hold us to.
When maintenance is the wrong engagement
Sometimes keeping a system alive is the expensive option, and we will tell you when we think that is the case.
- The system no longer matches how the business works — you are paying to preserve the wrong thing.
- The platform or framework is past end of life with no upgrade path. That is modernization, staged, not maintenance.
- You need feature delivery at pace. A support agreement is sized for change at the margin, not for a roadmap.
- The real need is capacity inside your own team — that is staff augmentation.
Why teams hand systems to Centricone
An audit and an honest read before any agreement
A named engineer, not a shared ticket queue
Documentation written as we learn the system
24/7 production cover across US and Canada time zones
Frequently asked questions
Not sure this is the right shape? Tell us the situation and we’ll say which engagement fits.