Skip to content

7 coverage areas

We don't disappear after deployment.

Software needs maintenance. Dependencies change, infrastructure evolves, traffic grows and businesses change. We can stay involved after launch — and if you would rather take it in-house, the handover is part of the deal.

What is covered.

Security updates
Patches applied when they are published, not when something breaks.
Dependency updates
Framework and library upgrades on a schedule, before versions go end-of-life.
Performance monitoring
Uptime, response times and error rates watched, with alerts that reach a person.
Bug fixes
Reported issues triaged by severity and fixed, with a note on the cause.
Feature improvements
A continuing budget for the changes your team asks for after launch.
Backups
Automated backups with a restore that has actually been tested.
Infrastructure support
Hosting, domains, certificates, scaling and cost review.

Three levels of involvement.

Priced monthly against the size and criticality of the system. We quote after seeing what is running, not before.

Essential care

Sites and small applications in steady service

Coverage

4/7

  • Security patches
  • Dependency updates
  • Uptime monitoring
  • Backups and restore test
Response2 business days

Active maintenance

Business-critical software with regular change

Coverage

6/7

  • Everything in Essential care
  • Bug fixes by severity
  • Performance review
  • Monthly report
Response1 business day

Continuous improvement

Products that keep evolving after launch

Coverage

7/7

  • Everything in Active maintenance
  • Monthly development budget
  • Roadmap and planning
  • Infrastructure ownership
ResponseSame business day

[ Support is optional and cancellable. You own the repository, the deployment configuration and the documentation regardless. ]

Questions

Answers before you ask.

Something not covered here? Ask directly — we answer scoping questions before there is any commitment.

Yes. We start with a short review of the code, dependencies, infrastructure and the risks we can see, then agree what to fix, what to leave and what to rebuild. We will tell you plainly if a rewrite is the wrong call — usually it is.

HAVE A PROBLEM WORTH SOLVING?

Tell us what you're trying to build, improve, or automate. We'll help turn it into a practical technology solution.

No sales pressure. Just a conversation about your project.