Application take-over
Your application does the job. Nobody dares to touch it anymore.
It has been running for years. But the framework is several versions behind, the server no longer gets updates, and the person who built it is gone. I take over any web application: I understand it, document it, bring it up to date in tested steps, then keep it evolving.
Warning signs
Do at least two of these sound familiar?
Why now
The clocks are already ticking.
An up-to-date application is an asset. A frozen one is a countdown: every month makes the upgrade more expensive, and an incident more likely.
And it is not just Rails: PHP, Node, Python, Django and Laravel all have their end-of-support calendars.
The approach
Three steps, prices known upfront.
- The audit · fixed price, agreed upfrontI read the code and the server: versions, dependencies, known vulnerabilities, backups. You get a readable report and a costed upgrade plan, even if you don't continue with me.
- The upgrade · on quote, fixed priceStep-by-step version upgrades, tested at each stage on a test environment, never straight in production. Application, dependencies and server brought up to date, documentation produced.
- What comes next · subscription from €390 / monthMonitoring, continuous updates, bug fixes, small improvements. Your application will never fall ten years behind again. The tiers.
Good to know
Frequently asked questions
My application isn't built with Rails. Is it still possible?
Yes. Ruby on Rails is my long-standing speciality, but the approach is the same for any web application: PHP, Node, Python, Django, Laravel… The audit says exactly what is feasible and at what price.
My application has no automated tests. Is that a problem?
That is the case for most applications I take over. Before touching anything, I add tests on your critical paths: they act as a safety net throughout the upgrade, and they stay yours afterwards.
What can break during the upgrade?
Nothing in production: everything happens first on a test environment, version by version. The switch only happens once each step is validated, and we can roll back at any time.
The original developer is gone and there is no documentation.
A classic situation. I only need access to the code and the server: AI agents reconstruct how the application works by reading all of its code. I produce the documentation as an output.
Do I need to move my application to another host?
Not necessarily. Your server can stay where it is; if the current hosting is a problem, I can offer a migration to Infomaniak, in Switzerland. Either way, you keep control and ownership of your infrastructure.
Going further
Technical guides.
Articles to understand what is at stake before deciding. The most technical ones are written for your developer, or the one you no longer have.
- Your application is ageing: take over, upgrade or rebuild?
- Taking over a web application with no documentation and no original developer
- How much does a Rails upgrade cost?
- Rails 7.1 has reached end of life: what does that mean for you?
- Upgrading from Rails 6 to Rails 7: the guide to breaking nothing
- Rails 8: what's new and why it's worth the upgrade
- Ruby 3.2 has reached end of life: why you should move to Ruby 3.3 now
- Ubuntu 20.04 reaching end of life: should you migrate your server?
- Webpacker is deprecated: how to migrate to esbuild
- DelayedJob has had its day: moving to Solid Queue
- Broken emoji, lost characters: the utf8mb3 problem in MySQL
Shall we talk?
Your application deserves a future.
Tell me what it does, what it runs on and what worries you. In thirty minutes we know whether an audit makes sense.