Maintenance & Support

Long-term ownership after launch. Security updates, monitoring, dependency upgrades, and the steady work that keeps a product worth using.

Software does not sit still after launch. Dependencies age out of support, a payment provider changes an API, traffic grows past what the original design assumed, and the person who understood the deployment leaves. The products that stay healthy are the ones where somebody is responsible for all of that between releases, not only when something breaks.

What we build

Security and dependency updates

Keeping the stack patched and current, in small regular increments rather than one frightening upgrade every second year.

Monitoring and uptime

Error tracking, performance monitoring, and alerts that reach a person, so problems surface before support tickets do.

Bug triage

A route for reporting problems, a rule for what gets fixed now, and a queue for what does not.

Ongoing feature work

Scheduled capacity for the changes the product needs after real people have used it for a year.

Backups and recovery

Backups that are tested by restoring them, because an untested backup is an assumption.

Taking over someone else's code

Reading, documenting, and stabilising a codebase we did not write, before changing anything in it.

What you get

  • A named response time for issues, agreed before we start
  • Monitoring and alerting on your accounts, not ours
  • A tested restore, not just a backup job that reports success
  • Documentation good enough for another team to take over

We build this for ourselves too

We operate our own products in production rather than shipping them and moving on. GetFade, RankMetrics and LawManager are all live, all maintained by us, and all subject to the same upgrades and monitoring we set up for clients.

Common questions

Will you maintain software you did not build?

Yes, and it starts with a review rather than a fix. We read the codebase, the schema, and the deployment setup, then give you a written assessment of what is safe to change and what needs work first.

How is it billed?

A monthly retainer sized to the product, covering a set amount of capacity. Emergency work outside that is agreed case by case rather than billed by surprise.

What if we want to bring it in-house later?

Then the handover should be easy, which is why the documentation and the infrastructure are yours from the start. We would rather hand over cleanly than be difficult to replace.

Other services

Let's talk about your maintenance & support project.

info@an2tech.com