Within this page, you can find a list of the latest software stacks and engines provided by the platform. These are the officially supported, regularly updated software solutions you can use to create your environments. The stacks are delivered as Docker images, which are stored in the platform’s public registry (Docker Hub). The exact specifics of the stack update and security handling are described in the dedicated section below.
- Software Stacks Versions
- Stack Updates and Security Handling
Note: All the platform-certified software stacks are based on the AlmaLinux 9 base OS images by default. This ensures support for all up-to-date functionality, modern security standards, and compatibility with the latest software solutions.
The AlmaLinux 9 base images are not available on the platform versions prior to 8.3, the CentOS 7 base OS (reached EOL on 30th June 2024) is used instead. If you want access to both options, please contact your hosting provider to upgrade the platform.
Each software stack remains supported by the platform up to the end-of-life (EOL) date notified by the respective upstream maintainer. After the EOL, stacks are no longer available for creating new environments, but the existing ones remain fully operable (including redeploy, cloning, and horizontal scaling). We highly recommend recreating or redeploying these containers with the latest release to ensure access to all the latest functionality and security fixes. Similarly, it is advisable to periodically (at least once per year) update all of your environments.
| LOAD BALANCERS | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||
| APPLICATION SERVERS | |||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||||||||||||||||||
| DATABASES | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
| ADDITIONAL STACKS | |||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||||||||||||
| ENGINES | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||
Stack Updates and Security Handling
- Stack Release Frequency: New stack versions are delivered as separate images shortly after upstream releases, giving users rapid access to the latest features and security patches. Many new images are available within a day or a week, while others may take longer to accommodate validation, debugging, and compatibility fixes. Existing images are not updated (see the “Existing Images” section below).
- Stack CVE Scanning: All new images of platform-certified stacks undergo mandatory CVE (Common Vulnerabilities and Exposures) scanning against the latest vulnerability database to identify and address potential security vulnerabilities before being made available for use.
- Vulnerability databases are synchronized daily to ensure up-to-date coverage.
- Images containing critical or high-severity vulnerabilities are not published until the fixes have been applied.
- Medium- and low-severity findings are assessed individually and may not block publication.
- Existing Images: After publishing a stack image, the platform does not modify or remove it, which ensures the stability and reliability of existing environments. CVE fixes are applied only in new stack versions released after upstream updates.
- Deprecated or end-of-life stack versions (including CentOS 7-based ones) are not updated, even if new CVEs are reported.
- CVEs disclosed after the publication of an image are handled through the regular release process as described in the “Stack Release Frequency” section.
- The platform may deprecate older stack versions over time, making them unavailable when creating a new environment.
- Existing Containers: After creating a container from the stack image, the platform does not modify it, as it may affect user applications. It is the responsibility of the environment owner to choose the appropriate stack version for their purpose. Also, we recommend monitoring relevant CVEs and periodically redeploying containers to incorporate security fixes.
- Containers based on deprecated or end-of-life stack versions remain fully operable (including redeploy, cloning, and horizontal scaling).
- Containers are not automatically updated to newer stack versions; users must manually redeploy them to apply updates.
- Users should monitor relevant CVEs and redeploy their containers as needed to incorporate security fixes.
Share this:
