We would like to inform you that, as of December 31, 2025, the public preview of Dedicated Cloud Foundry on STACKIT Kubernetes Engine has ended.
We greatly appreciate all the feedback received and will take it into account for future development.
If you have any questions, our Help Center is always at your disposal.
The STACKIT Cloud Foundry Portal got a major update, now offering intuitive Cloud Foundry organisation- and space-management, as documented here.
STACKIT project owners can now change Cloud Foundry organisation quotas and assign the Cloud Foundry organisation manager role from the STACKIT Portal.
Our Help Center is always at your disposal if you have any questions.
We would like to inform you that the 28.07.25 version has been updated. This change affects the idle connection timeout for the following services: MariaDB, Redis, RabbitMQ, LogMe2, and OpenSearch. Previously set to several days, the timeout is now reduced to 60 minutes.
Note: This change applies only to the above-mentioned Data Services and does not affect their Cloud Foundry counterparts ordered through the Cloud Foundry Marketplace.
Key Benefits:
This change is part of our ongoing efforts to enhance performance and reliability.
Our Help Center is always at your disposal if you have any questions.
We are happy to announce that STACKIT Cloud Foundry now supports 32 GB RAM instances as documented here.
There are also some other changes to note:
On 12 May 2022 the STACKIT Cloud Foundry introduces a new load balancer in front of all applications running on the platform. This new load balancer will ensure, that the Cloud Foundry stays scalable to keep up with the rapid growing traffic handled over its *.apps.XX.cf.eu01.stackit.cloud wildcard domain and all application routes using it.
This also means that the IP Addresses of the *.apps and *.system domains change to the IP Address of the new load balancer starting on 12. May 2022. The new IP Addresses will be:
This change means for you: If you have any Firewall Rule set to the current IP Address of the *.apps or *.system domains of the internal as well as the public Cloud Foundry Instances, you have to add the new IP Addresses, or the Firewall will block traffic to your application after the new load balancer is rolled out.
Currently the wildcard domain URLs of Applications on Cloud Foundry provided by the platform, so called Routes, are accessible over the HTTP (Port 80) and HTTPS Endpoints (Port 443). Any Access of Applications over the HTTP Endpoint (Port 80) are currently automatically redirected to the HTTPS Endpoint.
On 07.04.2022 we will disable the HTTP (Port 80) Endpoints of Routes.
To further harden our Cloud Foundry to deliver a maximum secure experience for hosting your applications in the Cloud we will completely disable the HTTP (Port 80) Endpoint of Routes on April 7, 2022 and therefore will also no longer automatically redirect from the HTTP (Port 80) to the HTTPS (Port 443) Endpoint of your Applications Route.
Please be aware, if you are still accessing your Application over HTTP (Port 80) Endpoint, your Requests will fail after the 07.04.2022. Please change any access to your Application to the HTTPS (Port 443) Endpoint.
We have improved the display accuracy of the cloud foundry status in the STACKIT Portal. Any action which will be done via API or CLI of the underlying Cloud Foundry platform will be represented in the STACKIT Portal. In addition, error messages that occur during the creation, update or deletion of service instances are now displayed in the STACKIT portal, so that users can correct them with the help of the documentation.