Maintenance
Your site or app kept running, updated, and secure without you having to track every dependency yourself.
The problem
Most sites are handed off at launch and never touched again until something breaks — at which point the dependency tree is eighteen months out of date, a critical security patch has been available since June, and the build pipeline needs to be rebuilt before anything can be deployed.
The cost of that gap is not just the emergency fix — it is the week of archaeology before the fix can land.
How we get there
Onboarding audit
A baseline of what the codebase actually is: dependencies, security exposure, performance, and the things that will cause a problem before they do.
Scheduled maintenance
Dependency updates, security patches, and framework upgrades on a regular cadence — not when they become urgent.
Monitoring
Uptime, error rates, and performance regressions tracked — with alerts that reach us before they reach your users.
On-demand changes
Copy changes, content updates, and small feature additions handled without a separate project engagement.
Deliverables
- Onboarding audit and baseline report
- Monthly maintenance log
- Uptime and performance monitoring
- On-demand change handling
Stack
- Vercel
- Sentry
- Uptime Robot
- GitHub Actions
- Dependabot
Frequently asked
What is included in a maintenance retainer?
Security patches, dependency updates, uptime monitoring, and a monthly change budget. The scope is fixed per retainer tier — scoped honestly before you sign up.
Can you maintain a site you did not build?
Yes, after the onboarding audit. We need to understand what is there before we commit to keeping it running.
What if something breaks outside the retainer scope?
We triage it immediately regardless. The retainer covers the agreed scope — an emergency outside that is handled as a time-and-materials incident, not left unresolved.
