Why now
The clocks are already ticking
If your application relies on one of these versions, it no longer receives
any security patches today:
Ruby on Rails 7.1 and earlierThe framework behind thousands of business applications
end of support · October 2025
Ruby 3.2 and earlierThe language under the framework
end of support · March 2026
Ubuntu 20.04 LTSThe operating system on a great many servers
end of support · May 2025
And this is not specific to Rails. Node, PHP, Python, Django, Laravel:
every ecosystem has its own end-of-support schedule. If your web application
runs on a VPS, the question is not whether it will need to be upgraded,
but when — and at what cost.
How it works
Three steps, prices known upfront
As with everything I do: no ticking clock of billable hours.
A written scope, an announced price, a verifiable result.
Step 1
The audit
€490 · fixed price, deducted from the rest if we continue
I examine your application and its server: versions, dependencies, vulnerabilities,
state of the backups. You receive a report a normal human can read, with
a costed upgrade plan. You know exactly where you stand — even if
you decide not to continue with me.
Step 2
The upgrade
on quote · fixed package based on the gap to close
Upgrading in stages, tested at each step on a staging environment —
never directly in production. Application, dependencies and server
brought up to date, critical flows verified, cutover once everything is green.
Step 3
What comes next
So it never happens again: monitoring, continuous updates,
bug fixes. Your application will never again fall ten years behind
all at once. The details are on the pricing page.
Why it is affordable with me. Specialized agencies charge
tens of thousands of euros for this work, because they throw whole teams at it.
My AI agents read your entire codebase, test every step and work under
my supervision — the same result, at a price a small business can afford.
Good to know
Frequently asked questions
My application is not in Rails — is it still possible?
Yes. Rails is my specialty, but the principle is the same for any
web application hosted on a VPS: Node, PHP, Python… The audit will say precisely what
is feasible and at what price.
My application has no automated tests at all. Is that a problem?
That is the case for most of the applications I take over. Before
touching anything, I put regression tests in place on your critical flows —
they act as a safety net throughout the upgrade, and they stay yours afterwards.
What could break during the upgrade?
Nothing in production: everything happens first on a staging
environment, version by version. The cutover only happens once each step is validated —
and we can roll back at any moment.
Do you host my application?
No — your server stays yours, at your own host. I bring it
up to date and I can monitor it through the subscription, but you keep control and
ownership of your infrastructure.
The original developer is unreachable and there is no documentation.
A classic situation. All I need is access to the code and the server —
my AI agents reconstruct how the application works by reading the entire codebase.
The documentation is something I produce as an output.