Flownative Blog

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.

This year's Neos Conference was once again a very special event. Many volunteers turned a simple conference room into a colorful event location where the Neos community celebrated the release of Neos 9 after years of development work. AI was of course a theme that also ran through many of the talks. However, the focus was on presentations about the current future possibilities of Neos.

An exciting week comes to an end for me: The Neos team met in Vienna for a crucial sprint to finalize the remaining open items for the eagerly anticipated Neos 9.0 and Flow 9.0 versions. I had the privilege of representing Flownative on-site, while Karsten, Christian, and Markus worked intensively remotely.

Responsibly sourced: The new Event Sourced Content Repository

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.