What we at Flownative think and do

Flownative Blog

Insights into our work, sneak peeks at projects, interesting technology, …

  • Critical security vulnerability in Flow and Neos

    The Neos team has issued a warning about a critical security vulnerability in Flow and Neos, which, under certain conditions, allows attackers to upload arbitrary files to the server and potentially execute the uploaded code.

    It affects all Flow versions released in recent years and, consequently, all Neos versions built on a vulnerable Flow version.

  • Price adjustments with effect from 1 July 2026

    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.
  • Digital Sovereignty – Where Should I Put My Kubernetes?

    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
  • CMS isn't dead—it's just starting to become important

    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.