The problem
Sites do not fail loudly. A certificate expires, a dependency gets a CVE, a backup has silently been writing zero bytes for four months. You find out from a customer.
How we approach it
- 01
Monitoring that pages a human
Uptime and error rate checks that alert us, not a dashboard nobody opens.
- 02
Backups that are restored
A backup nobody has restored is a hope. We test a restore on a schedule and tell you the result.
- 03
No hostage taking
Month to month, and your code and hosting stay in your name. Leaving should be easy, which is why most clients stay.
Common questions
- Is it required?
- No. One month of support is included with every build and plenty of clients handle it themselves after that.
- What counts as a content change?
- Text edits, image swaps, adding a team member, changing opening hours. Anything under about thirty minutes.
- Can you maintain a site you did not build?
- Usually yes, after a short audit so we know what we are taking on.