Flownative Blog

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.

contain auto

What a week… even friends and family who have nothing to do with IT asked us how we managed to get through it. What happened?

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.

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

Last Friday, we had a major outage at Flownative Beach, which took around 30 customer projects offline for about an hour and a half. We would like to explain transparently what happened, how we dealt with it and what measures we are planning for the future.