An uptime line with release markers, and an incident that gets resolved.

Software needs care after launch: dependencies age, traffic changes and users ask for things. On a monthly plan we monitor the product, fix what breaks, keep it patched and ship small improvements. If your own team prefers to take it on, we hand over with documentation instead.

A good fit if

  • There's no developer on staff after launch.
  • The stack is on or near an end-of-life version.
  • Dependency update alerts pile up and nobody merges them.
  • Customers expect it to be up, and you'd hear about an outage from them first.

Not the right start if

  • You have a capable in-house team with its own on-call. You may only need an audit.
  • The product is about to be replaced. Start with Legacy Modernization
  • It's a low-traffic internal tool. You may not need a plan. We'll say so on the call.

What counts as urgent

Severity comes from two questions: how many people are affected, and is there a workaround? Pick a cell to see what happens next.

No workaround Partial workaround Workaround exists
Everyone
Some users
One user

S1: Checkout is down for everyone. Who's told: you and the on-duty engineer, at once. Response target: agreed per severity in your support charter.

Every case

Everyone, no workaround
S1: Checkout is down for everyone. Who's told: you and the on-duty engineer, at once. Response target: agreed per severity in your support charter.
Everyone, partial workaround
S2: Payments work, but receipts don't send. Who's told: you and the on-duty engineer, at once. Response target: agreed per severity in your support charter.
Everyone, workaround exists
S3: Search is slow, but the menu works. Who's told: you, in the daily update. Response target: agreed per severity in your support charter.
Some users, no workaround
S2: Login fails for one company's single sign-on. Who's told: you and the on-duty engineer, at once. Response target: agreed per severity in your support charter.
Some users, partial workaround
S3: Exports time out for large accounts; smaller ones work. Who's told: you, in the daily update. Response target: agreed per severity in your support charter.
Some users, workaround exists
S4: A report column is misaligned in one browser. Who's told: the monthly report. Response target: agreed per severity in your support charter.
One user, no workaround
S3: One customer can't open their invoices. Who's told: you, in the daily update. Response target: agreed per severity in your support charter.
One user, partial workaround
S4: One user's avatar won't upload. Who's told: the monthly report. Response target: agreed per severity in your support charter.
One user, workaround exists
S4: A typo on a settings page. Who's told: the monthly report. Response target: agreed per severity in your support charter.

How it runs

  1. 01 of 08

    Onboarding audit.

    Access, dependencies, end-of-life dates, alerts and a test restore from backup.

    You keep A health report and a risk list.

  2. 02 of 08

    Agree the rules.

    What each severity means, who to contact, response targets and who may change what.

    You keep A one-page support charter.

  3. 03 of 08

    Watch it.

    Uptime, errors, speed, certificate and domain expiry, and backup checks.

    You keep The alert list and dashboards.

  4. 04 of 08

    Keep it current.

    Grouped dependency updates each week, held back a few days after release, with known-exploited flaws fixed first.

    You keep The update settings and an upgrade log.

  5. 05 of 08

    Fix and respond.

    Problems triaged by severity, with a postmortem for the serious ones.

    You keep An incident log and postmortems.

  6. 06 of 08

    Improve.

    Small changes from a list you rank.

    You keep A changelog.

  7. 07 of 08

    Report monthly.

    Uptime, incidents, updates, open risks, hours used and next month's plan.

    You keep A report you can forward.

  8. 08 of 08

    Hand over, when you're ready.

    Pairing, documentation and our credentials removed.

    You keep A handover pack.

Software ages even when nobody touches it

  1. Known flaws, exploited fast.

    Attackers move on published vulnerabilities within days.

    Prevented in step 4
  2. Versions that expire on a date.

    Node.js 20 reached end of life on 30 April 2026, and PostgreSQL 14 on 12 November 2026.

    Prevented in step 1
  3. Poisoned updates.

    In September 2025 a worm spread through 187 npm packages, so we hold new releases back a few days before merging.

    Prevented in step 4

28.96%

Share of exploited vulnerabilities that were attacked on or before the day they were published.

VulnCheck, 2026Checked Nov 2026

31%

Share of breaches that started with an exploited vulnerability, now the most common way in.

Verizon DBIR, 2026Checked Nov 2026

What you keep

  • Monitoring and alerts

    Uptime, errors and speed monitored, with alerts set up for the issues that matter to you.

  • Bug fixes

    Problems triaged and fixed in order of impact.

  • Updates and patches

    Frameworks, libraries and servers kept current and secure.

  • Monthly report

    What we did, what broke and what we recommend next.

Done means

  • Nothing runs past its end-of-life date.
  • No known-exploited vulnerability is left open.
  • Alerts are routed to a person, and tested.
  • A backup was actually restored this month.
  • Serious incidents have a postmortem.
  • You have a report you can forward to your board.

Sample

Monthly report

Uptime99.97%, target 99.9%
Incidents1 × S2 (receipts delayed 40 min), postmortem done
Updates23 dependencies updated, 2 high-severity fixes
WatchlistNode.js 22 reaches end of life in April 2027
Backup restore testPassed, 18 minutes
Next monthUpgrade the database, then the search index
Illustrative values, not a client result.

Questions about Support & Maintenance

Still deciding?

Ask the people who would build it. We reply within one business day.

After launch we monitor the product, fix what breaks and improve it, on a monthly support plan. If your own team takes it on instead, we hand over with documentation.

Then the hours go to updates and small improvements. Keeping it current is the work, because software ages even when nobody changes it.

Often, after a short audit. We need to understand the code before we promise to keep it running, and we'll tell you if the audit finds something that has to be fixed first.

You own every account. We get named, limited access that you can remove in one step, and every change goes through your pipeline.

Only if an hour of downtime at night costs you more than the cover would. We'll help you work out which it is.

Yes. Code, designs, prompts and infrastructure are yours from the first commit, so nothing needs handing back and another team can pick it up.

Have an idea or a stuck project? Let's talk.

We reply within one business day. If we're not the right team, we'll say so on the first call.

On the first call

  • What's live, who built it and where it's hosted.
  • What broke recently.
  • What would count as urgent for you.