Software is not a building; it is a garden. Left alone, dependencies go stale, certificates expire, disks fill and small issues compound quietly until something breaks at the worst possible moment.
What a support plan covers
- Security — framework and library patches applied promptly, not annually.
- Reliability — uptime monitoring, error tracking and alerts that reach us before your customers notice.
- Backups — automated, off-site, and periodically restore-tested. A backup you have never restored is a hope, not a backup.
- Fixes — defined response and resolution times by severity, agreed in writing.
- Improvements — a monthly allocation of hours for the small changes that keep the product moving.
- Reporting — a plain-language monthly summary: what happened, what we changed, what needs a decision from you.
Also for software we did not build
Inherited a project from another vendor? We start with an audit — code quality, security posture, dependency age, backup status — and give you an honest assessment before you commit to anything. Sometimes that assessment is "this is fine, here is the plan". Sometimes it is not. Either way, you get the truth in writing.
What You Get
- Security patches and dependency updates
- Bug fixes with an agreed response SLA
- Automated backups, verified by restore tests
- Uptime and performance monitoring with alerts
- Small feature improvements each cycle
- Monthly health report in plain language
Technologies We Use
Frequently Asked Questions
What does a maintenance plan include?
Security patches, dependency updates, backups, uptime monitoring, bug fixes and a set number of small change requests each month.
Can you maintain software someone else built?
Yes. We start with a code audit, tell you honestly what shape it is in, and then take over maintenance.