Start a conversation

RSV Global / Services / Software Maintenance and Modernisation

Take on the codebase
nobody wants to touch.

Take over an existing application, stabilise it, reduce the technical debt that is actually costing you, modernise the infrastructure, or add AI where it creates real leverage rather than everywhere it fits.

Bring us a workflowSee the work
What we deliver

Make it safe to change, then make it better.

01Takeover. Read the system, document what is actually there, and establish a safe change process before changing anything.
02Stabilisation. Fix the failures that are costing you now, and put monitoring on the ones that will.
03Technical debt. Reduce the debt that blocks delivery, and leave alone the debt that does not.
04Infrastructure. Modernise deployment, environment isolation, secrets and credential lifecycle. Infrastructure as code where it earns its place.
05Release. CI, migrations, staged rollout and rollback, so shipping stops being an event.
06Selective AI. Add AI to the parts of the system where it creates leverage, under the same boundaries as any new build.
How we approach it

Architecture first. AI compresses implementation afterwards.

The workflow, boundaries and acceptance criteria are written down before implementation. That lets AI accelerate delivery without quietly becoming the architect.

01

Assess

Reproduce the failures, classify inherited against introduced, and find out what the risky changes actually are.

02

Stabilise

Make the system safe to change before making it better. Do not weaken a check to get a green result.

03

Modernise

Infrastructure, delivery and dependencies, in bounded increments that each ship independently.

04

Maintain

Runbooks, health monitoring, credential lifecycle and failure recovery, whether we run it or you do.

Where AI does not belong

A rewrite is usually the expensive answer to a diagnosis nobody made.

Most systems that feel unmaintainable have a small number of specific problems: no test coverage where it matters, an unclear data owner, or a release process everyone fears. Those are fixable without discarding working software.

Proof

Systems we built and run ourselves.

Not client work. These are our own products, carrying our own risk, which is why the boundaries sit where they do.

Estate defined in code

LeaseOasis

A managed Kubernetes estate on AWS defined in Terraform, with autoscaling, private administration, federated CI credentials and an operations runbook.

Operated at the edge

AI Economy Ledger

Cloudflare Workers and object storage, with scheduled database, queue, ingestion and storage health monitors running against production.

Other services

Not quite the right door?

Custom Software DevelopmentGTM AutomationAI and Workflow AutomationAI Agent DevelopmentAI System Review
A useful first conversation

Show us the workflow everyone has learned to tolerate.

We will help determine whether it needs a focused product, an autonomous operating system, a stronger data layer, a review of what already exists, or a simpler fix that involves no AI at all.

Start a conversation