Service · Ongoing Support
We don’t disappear after launch.
Keep your software fast, secure, and growing with the people who built it. Same engineer. Same codebase. Not a support ticket queue. Not a stranger reading someone else’s code.
From £500/mo
What’s covered
After ship isn’t the end — it’s the beginning.
Software that isn’t maintained degrades. Dependencies fall behind, CVEs accumulate, performance slips. The retainer keeps it from quietly becoming a liability.
Uptime monitoring and incident response
Something goes down, we know before you do. We triage, fix, and tell you what happened and why — not the other way around.
Security patches
CVEs don't wait for a convenient moment. We monitor, apply patches, and keep the dependency tree healthy — without you having to ask.
Dependency updates
Framework updates, breaking changes, deprecated APIs. Kept up to date on a rolling schedule — not left until a vendor forces a painful upgrade.
Automatic backups
Database backups verified monthly against a real restore test. You know the backup works before you need it.
Small features and improvements
A budget of engineer-days each month for new work. A new integration, a workflow change, a form that needs to do something different. Scoped, shipped, in the changelog.
Priority response
One hour acknowledgement on business hours. Critical incidents — site down, data integrity risk — handled outside hours. One point of contact, not a ticket queue.
Vendor API changes
A third-party API changes their auth flow or deprecates an endpoint. We handle it before it reaches your customers — and before it breaks at the worst possible time.
Content and copy updates
New team member, updated pricing, a page that needs rewriting. Changes that should take minutes get done in minutes.
How the retainer works
Simple terms. No surprises.
Scope is agreed in writing at the start. You know exactly what’s covered, exactly what isn’t, and who’s doing the work. Cancel any time — one month’s notice, code stays yours.
- SCOPEAgreed in writing at the start — no surprises mid-month
- ENGINEERSame person who built it, or a Canarlo engineer who reviewed it first
- RESPONSEOne hour acknowledgement business hours · critical out-of-hours
- COMMITMENTMonth-to-month · one month's notice · cancel any time
- OWNERSHIPYour code · your cloud · no lock-in on either side
- PRICEFrom £500/mo · scaled to scope
Software that stays working is software that keeps earning.
Questions
What clients ask before they sign.
Does the retainer only cover software Canarlo built?
We prefer to take on systems we built — we know the codebase, the data model, and where the edge cases are. We do take on external codebases, but we start with a structured review first: architecture, security posture, dependency health, test coverage. That review tells us both what needs attention and whether it's a good fit.
What's included in the monthly retainer?
Uptime monitoring and incident response, security patch application and dependency updates, automatic backups verified monthly, a budget of engineer-days for small features and improvements, and priority response when something goes wrong. The exact scope is agreed in writing at the start — no surprises mid-month.
What's not included?
Large new features, architectural changes, or scope that requires a proper discovery and build phase. When work is beyond the retainer scope, we say so clearly and scope it separately — not silently eat the hours.
Can I cancel any time?
Yes. One month's notice. The code is yours whether or not we continue — no proprietary runtime, no Canarlo lock-in. If you want to take it in-house or move to another team, the handover doc is already there.
Who does the work?
The same engineer who built the system, or a Canarlo engineer who has reviewed the codebase before a single change is made. Not a rotating support queue. You get one point of contact who knows the code.
How quickly do you respond to incidents?
Priority response means we're aware of production incidents before you are — the monitoring fires before a customer notices. Target acknowledgement within one hour during business hours. For critical incidents (site down, data integrity risk) we respond outside business hours.
After launch
One call, honest answer.
Tell us about your stack and what’s keeping you up at night. Every Canarlo build can transition into a support retainer — or we can review an existing codebase and tell you honestly if it’s a good fit.