arveldon Say hello

Application modernisation and technical maintenance

Your app still works. Let's keep it that way.

Arveldon modernises ageing business applications and keeps them healthy afterwards. Upgrades, refactoring, re-platforming and careful maintenance, done without stopping the business that depends on them.

Find your modernisation pathMaintenance plans

Illustrative still life: coral vase with olive leaves, green glass and an open laptop on a warm table
Illustrative, AI-generated

Most software is not replaced. It is inherited.

Somebody built it years ago. It runs a crucial part of the business: orders, bookings, records, quotes. The original developer has moved on, the framework is several versions behind, and every change feels risky. Nobody wants to touch it and nobody can afford to lose it.

That is where we come in. Arveldon is a London software company focused on two things: bringing existing applications up to date, and maintaining them properly once they are. We are not here to sell you a rewrite. Often the best answer is a sequence of careful, reversible steps that leaves the app modern, documented and boring to run.

Boring is the goal. A well-maintained application should be something your team stops worrying about: updates arrive on schedule, releases happen on an ordinary Tuesday, and anyone new can read how it works. Getting there rarely needs heroics. It needs patience, good tests and someone who takes responsibility for the whole picture.

Modernise

Bring it up to date

Framework and runtime upgrades, dependency clean-up, moving from a single ageing server to managed hosting, untangling the parts nobody understands and adding the tests that make future change safe.

  • Version and dependency upgrades
  • Refactoring risky modules
  • Re-platforming to managed hosting
  • Database upgrades and migrations
  • Replacing a module where repair is not worth it
How modernisation works

Maintain

Keep it healthy

Planned maintenance on a monthly rhythm: security updates applied and tested, small fixes, monitoring of errors and uptime, backups checked by actually restoring them, and a running record of what changed and why.

  • Security and dependency updates
  • Bug fixes and small changes
  • Error and uptime monitoring
  • Tested backups
  • A change log you can read
Maintenance in detail

Where every project starts

The health check

A fixed-price review, usually one to two weeks, that tells you exactly what you are dealing with before anyone commits to a larger budget. If you stop after it, you still keep everything it produced.

  1. Code and dependencies. Versions, end-of-life dates, known vulnerabilities in libraries, the modules that are hardest to change and why.
  2. Hosting and delivery. Where the app runs, how it is deployed, who has access, and whether the environment could be rebuilt from scratch if the server disappeared tomorrow.
  3. Data and backups. Database version and size, backup schedule, and a real restore attempt to a separate environment so recovery time is measured rather than guessed.
  4. People and knowledge. Short conversations with the people who use and support the app, so we understand which features matter and which can be retired.
  5. The report. Risks ranked in plain English, a recommended route with alternatives, rough effort ranges and the inputs we would need from you.

Who calls us

Operations managers who rely on an internal app built by a contractor who has since moved on. Small software-led businesses whose product has outgrown its first framework. Organisations whose agency has closed or changed focus, leaving a working system with no one looking after it. Teams told by an auditor or insurer that an unsupported platform needs attention.

What they share is not a technology. It is a working application that matters, a growing sense of risk, and a wish to deal with it calmly rather than in a crisis. That is the situation we are built for, and the one in which careful, unglamorous engineering pays off.

Interactive

Retain, refactor, re-platform or replace?

Four honest options for an ageing app, each with real tradeoffs. Answer six quick questions in our path picker and see which route fits, what it costs you in disruption and what it buys you in years.

Open the path picker
  1. RetainPatch, secure and document what is there
  2. RefactorImprove the code in place, step by step
  3. Re-platformMove it to modern hosting and runtime
  4. ReplaceRebuild or buy, with careful migration

Signs your app needs attention

Nobody will deploy on a Friday. Releases are manual, rare and frightening.

The framework is out of support. Security patches no longer arrive for the version you run.

One person holds the knowledge. If they are away, changes wait.

Small changes take weeks. Every fix breaks something somewhere else.

The server is a mystery. Nobody is sure what is installed or how to rebuild it.

Backups are assumed. They exist, probably, but have never been restored.

Illustrative close-up of a green drinking glass and coral ceramic in warm light

Approach

Small, reversible steps

We start with a technical health check: reading the code, mapping the infrastructure, running the tests if any exist, and listing risks in plain language. Then we agree a sequence of changes, each one deployable on its own and each one with a way back.

We add tests around the parts we touch, automate deployment early so releases become routine, and write down what we learn as we go. By the end, the app is not just newer. It is understood.

Read the approach

Build your own care plan

Choose which maintenance activities matter to you, and how often. The care plan builder turns your choices into a plain written plan with the effort each activity typically involves, ready to send to us or to use with any other supplier.

Open the care plan builder

Promises and limits

What we say, and what we will not

We will

Explain risks before we start. Give estimates as ranges with assumptions. Keep the app running during the work. Leave documentation behind. Hand you everything if you move on.

We will not

Promise round-the-clock cover; we work Monday to Friday, 09:00 to 18:00 UK time (Europe/London, GMT/BST). Claim security certifications we do not hold. Recommend a rewrite because it is more interesting to build. Show you clients or numbers we do not have.

All promises and limits

Field guide

Reading before you decide

Quick answers

Which technologies do you work with?

Mainstream web stacks, typically PHP, JavaScript and TypeScript, Python and common relational databases, plus the major cloud and managed hosting providers. We confirm fit during the health check and say so if your stack is outside what we can maintain well.

Can you take over from our current developer?

Yes. We prefer an overlap period and a handover session, but we can also start from the repository and server access alone.

Do we have to sign up for maintenance after modernisation?

No. Maintenance is optional. Everything is documented so you can maintain the app yourselves or with someone else.

Is there a minimum size of app?

No, but very small apps may be better served by an off-the-shelf replacement. We will tell you if so.

Already looked after by us?

Report issues and request changes through the help page.

Get help

Tell us about the app nobody wants to touch.

A few sentences is enough to start. We reply within two working days.

Say hello