Skip to main content
– Blog

Code is generated quickly, but proper maintenance takes time. Changing our release channels

by Tobias Baader, OpenCloud Product Manager

The world of software is undergoing a transformation: code is now being produced faster and in greater volumes than ever before. This does not make it any easier to keep software secure and stable over the years. We are responding to this. From the production release in April 2027, these will only be available via subscription. The ‘Rolling’ release channel will remain public and free of charge, and every fix will be included there. The licence remains unchanged and the source code will continue to be publicly accessible.

Code is generated quickly but proper maintenance takes time.

How does our business model work with fully open-source software? By providing professional maintenance and support to organisations that use OpenCloud for business-critical purposes. In future, this maintenance will be included in the subscription. We are aware that this change represents a restriction for existing users of the free Production Release. At the same time, subscriptions provide the financial basis for the long-term maintenance and further development of OpenCloud.

Code comes quickly, maintenance remains

This year, over 1,000 people have contributed to OpenCloud with comments, feature requests or suggestions for improvement. In addition, there were over 330 pull requests from the community – twice as many as in the same period last year. For an open-source project, this is a positive development and we want to see more of it.

Each of these pull requests requires careful review, comprehensive testing and ensuring long-term functionality. Every issue must be read, categorised and responded to (even if we don’t always manage to do so). This process cannot be sped up simply because writing takes less time. Keeping software secure and stable over many years, on servers that people rely on, remains a labour-intensive task. As a company, this is the work we do.

Production: Rolling Releases and Reliable Maintenance

OpenCloud has two release channels: Rolling and Production. The Rolling channel is released every three weeks with the latest features and undergoes automated quality assurance. Individual Rolling releases do not receive patches. Instead, bug fixes are incorporated into the next release.

Twice a year, we select an existing Rolling release, stabilise it and subject it to comprehensive quality assurance. We then publish it as a Production release. This version is continuously maintained: we backport fixes, test them against this version and publish patch releases, so that no one has to switch to new features just to receive a security fix.
Enterprise customers with a support contract can run production releases as LTS versions (Long-Term Supported Releases) and receive backports for two years.

For companies and organisations using OpenCloud in complex or business-critical IT environments, the Production channel offers key benefits:

  • Greater operational reliability: Additional testing and release processes reduce risks during production use and create a reliable foundation for stable operation.
  • Predictable updates: Longer release cycles make it easier to integrate updates into existing IT and maintenance processes.

Free code, paid maintenance

Until now, the Production release channel was free of charge, including all patches. So we have made available for free exactly what we sell. To ensure we can continue this work in the future, it must be funded in the long term.

The usual approach for open-source companies is known as ‘Open Core’: certain features are then only available for a fee. We are not taking this route, as it breaks the promise that OpenCloud is open.

Production vs. Rolling: How to work out what you need

Regulation: NIS-2, ISO 27001, BSI Basic Protection, KRITIS

The simplest test: Do you need to explain to an auditor or senior management how security updates are applied? Then you need Production. This applies to anyone subject to NIS-2 or operating in accordance with ISO 27001 or BSI Basic Protection. You must demonstrate that security vulnerabilities are patched promptly and that changes to the system are implemented in a controlled manner.

With ‘Rolling’, this becomes a hassle: every security fix brings new features, every three weeks, and each one has to be tested and approved. Production separates these processes. The version remains the same for half a year; only the patches are added (tested, of course). And if something does go wrong despite this, our support team is on hand.

An outage is costly

The second factor has nothing to do with regulation: what does a botched update cost? If, as a result, entire departments grind to a halt or files and patient data become inaccessible, Production is worth it even without an auditor.

Everything else: Rolling

If neither of these applies – for example, for home use – Rolling is sufficient. You simply need to update every three weeks.

Request an OpenCloud subscription

Do you use OpenCloud in a professional IT environment and place particular emphasis on stability, professional support and predictable updates?
With an OpenCloud subscription, you gain access to our comprehensively quality-assured production releases. Appropriate LTS packages are available to meet long-term maintenance requirements.

FAQs

What happens if you use Production and do nothing?

The instance continues to run; OpenCloud does not check for a licence. As usual, the November 2026 production release will receive patches until the next production release in April 2027. After that, no further fixes will be provided for this version. You can then switch to the rolling release or take out a subscription.

For how much longer will my version continue to receive patches?

As before, until the next production release. For the November 2026 release, this means: until April 2027.

How do you switch from Production to Rolling?

Replace the image opencloudeu/opencloud with opencloudeu/opencloud-rolling and select a rolling release that is newer than your production version. Production is a stabilised rolling release, so a newer rolling release will contain everything you already have. As with any upgrade, make sure you back up your configuration and data first.

How do I get onto Production?

Replace the image opencloudeu/opencloud-rolling with opencloudeu/opencloud and select a production release that is the same age as, or newer than, your rolling release. It is not possible to revert to an older version; a downgrade is not documented. If you are already ahead of the current production release, wait for the next one. From April 2027, you will need a subscription to do this.

Will I receive security updates as quickly as paying customers?

Critical fixes are also included in the rolling release and are then backported to Production. The difference for customers with a subscription is that they receive the fixes on a version that otherwise remains unchanged.

Is Rolling safe if I don’t update it every three weeks?

No. Fixes are only included in the next rolling release; we do not patch older rolling releases.

Is the licence changing?

No, the licence remains unchanged and the source code will continue to be publicly available. Anything published under Apache 2.0, AGPL or GPL will, in any case, remain available under that licence.

Is this the first step towards Open Core?

No. There are no proprietary functions, and there never will be. Every function is in the public code.

What subscription plans are available?

There are Basic, Professional and Premium editions. LTS is included in the Professional and Premium editions.

Is billing per instance, user or organisation?

Charges are calculated per user. If the High-Performance Computing add-on is used, an additional charge per TB applies.

Our service provider manages OpenCloud on our behalf. Who needs the subscription?

The service provider is responsible in this case.