Skip to main content
Your running self-hosted Vexa service that stays up to date.
  1. Bring your own cloud — k8s, GCloud, AWS, OpenShift. A namespace in a cluster, or an entire fresh one.
  2. Install Vexa Delivery — new deployment · existing one.
  3. Set it to consume the public images — or a private channel — how channels work.
  4. Cluster running, self-updating on new images published — operations.
Everything is open source, images public on Docker Hub. Nothing reaches in: your cluster pulls, verifies with keys you pin, and promotes to production on your attestation. Already running Vexa? Start at Upgrade.
Not built yet. Every channel is credentialed today — the free one in step 3 is issue #9, not a running service. What else is and is not proven: what’s proven, and where.
How it works · Install · Environments