This topic explains how Lobster manages software versions for your Lobster Cloud environment, including the version selection process, the staggered rollout from test to production, the versioning schema, and the option for customer-managed updates. You can find more details on this topic here: Platform Update Guide.
Standard update process
Lobster follows a structured process to ensure that only validated software versions are deployed to customer environments.
You can find the defined maintenance schedule for Lobster Cloud here: Maintenance schedule.
Step | Timing | Description |
|---|---|---|
Version selection | Before the test/DEV maintenance window | The latest version available at the time of the test/DEV maintenance window is selected. Each version is tested for installation compatibility before deployment. |
Test system deployment | As per predefined maintenance schedule | The selected version is deployed to all test and DEV systems. |
Customer testing period | 3 weeks between test and production deployment | You have approximately three weeks to test the new version in your test environment before it reaches production. |
Production deployment | As per predefined maintenance schedule | The same version is deployed to all production systems. |
Infrastructure maintenance | As per predefined maintenance schedule | Infrastructure maintenance — including web servers, databases, and cloud services — is managed exclusively by Lobster. Maintenance windows for these components are predefined and fixed; they cannot be adjusted or customized on a per-customer basis. |
Info
If issues are discovered during testing, the version is withdrawn and deployment is postponed until the issue is resolved.
Important
Lobster reserves the right to adjust infrastructure maintenance schedules or reschedule maintenance windows for individual cloud components to different dates or times at any time. This may occur without prior notice but will always be published on the status page.
Important
Operating system maintenance windows and database maintenance windows are predefined and cannot be customized on a per-customer basis. Standardized schedules allow Lobster to maintain all customer environments consistently and efficiently.
Staggered rollout benefits
The staggered update procedure (as per predefined maintenance schedule) provides:
Benefit | Details |
|---|---|
Automatic security updates | Your systems receive the latest security patches without any effort on your part. |
Pre-testing period | New versions are deployed to your test system three weeks before reaching production. You can validate critical business processes in advance. |
Predictable schedule | Fixed maintenance windows allow you to plan around updates. |
Versioning schema
The Lobster Data Platform uses semantic versioning in the format Major.Minor.Patch. Further information can be found here: Platform Update Guide.
GA and LTS version policy
Lobster Cloud customers always receive the latest available version, regardless of whether it is a GA release (General Availability) or an LTS release. If a major release transition occurs (for example, from LDP 25.1.x LTS to 26.1.x GA), your system will be updated automatically to the new GA version as part of the regular patching cycle. You may opt out of this update at any time and remain on the LTS version. In that case, you are solely responsible for keeping the software up to date. You will find the details in the next point.
Opting out of automatic LTS version upgrades
If you prefer to remain on your current LTS version and not receive automatic major release upgrades, you can opt out at any time by submitting a ticket to support@lobster.de. For more information, refer to the section Customer-managed updates (optional)
Please note
If you choose to manage patching yourself, this applies bindingly to all your environments (DEV, Test, and Production). A shared responsibility for patching between Lobster and the customer is technically not possible. We recommend keeping patching management within Lobster Cloud with Lobster to ensure consistent and verified maintenance.
Aspect | Details |
|---|---|
What happens when you opt out | Lobster removes your system from the automatic software patching cycle. You remain on your current LTS version. |
Your responsibility | You are fully responsible for downloading and installing patches yourself via the Update Center. Lobster continues to manage OS updates and database maintenance. |
Opting back in | You can return to automatic patching at any time by submitting a ticket. However, when re-entering the automatic cycle, your system will always be updated to the latest available version or release. There is no option to selectively skip versions. |
Automatic version enforcement
If your system falls three or more versions behind the current release, Lobster may automatically update it after prior notification. This policy ensures that all customer systems remain within a supportable version range and continue to receive security patches.
Customer-managed updates (optional)
In exceptional cases, Lobster offers an optional customized patching approach. This allows you to manage your update schedule through the Lobster Data Platform Update Center.
Please note
If you choose to manage patching yourself, this applies bindingly to all your environments (DEV, Test, and Production). A shared responsibility for patching between Lobster and the customer is technically not possible. We recommend keeping patching management within Lobster Cloud with Lobster to ensure consistent and verified maintenance.
Aspect | Details |
|---|---|
Opt-in required | Submit a ticket to support@lobster.de to opt out of automatic software updates. |
Download updates yourself | You download patches from the Update Center approximately 30 minutes before your planned restart. |
Restart via ticket | System restarts must still be initiated through Lobster via support ticket. You cannot restart the system yourself. |
OS and database updates unchanged | Operating system updates remain the responsibility of Lobster and are applied automatically within the predefined maintenance windows. |
Important
Operating system maintenance windows and database maintenance windows are predefined and cannot be customized on a per-customer basis. Standardized schedules allow Lobster to maintain all customer environments consistently and efficiently.
Important guidelines for customer-managed updates
Guideline | Details |
|---|---|
Do not download updates too far in advance. | If an emergency restart occurs, any pending update in the file structure will be installed automatically. This can cause unintended version changes. |
Avoid updates on Fridays, weekends, and holidays. | In rare cases, automated restarts may not complete successfully outside service hours. |
Download updates approximately 30 minutes before your planned restart. | This minimizes the risk of unintended installations during emergency restarts. |
Automatic fallback | If your system falls three or more versions behind, it will automatically return to the standard patching schedule after prior notification. |
Risks of customer-managed updates
If you choose to manage updates outside the regular maintenance windows, you must be aware of the following:
Risk | Details |
|---|---|
Updates are performed on test systems first. | You are responsible for extensive testing of all critical business processes. |
Rollback is not possible. | Once a version has been installed, it cannot be rolled back to the previous version by you. Restoring to the previous version is only possible via a backup restore. This will result in the loss of all data created after the update. Additional charges may apply for performing a backup restore. |
You bear the risk. | Any issues or errors in the new version must be reported by the customer. Resolution will be provided as part of the next available patch. |
Service hours only. | Updates can only be performed during regular service hours (Monday to Friday, 08:00 to 17:00 CET). |
Info
Customer-managed updates are not recommended unless you have a specific requirement that cannot be met by the standard software update schedule.