Who can maintain a custom business app in the UK, and what should a retainer include?
A maintenance retainer should cover monitoring, security updates, fixes and small changes from a named team, and the NCSC's own timescales for updates give you a number to hold it to.

A maintenance retainer for a custom business app should cover four things: monitoring, security updates, bug fixes and small changes, all done by a named team that already knows your code. The UK's National Cyber Security Centre sets the benchmark for the second of those: apply updates within 5 days for internet-facing software and 7 days for operating systems and applications. Whoever you ask to look after your app, ask them to put those four things and a response time in writing, and ask who has access to your hosting.
What does "maintenance" actually mean for a custom app?
Maintenance is the ongoing work that keeps an app that already works from breaking: watching it, patching it, fixing what goes wrong and making small changes as the business moves. An app doesn't stand still once it is live, because the libraries it is built on publish security fixes, the hosting provider retires old versions, and the payment or accounting service it connects to changes how it behaves. If nobody is assigned to that work, it still happens, just on the day something fails in front of a customer.
What should a retainer include?
A retainer should include the following, and each item should be written down so you can check it was done:
| Item | What it means in plain words | What to ask for |
|---|---|---|
| Monitoring | Someone is alerted when the app is down, slow or throwing errors, before a customer tells you | Who is alerted, and how quickly someone looks |
| Security updates | The software your app is built on is kept current | A stated timescale, for example the NCSC's 5 and 7 days |
| Fixes | Faults in the app are corrected | A response time for urgent faults, and who decides what is urgent |
| Small changes | Short pieces of work such as a new field, a changed email or a report | How many are included, and how bigger changes are quoted |
| Backups | A copy of your data exists and has been restored at least once to prove it works | When the last restore test happened |
| A named team | The people doing the work are the ones who know your app | Names or roles, and what happens when one is away |
How quickly should security updates be applied?
The NCSC's guidance says security updates should be applied as soon as possible, and it gives timescales: 5 days for internet-facing services and software, 7 days for operating systems and applications, and 14 days for internal services. It says these timescales apply to all updates regardless of the vulnerability's severity, and that when a vulnerability is being actively exploited they are too long and the process must be faster. A customer portal on the public internet falls in the 5 day group. If a quote promises "regular updates" without a number, ask what the number is.
Do the UK data protection rules say anything about this?
UK data protection law does not set a number of days for applying updates, but the Information Commissioner's Office says the UK GDPR requires a level of security that is "appropriate" to the risks presented by your processing, and that you need a process for regularly testing, assessing and evaluating the effectiveness of your measures. Its guidance says the UK GDPR now makes that testing an obligation for all organisations. If your app holds customer records, a retainer that includes regular checks is part of showing you took that seriously. The ICO has said the guidance is under review following the Data (Use and Access) Act 2025, so check its page for the current wording.
Who can look after an app someone else built?
Several kinds of provider can, and the difference is how much they know about your code on day one. The original developer knows it best, and is the natural first call if they are still available and still work on this kind of thing. An agency or software company will usually want to read the code before agreeing to look after it, so expect a review first and a price afterwards. An in-house hire gives you someone who is always there, but one person is one point of failure, and they will need time to learn code they did not write.
If the original developer has gone, our piece on who can take over an app when the developer has left goes through the handover.
What does Run from We UC cover?
Run is our maintenance offer: monitoring, security updates, fixes and small changes from a named team, on a monthly retainer. It is for software we built or rescued, so a normal route in is a Rescue audit, where we read your code and hosting, change nothing and give you a written report and a priced plan, followed by the fix. We don't publish a Run price, because it depends on what the app does and what it connects to, so you ask and we quote.
We UC is a UK software company with its main engineering team in Southampton and some engineers offshore in Ukraine and Eastern Europe. We run Olatti, a UK business phone network, and Quenta, an app that posts receipts into Xero, in production ourselves, and the team that does that is the team that looks after client software. An engineer reviews every change before it ships and two QA engineers test the work.
What should I check before signing a retainer?
Check these five things, and treat a missing written answer as a no:
- Do you hold the code, the repository and the hosting accounts in your own name?
- Is there a stated timescale for security updates, and a response time for urgent faults?
- How are changes bigger than the included small ones scoped and priced?
- When was the last backup restored as a test, and who did it?
- Can you leave, and what do you get when you do?
Common questions
Is a maintenance retainer worth it for a small app?
It is worth it once the app holds customer data or takes money, since the updates and monitoring then protect something. For an internal tool with a handful of users and nothing sensitive, ad hoc fixes from whoever built it may be enough.
Can you maintain an app built with Lovable, Bolt, Cursor or Replit?
Yes, for apps we have audited or rescued, which is how we start with software we didn't write. You got an app working and in front of real users, which is further than most ideas get, and the audit tells us what needs fixing before we take it on.
What does it cost?
We don't publish a price for Run. The Rescue audit that usually comes first is £2,500 + VAT, fixed, and it is deducted from the first phase if you go ahead with us on the fix.
Do I own the code?
You should, and you should have it in writing. Our approach is that your code, your repository and your accounts are yours to keep.
If you have an app that real customers depend on and nobody currently looking after it, you can book a Rescue audit, or ask us about Run.