We are hiring across engineering, design and delivery.

See open roles

Looking after software somebody else built

Support, security patching, upgrades and small improvements for systems already running — including the ones with no documentation.

Software nobody wants to touch

Plenty of businesses depend on an application whose original developer is long gone. It works, mostly. Nobody wants to touch it, the framework is four versions behind, and every small change is quoted as a rewrite.

We take these on. The first month is spent understanding what is there and writing it down — which is usually the single most valuable thing anyone has done to the system in years. After that it becomes maintainable again, incrementally, without the rewrite.

What the work includes

What the work includes

Codebase audit

What it does, what it depends on, and where the genuine risks are. Written down.

Security patching

Dependency updates and framework upgrades applied in a planned way rather than after an incident.

Bug fixing

With agreed response times, and a root cause rather than another workaround.

Small enhancements

A monthly allowance of change, so the system keeps up with the business.

Monitoring and backups

Put in place if they are missing, which they often are.

Documentation as we go

Built up while we work, so the knowledge stops living in one person again.

Who this is for

If one of these sounds like your situation, it is worth a conversation.

A developer who has moved on

Nobody left who understands it, and it is running something important.

Known security debt

Unsupported versions, unpatched dependencies, and an audit coming.

Change quoted as rewrite

Every request comes back as "we should rebuild it". Sometimes true, usually not.

How we work

Engineering practice, stated plainly, so you can hold us to it.

You own the code

Your repository, your infrastructure, from the first commit. No hostage-taking, no licence to renegotiate.

Working software every fortnight

Something you can open and use, not a progress report. If a sprint produced nothing you can click, we say so.

Tests where they earn their keep

On the logic that would be expensive to get wrong. We do not chase a coverage number for its own sake.

Handover assumed from day one

Written so your team, or the next agency, can pick it up. That is a feature, not a risk to us.

Part of Technology

Part of Technology

Software that carries the business

Custom software, web and mobile applications, cloud platforms and the integrations that hold them together — built to be maintained, not just launched.

See all Technology services
What we commit to

What we commit to

  • A fixed price for a fixed scope, or a rate — never both at once
  • One named engineer who knows your system, not a rotating pool
  • Weekly written updates, including the weeks that went badly
  • Your data exportable in a documented format, always
  • No lock-in: no proprietary framework you can only maintain through us
How a build runs

How a build runs

Four stages. You can stop after any of them and still have something worth having.

Discovery

We map the process as it really is, agree what the software must do, and write down what it will not. You get the plan whether or not you build with us.

Design and architecture

Screens, data model, and the technical decisions that are expensive to reverse later. Reviewed with you before anyone writes code.

Build

Two-week cycles, each ending in something you can use on a staging environment. Priorities can change between cycles; scope inside one cannot.

Launch and support

Deployment, monitoring, and a support arrangement sized to what you actually need — which is usually less than you were quoted elsewhere.

Common questions

Yes, including undocumented ones. The first month is spent understanding what is there and writing it down, which is usually the most valuable thing anyone has done to it in years.

It is the common case. What matters is whether the code runs and the data is intact — from there it can be made maintainable again incrementally.

Rarely, and it is usually quoted because a rewrite is easier to price than understanding what exists. We will tell you honestly when it genuinely is the right call.

Is this the right fit?

Tell us what you are trying to do. If software maintenance is not the answer, we will say so.

Get in touch
Payment We Accept

© 2026 Myrris. All Rights Reserved.

Contact us