Maintenance and support plans
After launch, a monthly plan keeps the site, app and automations I built for you working: hosting, dependency and security updates, monitoring, and small changes when you need them. Plans cover only projects I built myself, so I know every part of what I look after. Every project already includes a support window after launch; the plan is for what comes after. Plans are quoted per project, based on what there is to look after.
What you get
- Hosting and domain looked after in your own accounts
- Dependency and security updates
- Uptime and error monitoring, with alerts to me
- Automation logs checked and failures fixed
- Small content and design changes
- A short monthly note on what was done
See it in practice:Krunchy’s over-the-air updates and remote switches
Who it is for
Small businesses whose website, app or automations I built, and who want them to keep working without thinking about updates, expired keys or a provider that changed its API.
What a plan covers
The sites, apps and automations I built. I don’t take over the upkeep of existing systems that someone else built.
Why it matters
Software that isn’t maintained breaks quietly: an AI model is retired, a service changes its API, a certificate expires. When a provider retired its model in August 2026, Krunchy’s imports stopped until it was switched. Now the model is a setting that changes without a release. A maintenance plan is how problems like that get caught early.
How it works
- At handover. We agree what the plan covers and how fast I respond.
- Every month. Updates, monitoring and the small changes you ask for.
- When something breaks. I fix it and tell you what happened.