Flownative Blog

For the first time in over 10 years—since Flownative Beach was founded—we have to raise our prices. Due to the extreme increase in hardware prices (keyword: “Ramageddon”), our main supplier, Hetzner, has drastically raised its prices. Since the extent of these adjustments was not known in advance, we, too, were surprised by their magnitude. Unfortunately, we have no choice but to pass these higher costs on to our customers on relatively short notice.

Yesterday, I spoke at the International PHP Conference in Berlin about digital sovereignty – and about why and how we’re migrating Flownative Beach from Google to Hetzner step by step. Here’s a summary for anyone who couldn’t make it.

The dreaded late-night call

In early June, I was on stage at the Neos Conference in Karlsruhe, trying to describe just how much the world of content management is shifting right now. And like probably everyone else, I’ve scrolled past posts that go something like this:

“Build a fully functional website in 5 minutes with AI. CMS is dead. RIP CMS.”

There are plenty of posts like that right now. And they annoy me every time. They’re partly right, of course. But they don’t tell the whole truth.

An important announcement of interest for anyone using pixx.io with Neos by means of flownative/neos-pixxio – they will be switching off their old Perl-based API on 2026-01-31 (that is this weekend!).

Today we have made an adjustment to the automatic scaling of Beach instances. This post explains the background and explains the effects.

An instance can be automatically scaled horizontally in Beach in order to be able to react to fluctuating loads.

For this purpose, the minimum and maximum number of replicas can be defined, as well as the CPU load, which triggers scaling up if exceeded.

Settings for the automatic scaling of an instance cover auto Einstellungen für die automatische Skalierung einer Instanz