Live systems need someone who answers.
Care plans for the software we build, the applications we rescue, and the systems you already run. Monitoring, updates, fixes and a monthly review, from the person who knows how it works.
The quiet work that keeps incidents small.
Most incidents start as something small nobody was watching. A care plan is someone watching.
- Monitoring and alerting, set up so failures reach a person before they reach your users
- Platform updates and vendor releases tested before they reach Production
- Small fixes included every month, without a new quote each time
- A monthly review: what ran, what failed, what we changed and what's next
- Documentation and runbooks kept current as the system changes
- Every access we hold listed, so you can see it and revoke it
When something breaks, it follows the same path every time.
You always know who has it, what happens next and when you'll hear back.
Report
Email or your agreed channel. No ticket portal to learn.
Reply
Within one business day, usually sooner, with what we know and what happens next.
Fix
Through your release path: Development, then Test, then Production. Never hand-edited in Production.
Write it up
What happened, why, and what stops it happening again, added to your docs.
Pick the level of help you need.
Each one is scoped in writing and priced before it starts. Never open-ended hours.
- 01Care planMonitoring, updates, small fixes and a monthly review for the systems we agree on. Billed monthly, scoped to your systems.
- 02Fixes and features on requestLarger changes scoped and priced one at a time, and run through the same release path. Fixed price per request.
- 03Your team, our runbookYour team runs it with our documentation, and calls us when it wants a second pair of eyes. Included with every handover.
Before you sign up for support.
Last updated
Do you support systems you didn't build?
Yes, after an assessment. We only take on what we've looked at first, so the care plan is priced on what's actually there.
Do you offer after-hours coverage?
In some contracts, yes. When it's included, the hours, response times and contact path are written into the agreement. We won't promise coverage we can't keep.
What are the response times?
The default is a reply within one business day. Faster commitments for critical systems are agreed up front and written into your agreement.
What happens if we stop?
You get a handover pack: current documentation, the runbook and the list of every access we held, which we then close.