What we at Flownative think and do

Flownative Blog

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

  • Log4j zero-day vulnerability (Log4Shell)

    A critical zero-day exploit in the popular Java-based logging framework Log4j was published last Friday afternoon. Since it is easy to exploit and its widespread use, Germany's BSI assigned its highest warning level to this vulnerability.

  • New prices and plans for Flownative Beach

    For the first time since we launched Beach we make adjustments to our pricing model, based on how our customers use Beach today and what is planned for the future. We added some plans, removed others and updated prices for most of them.

    tldr; We love transparency, so I'm going to give you some insights into how our prices come to be. However, if you're only interested in the actual changes and not the background information, you can skip to "what we changed" further below.

    The Guess Work

  • Support for PHP 8 available

    PHP 8 is now available in Beach and Local Beach, with support in Flow and Neos right around the corner!

    Neos and Flow

  • Multi-Factor Authentication in Flownative Beach

    As of today we introduce a centralized login and Multi-Factor Authentication for Flownative Beach accounts

    Flownative ID

    Throughout the last weeks we've been busy with a major rework behind the scenes: We introduced a centralized authentication service for Flownative Beach and future services we are going to offer.

  • Semantic Versioning and version number formats

    In an automated build and deployment pipeline you deal a lot with version numbers. At Flownative, we generally follow the rules of Semantic Versioning, since it's a widely-used standard.

    One of the benefits of using such a standard is, that many tools play well together. There are also regular expressions you can use to check your own made up version numbers. So, since there is a standard, and your tool claims to support it, everything should be clear, right?