H
Ongoing care for software we built or inherited — proactive monitoring, dependency and security patching, and an on-call rotation with response times written into the contract rather than promised verbally.
These are the situations clients are usually in when they come to us for this work.
The person who built the system has left
Nobody notices an outage until a customer reports it
Dependencies are years out of date and now hold known vulnerabilities
Small changes wait months because there is no one to make them
Every engagement runs in these stages, with a decision point at the end of each — you are never locked into the whole thing up front.
Take on the codebase and infrastructure, document what exists, and flag urgent risks in the first weeks.
Alerting, uptime checks, and error tracking so problems are found by us rather than reported by your customers.
Scheduled patching, dependency upgrades, and security updates on a predictable cadence.
On-call rotation with response times defined in the contract, and a written post-incident review each time.
The things people usually want to know about this service, answered straight.
Yes. We start with an audit and handover period to learn the system before taking on response commitments.
Tiered by severity and written into the contract — typically one hour for critical incidents on a 24/7 plan. We do not promise response times verbally.
Support contracts run monthly with a three-month minimum, which is roughly what it takes to learn a system well enough to be useful on call.
Tell us what you are trying to build. We will come back with an honest view of scope, timeline, and cost — no obligation.