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.

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.

Regular backups are made automatically for all Beach instances. If something goes really wrong, it was previously possible to quickly restore the working state via a support ticket. So that you can now do this yourself at any time of day or night, there is a new feature in the Control Panel - and it can do even more than just restore backups!

In the Control Panel, you will now find a “Backups” section where you can see all available backups:

cover auto

The recent security vulnerability in OpenSSH – nicknamed RegreSSHion for good reason – is already patched in Flownative Beach.

The issue, assigned the CVE-2024-6387 and published on July 1st, is rated with a score of 8.1 out of 10. So we understand our customers are worried about a potential impact on our Flownative Beach cloud hosting.