Maintenance and
support
Ongoing care for a product that is already live — updates, monitoring, fixes and small changes, with a response time written into the contract instead of promised verbally.
What support covers
Four areas. Everything is logged, so you can see where the hours went.
Security and updates
Dependency upgrades, framework versions and patches applied before they become an incident, not after a scanner finds them.
Monitoring and uptime
Error rates, latency and availability watched continuously, with alerts on what users feel rather than on CPU graphs.
Bug fixes
Defects triaged by impact and fixed within the agreed response time, with a root-cause note when something recurs.
Small changes
Copy, prices, new fields, a report, an integration tweak — the steady stream of requests that does not justify a project.
How support works
A named engineer, a written response time, and hours you can see.
Handover and access
We take over the repository, infrastructure and documentation, then run an audit to find what is already broken or out of date before agreeing the terms.
Agreed response time
Severity levels with a response time for each, written into the agreement. Critical means critical — not a ticket that waits for Monday.
Monthly rhythm
Planned update windows, a report of what was spent and on what, and a short list of what we recommend fixing next.
What we support
If your product runs on something else, ask — we will say honestly whether we can take it on.
AWSProduct live and
nobody watching it?
Tell us what you run and where it hurts. We will audit it first and quote support against what we actually find.
