Hosting and ongoing support
Running what we build, or what someone else built, with monitoring that tells us before it tells you.
A site is not finished when it launches. This is the part afterwards: keeping it up, keeping it patched, and being reachable when something goes wrong.
What the work covers
- Managed hosting on Cloudflare or AWS, billed at cost plus a flat fee rather than marked up
- Uptime and error monitoring, with alerts that reach a person
- Dependency and security updates
- Backups, and restores that are actually tested
- Incident response, with a written note afterwards explaining what happened
What we build it with
- Cloudflare Pages, Workers, R2
- AWS
- Uptime and error monitoring, with alerting into email or Slack
How an engagement runs
- 01
Take it over
We audit what we are inheriting first and tell you what we find, including anything we are not willing to be responsible for.
- 02
Instrument it
Monitoring and alerting before anything else, so problems surface from us rather than from your customers.
- 03
Keep it current
Updates applied on a schedule, not when something breaks.
- 04
Answer when it matters
Business hours by default. Out of hours by arrangement, and we will be honest about what we can commit to.
What we don't do
- 24/7 on-call. We are small and promising it would be a lie.
- Managing hosting we have no access to change
- Support for software we did not build and cannot read the source of