Sovereign Cloud Stack

One platform — standardized, built and operated by many.

Use Sovereign Cloud Stack

Getting SCS

Sovereign Cloud Stack is fully Open Source – we develop it in an open development process in an open community. We follow the Four Opens of the Open Infrastructure Community. We work closely with the upstream projects from the Open Infrastructure Foundation, the Cloud Native Computing Foundation and other open source communities. Most of our source code comes from these communities – when we improve, amend, change things, we seek the contact with these communities to contribute our changes back.

We use Github/SovereignCloudStack to manage the code we are using – our own code mainly consists of the automation and integration that glues the used upstream projects together in a consistent and manageable way. Add documentation and CI tests to the mix.

To install your own SCS code, so you can study, test, change it and contribute to it, we refer you to our Github SCS Docs repository.

On Jul 15, 2021 we have published Release 0.

On Sep 29, 2021 we have published Release 1.

On Mar 23, 2022 we have published Release 2.

On Sep 21, 2022 we have published Release 3.

On Mar 22, 2023 we have published Release 4.

On Sep 20, 2023 we have published Release 5.

On Mar 20, 2024 we have published Release 6.


For the base layers, we heavily build on top of the Open Source Infrastructure and Service Manager (OSISM) project.


We are a global community of companies, organizations and individuals.

Please see the Community section on our docs pages to understand how the community interacts to create the SCS standards, code and knowledge. If you want an individual onboarding, you can also directly get in touch with us.

We are an open and welcoming community. Expectations towards the behavior of community members are expressed in our Code of Conduct.

Adopting SCS

There are different steps you can take to support and adopt SCS.

First of all, we appreciate contributions to SCS and to the relevant upstream open source projects. If we can join forces upstream to successfully push topics that are relevant e.g. for digital sovereignty, that’s great.

If you consider adopting SCS, there are two dimensions: Which modules and what adoption level.

First is that SCS is modular. You might adopt just some pieces of our container stack. Or maybe the Ops stack. Or IaaS. Or ceph. Or maybe everything but ceph …

Second, we see three different levels of adoption.

Adoption levels

First level would be that you want to make your platform compliant with SCS standards for this module. This ensures you are compatible to a growing ecosystem. This requires to pass conformance tests. (Note that as of July 2021, most of the conformance tests are still to be developed, but they will come as they are an integral part of our deliverables.)

Second level would be using the (reference) implementation for the module in question. This means you are using and contributing to the same piece of code and save a lot of work in curating, integrating, automating, testing, documenting this piece. Importantly, as we create best practices for Operations, you’d also be able to participate in this – possibly opening yourself up to a model, where you could share Operational duties in an Open Operations model.

So an adoption matrix could look like this (simplified):

Module Adoption level 2022 Adoption level 2023
Monitoring none compliant
IaaS compliant implementation
Storage none none
k8s-capi implementation impl+OpenOps
k8s registry implementation implementation