01
Security fixes stop
Older Rails series eventually stop receiving fixes, even when new vulnerabilities are found.
Ruby on Rails modernization
Bring your Rails app forward — without rewriting what works.
We upgrade business-critical Ruby on Rails applications to a maintained version, verify that they still behave as they should, and keep them current afterwards.
No commitment. You speak directly with an engineer.
Free version check
Check your Rails application.
See what your application shows the outside world. One page, one request, and nothing about you is stored.
What we saw
A familiar situation
The software still works. The risk keeps growing.
A Rails application can stay useful for years while the framework falls behind. The longer the gap grows, the harder it becomes to patch, hire for and safely change.
02
Knowledge walks out
The person who knew the system best moves on, while the business still depends on it every day.
03
Every change gets heavier
Old dependencies and unsupported tooling turn small requests into risky, slow projects.
What changes
A current stack. A familiar application.
The goal is not a redesign or rewrite. It is the same business system on a maintainable foundation, with evidence that it still does what your people need.
Current Rails and Ruby versions
We move through major versions in controlled steps and update the supporting stack where required.
Behaviour checked before acceptance
We establish what the application does today, then verify the upgraded system against that baseline.
No big-bang cutover
The upgrade is prepared alongside the live application. Production keeps running while the work happens.
A system that stays current
Managed Rails keeps updates, security work and backup checks from becoming another postponed project.
The process
From uncertainty to a fixed plan.
You do not have to scope the upgrade for us. Discovery turns the codebase, its dependencies and its real use into a clear offer.
01 / DISCOVERY
We inspect the application
After an NDA, we review the source, clarify how the system is used and map the upgrade path.
02 / OFFER
You get one fixed price
The proposal sets the upgrade price and the monthly figure for keeping the application current.
03 / UPGRADE
We move version by version
The application is upgraded alongside production. You see progress throughout the work.
04 / OPERATE
You accept, then we maintain
We verify the result together, switch over and keep the framework and dependencies current.
Transparent starting points
Know the commercial model before the first call.
Discovery makes the upgrade price exact. The figures below are starting points, not a low headline followed by unpriced extras.
Discovery
€1,000+ VAT · one-off
A codebase review and clear upgrade plan you keep, whether or not you continue.
- Signed NDA
- Source and dependency review
- Fixed upgrade offer
- Fully deducted if you proceed
UpgradeFIXED PRICE
from €20,000+ VAT · one-off
Your application on the current Rails series, behaving as it did before.
- Exact fixed price set by Discovery
- Version-by-version upgrade
- Ruby and dependencies included
- Behaviour verification
- 50% on signature, 50% on acceptance
Managed Rails
from €500+ VAT · per month
Ongoing upkeep that prevents the next large upgrade backlog from forming.
- Framework and dependency updates
- Security advisories tracked
- Backups checked
- Three-month cancellation notice
Pricing covers one production environment plus backups. Larger features, third-party licences and additional environments are quoted separately.
Why us
You are not hiring a tool. You are hiring a responsible team.
Our engineers and AI work together to move faster and keep a clear picture of what has changed. The team stands behind the result together.
A company, not one contractor
Several engineers can take over from each other, with routines and paperwork that survive holidays and staff changes.
Production systems, not demos
Our experience is in software where an outage is noticed outside the development team.
Your code stays yours
You retain ownership of the application, its business logic and its data. Nothing is used to train AI models.
Remote across Europe
We contract across the EU and the UK. A video call is the only meeting the process needs.
Common questions
What teams ask before starting.
Which Rails versions can you upgrade from?
Any of them. An older starting point means more steps, which Discovery captures in the fixed price. The controlled, version-by-version method stays the same.
What if our application has few or no tests?
That is common. We establish the application's real behaviour before changing it, then build checks around the areas that matter. Those checks stay with the application afterwards.
Will the application go down during the upgrade?
No planned downtime is needed while the upgrade work is carried out. The new version is prepared alongside the running application and switched over after acceptance.
Can we buy only the upgrade?
The upgrade is delivered with Managed Rails so the application does not begin falling behind again immediately. The monthly service can be cancelled with three months' notice.
Where will our data and hosting live?
You choose one of two set-ups: we run the application on a dedicated Cirit server, or it stays on your own application server and you give us access to it. Either way, Managed Rails includes verifying that backups work rather than merely assuming they do.
How much time do you need from us?
Little, at three points. Discovery: a signed NDA, source access and answers to a questionnaire — usually a couple of hours from someone who knows how the application is used. Before the upgrade starts: a one-hour kickoff. After it: your acceptance of the delivery.
A useful first conversation
Tell us what the application does — and what worries you about it.
In thirty minutes, an engineer can help you decide whether an upgrade is worth investigating. No quote theatre, no commitment and nothing to sign. The price for the upgrade itself comes only after Discovery — never before.
If the calendar does not appear, a content blocker is likely hiding it.Open the booking page instead ↗