Ongoing maintenance, updates, and support for existing applications. We treat software like an asset that needs care — patched, monitored, and improved long after the original launch party.
What's Included
Each maintenance plan is tailored — these are the core capabilities every engagement starts from
Proactive Monitoring
Uptime, performance, and error monitoring with alerts that go to a real person, not a forgotten inbox.
Security Patching
Regular dependency updates, CVE triage, and timely patches for the libraries your application depends on.
Performance Tuning
Quarterly reviews of slow queries, render bottlenecks, and bundle sizes — small fixes that compound.
Backups & Recovery
Automated backups with documented restore procedures, tested often enough to actually trust them.
Incident Response
Defined response SLAs, on-call channels, and post-incident reviews so you never relive the same outage twice.
Continuous Improvement
A monthly retained budget for small features and refactors, so technical debt does not quietly compound.
How We Engage
A clear path from "we inherited this codebase" to "we sleep well at night"
Codebase Audit
We map the application, dependencies, infrastructure, and known issues — and flag the urgent ones immediately.
Plan & SLA
We agree on monthly hours, response times, escalation paths, and the things that are explicitly out of scope.
Onboarding
Monitoring, logging, alerting, and CI/CD are stood up or improved so we are not flying blind.
Routine Maintenance
Scheduled patching, dependency updates, backups, and platform housekeeping happen on a predictable cadence.
Incident Handling
Bugs and outages are triaged against agreed severity levels, with status updates and post-mortems as standard.
Reporting & Reviews
Monthly reports on uptime, work done, and recommended next steps — so leadership stays close to the system.
Support Toolkit
The tools we lean on to keep production calm
Monitoring
- Sentry
- Datadog
- New Relic
- Grafana
- Prometheus
- UptimeRobot
Incident Management
- PagerDuty
- Opsgenie
- Statuspage
- Linear
- Jira
- Slack
CI/CD & Patching
- GitHub Actions
- GitLab CI
- Dependabot
- Renovate
- Snyk
- Trivy
Backups & Recovery
- AWS Backup
- Velero
- Restic
- BorgBackup
- pg_dump
- Snapshot Lifecycle
Frequently Asked Questions
Do you support applications you did not build?
Yes — we frequently inherit codebases. The first month is usually an audit and stabilisation phase, after which we settle into a regular support cadence with you.
What response times can we expect?
We define severity levels at the start of the engagement. Critical production incidents typically get a response within an hour during business hours, with after-hours coverage available on request.
How is the work scoped each month?
Each plan includes a budget of hours covering monitoring, patching, and a defined amount of feature or fix work. Larger pieces of work are scoped separately so there are no surprises.
Can we scale support up or down over time?
Yes. Most clients start at a baseline plan and adjust quarterly based on the work the system actually needs. We are happy to scale back when things are stable.
What about handover if we want to move support in-house?
We document everything we touch and run knowledge-transfer sessions with your engineers when you are ready. The goal is for support to be portable, not sticky.
Whether you need a watchful eye on production or a full support partner, we can shape a plan that fits the risk and the budget.
No commitment required — start with a free audit