SCS Cloud Store — Sovereign Cloud Stack Technology Demo

Step 1 · Service

What do you want to host?

Open-source services with no licence lock-in. Every one of them runs on plain OpenStack and Kubernetes — the same stack every SCS-compatible cloud is built on.

Step 2 · Location & shape

Where may it run?

Jurisdiction is a hard filter, not a preference: only clouds operated under the law you pick will be asked for a quote.

Jurisdiction

A cloud whose parent company is subject to a foreign disclosure law is not in the EU jurisdiction set, wherever its data centre happens to stand.

Resources

Data volume — 500 GB

Block storage, scs-0114 volume type

Floating IPs — 1

Public IPv4 addresses

Backup retention — 30 days

Nightly snapshots, off-site

Expected egress — 500 GB / mo

Traffic leaving the cloud

Discount or framework agreement

Try:

Availability

Environmental footprint

Step 3 · Price discovery

One request. Every cloud answers.

Because the resources are standardised, the question can be too. The same JSON goes to every SCS-compatible cloud, and every answer comes back in the same shape — comparable without a spreadsheet.

This request is not a standard yet

scs-0412 standardises metering for operators. The customer-facing question — “what would this cost at your cloud?” — has no standard at all. Here is what one could look like.

Step 4 · Offers

Pick the offer that suits you

Identical resources, priced by independent operators competing for your workload. The last rows are hyperscalers — sized to match, but they answer no such request.

Step 5 · Deployment

Rolling out

Plain OpenStack API calls against a standard image. Nothing here is provider-specific — that is the whole point.

openstack --os-cloud …

Step 6 · Portability

Twelve months later…

This is the moment that decides whether a cloud is sovereign. Not the marketing — the exit.