Stack category
Container Runtimes & Orchestration
The runtime layer decides how your code runs in production: as a container, a pod in a cluster, or a process on a bare VM.
Why this layer matters for sovereignty
Orchestration is the layer that makes your deployment portable: a container image runs the same way on any European cloud — this is what keeps infrastructure providers swappable.
Small, embedded distributions (k3s, k0s, MicroK8s) make Kubernetes viable on a single node, not just for platform teams.
PaaS offerings on European infrastructure give you the abstraction without the cluster to run.
What to look for
Right-size the tool: a single-node k3s or plain Docker Compose beats a cluster you don't operate well.
OCI-standard images (Docker, Podman) keep you portable between all providers.
Ecosystem: Helm charts and operator availability determine what you can install in one command.
For PaaS: build-pipeline and scaling behavior, and where the build servers physically run.
European & open-source runtime / orchestration providers
Curated as part of the European Stack Builder. Badges reflect the organization's origin — EU, EEA, EFTA, and UK count as European.
Dockerdocker.com
Industry-standard platform for building and running containerized applications
Lightweight Kubernetes for workstations, IoT, and edge devices
Minikubeminikube.sigs.k8s.io
Local Kubernetes focus tool primarily used for development and learning
Nebulanebula-orchestrator.github.io
Docker orchestrator for managing containers across multiple hosts.
Nomadnomadproject.io
Simple and flexible scheduler & orchestrator to deploy and manage containers and non-containerized apps
PaaS that auto-detects frameworks and deploys to EU data centers with zero config
Podmanpodman.io
Daemonless container engine for developing, managing, and running OCI containers
Static site hosting built entirely on European infrastructure with zero US dependencies
Frequently asked questions
What is container orchestration?
Container orchestration automates the lifecycle of containers: scheduling them across servers, restarting failed instances, scaling them with load, and rolling out updates without downtime. Kubernetes is the dominant system; Nomad is a lighter alternative, and Docker itself covers the single-host case.
Do I need Kubernetes?
Not necessarily. If you run a handful of services on one or two servers, Docker Compose or a minimal distribution like k3s is simpler and safer. Kubernetes pays off when you run many workloads, need self-healing and autoscaling, or must offer a platform to multiple teams.
Pick your Runtime / Orchestration
Compare these providers side by side and assemble your full sovereign stack.
Open the Stack Builder