You’re in good company

A few of the companies we’ve worked with.

Software ages, even when nobody touches it

The code stays the same, but everything around it moves. The packages it uses publish fixes. Its framework and runtime reach the end of their support, when their makers stop releasing fixes for them. Browsers and providers change how they work, and certificates expire. The people who know it best move on. Each skipped update makes the next one bigger, until updating becomes a project of its own and every change feels risky.

What we look after

The routine work that keeps software healthy, done on a regular rhythm by people who know your system.

Kept current

  • Regular updates

    Packages, frameworks and runtimes updated in small steps, each one tested before it’s released.

  • Security fixes first

    Security advisories checked as they’re published, with flaws attackers are known to use fixed first.

  • Upgrades planned ahead

    Each part’s end of support tracked, with its upgrade planned well before the date.

Kept working

  • Monitoring and alerts

    Errors, slowdowns and failed jobs watched, with alerts that reach a person who can act.

  • Fixes by priority

    Problems your team or your users report, fixed in order of impact, within an agreed response time.

  • Small improvements

    The changes your team asks for, planned in alongside the routine work, so the software keeps up with the business.

Kept on record

  • Renewals tracked

    Certificates, domains and the services your software depends on, tracked so each is renewed before it lapses.

  • Documentation kept current

    How to run, release and recover your system, written down and updated as it changes.

  • A regular report

    What changed, what’s due next and what we’d recommend, in plain words.

Small updates, planned upgrades

Most updates are meant to be small: fixes and features that shouldn’t change how your software works. Major versions are different, because they can remove or change what your code relies on, so each one is planned and tested on its own. Runtimes and frameworks publish when each version stops receiving security fixes, so an upgrade can be planned months ahead instead of rushed at the end.

Renewals come round faster now

The certificates that secure connections to your website are being given shorter lives. In 2025, browsers and certificate authorities agreed to cut the longest a public certificate can last: 200 days from March 15, 2026, 100 days from March 15, 2027 and 47 days from March 15, 2029. Renewing by hand stops being practical, so we automate renewals and check that they work.

When something goes wrong

You report it once, through the channel we agree. We confirm we have it, agree its priority with you and keep you updated until it’s fixed. After anything serious, we write a short review: what happened, why, and what will change so it doesn’t happen the same way again. It looks for causes, not someone to blame.

An urgent problem, and no agreement with us yet? Urgent help →

Choose an example report

Priorities
PriorityWhat it means
CriticalThe service is down, or data is at risk.
HighAn important feature is broken, with no workaround.
NormalSomething isn’t working as it should, but there’s a workaround.
RequestA change or a question.

First response times for each priority are agreed in your support plan.

{{ priSay }}

Taking over from another team

Software often reaches us after the people who built it have moved on. We start with a review: how it’s hosted and released, what’s out of date, how it’s monitored and backed up, and what’s written down. We also check who owns each account it depends on. Your domain, hosting, code and app store accounts should belong to your company, not to one person or a former supplier.

Start with a health check

We look at your system the way we’d look after it: what it runs on, what’s out of date or close to the end of its support, how it’s monitored, backed up and released, and who has access. You get a short report ranked by risk and a support plan with response times that suit your business, and the most urgent items are fixed first.

Support can stand on its own, or sit alongside a team building with you. Compare engagement models →

Questions worth asking

Can you look after software you didn’t build?

Yes. We start with a health check, so we know what we’re taking on before we agree response times.

What response times do you offer?

They depend on the priority. We agree a first response time for each one in your support plan, once the health check shows what your system needs.

Is hosting included?

Hosting and the platform beneath your software are a service of their own. Cloud, DevOps & Security →

What if part of our software is too old to update?

Then updating it is a project of its own. We’ll say so, and plan it with you. Legacy Modernization →

Can our own developers stay involved?

Yes. We work in your repositories and tools, and keep the documentation where your team can use it.

Do you use AI to maintain software?

For routine work, such as proposing updates, explaining unfamiliar code and drafting tests. A person reviews every change before it’s released.

What happens if we end the agreement?

You keep everything: the code, the documentation and the accounts. We hand over with notes, so the next team can carry on.

We have an urgent problem and no agreement. Can you help?

Tell us what’s happening. Urgent help →

Let’s run it better

Tell us what you run and how it’s looked after today. We’ll suggest a sensible first step.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}