Self-hosted Wave
Self-hosting runs the Wave container provisioning service inside your own infrastructure instead of using Seqera-hosted Wave. Teams self-host when they cannot grant Seqera-hosted Wave access to a private registry, or when compliance requires the service to run inside their own boundary.
You can self-host Wave in two configurations:
- Wave Lite: Container augmentation, inspection, and private registry authentication.
- Wave: Everything in Wave Lite, plus on-demand container builds, freeze, mirroring, and security scanning.
Every deployment starts with Wave Lite. The full configuration is a Wave Lite deployment on Amazon EKS with build, mirror, and scan enabled on top.
For the full capability comparison, see the feature matrix. For how Wave provisions containers, see How Wave works.
Install path
Choose the path that matches your infrastructure.
Docker Compose
Run Wave Lite on a single Docker host without Kubernetes. Choose this path for a compliance-constrained site that cannot run Amazon EKS, or a deployment too small to need a cluster.
Install Wave Lite with Docker Compose
Kubernetes
Run Wave Lite on a Kubernetes cluster you already operate. Wave Lite has no AWS dependency and runs on any conformant distribution. This is also the path to the full Wave configuration. Install Wave Lite on Amazon EKS, then enable Wave builds to add on-demand builds, freeze, mirroring, and scanning.