Systems maintenance & support

Software needs looking after once it is live: fixes, security updates, small improvements, backups, hosting and someone to call when something breaks. We provide all of it under a service level agreement. Many of our clients come to us with a system another vendor built and left behind; we take it over, stabilise it and keep it running. It is the same work we do every day to keep Mittr running.

For example
  • Support after launch
  • Rescuing an abandoned system
  • Changing vendors
  • Hosting for systems we build
  • Older systems

When something breaks

Problems happen to every system. What matters is how quickly they are noticed, how well they are fixed, and whether you are told.

  1. Alert raised automatically

    Our monitoring spots the problem, often before your users do.

  2. An engineer responds

    Within the response time set in your service agreement.

  3. Fixed and verified

    The cause is fixed, not just the symptom, and checked in live use.

  4. Report sent to you

    What happened, why, and what we changed so it does not happen again.

Inherited a system?

Your previous developer moved on and nobody knows how it works. We take it over in three steps.

  1. Fragile
    Step 1AuditWe review the code, hosting and data, and tell you plainly what we find.
  2. Stable
    Step 2StabiliseFix what is breaking, secure it, back it up and document it.
  3. Healthy
    Step 3MaintainOngoing fixes and improvements under a written agreement.

Free bug fixes for at least three months after every launch we deliver, or longer where your contract requires.

What you get

  • Free bug fixes for at least three months after launch
  • Bug fixes, small changes and improvements
  • Security patches and updates
  • Monitoring, alerts and monthly reports
  • Hosting, backups and a tested recovery plan
  • Incident response with written reports
  • Audits and takeover of systems built by others

How we work

01

Response times in writing

Response and fix times are set by severity in the agreement, and we report against them every month.

02

Every incident is written up

After an outage you get a short report: what happened, why, and what we changed so it does not happen again.

03

Careful takeovers

When we take over a system we audit it first, fix what is fragile, and document what we find before making changes.

Typical technology

  • Uptime monitoring
  • Automated backups
  • Status pages
  • Ticketing
  • Runbooks
  • Cloudflare

Related work

In-house productIn service

Mittr: webhook delivery infrastructure

A multi-tenant platform that persists, signs, retries and accounts for every webhook a business sends, so integrations never fail silently.

  • Go
  • PostgreSQL
  • REST API

Have a project in mind?

Send us your brief, terms of reference or RFP. We reply within one business day.