Renewing your software, without downtime.

Outdated software is a risk and gets more expensive every year. We bring your platform to a current stack step by step. Your customers notice nothing, except that it gets faster.

  • Small steps, each live on its own
  • Always back to the previous version
  • New features can simply continue

Every version has an end date.

After this date there are no more security updates. If your platform runs a version to the left of the line, new leaks stay open.

20222023202420252026202720282029
PHP 7.4
28 Nov 2022
PHP 8.0
26 Nov 2023
PHP 8.1
31 Dec 2025
PHP 8.2
31 Dec 2026
PHP 8.3
31 Dec 2027
PHP 8.4
31 Dec 2028
Today

Source: end of security support according to php.net.

We replace your platform part by part.

A large project in which everything is converted at once almost always overruns. We replace part by part, while the old system simply keeps running.

Everything at onceMonths of building, then one tense switch.
Building, nothing liveSwitch
Step by stepSomething better every two weeks, every step live.
Month 1Month 3Month 6
Less riskEvery step is small and can be rolled back.
Earlier resultsImprovements are live after weeks, not after months.
Room to adjustIf priorities change, we move with them.

Which layers of your platform we modernise.

Not just the programming language. We look at every layer of your platform and tackle what delivers the most.

Language and framework

PHP 5.6PHP 8.4
Laravel 5Laravel 11

Database

MySQL 5.5MySQL 8.0
Loose queriesMigrations

Frontend

jQueryVue or React
Separate pagesComponents

Infrastructure

One serverDocker and CI
Manual deploymentAutomatic

Quality

No testsAutomated tests
Hoping it worksKnowing it works

Frequently asked questions about modernisation.

Is your question not listed? Call +31 10 318 0515.

Does everything have to change at once?

No. We modernise in small steps, part by part. Each step goes live on its own and the platform keeps running.

Can we have new features built during the modernisation?

Yes. We plan it together in the same sprints. A new feature is often a good moment to replace an old part.

How long does a modernisation take?

That depends on the size. After a code audit you get a schedule per step, with a fixed price per phase.

Is rebuilding not faster?

Sometimes it is. Usually not: rebuilding takes longer than expected and you stand still for months. In the audit we weigh both options fairly.

What if something goes wrong with a release?

Every release can go back to the previous version within minutes. That is why the steps are small.

The coffee is already on.

Bring your question, your process or an idea that is not finished yet. In a first conversation we map out your situation and you get honest advice on the next step.

Freshly made

How do you take it?