Vesper gives each pull request its own preview environment on Kubernetes: a
running copy of your application at that version, with its own URL, isolated
from the others, and deleted automatically when its time to live (TTL) ends.
It is an operator that runs in your cluster, and a CLI, vesperctl.
Quickstart · Documentation · Security model · Contributing
Vesper does not build images: your CI builds one per pull request, and a
PreviewEnvironment points at it. The operator watches these objects and does
the rest. The architecture goes through it step by
step.
On a local kind cluster:
kind create cluster --name vesper
kubectl apply -f https://github.com/eventide-oss/vesper/releases/download/v0.1.0/install.yaml
kubectl -n vesper-system rollout status deploy/vesper-controller-manager
# install vesperctl from the release: see the quickstart, step 3
vesperctl create demo --image nginxinc/nginx-unprivileged:1.27-alpine --port 8080 --ttl 2h
vesperctl get demo # phase, URL, expiry, conditions and eventsThe quickstart walks through it, from installing
vesperctl to opening the preview in a browser, in about ten minutes. On a
real server, with a domain and HTTPS: try Vesper on a server.
Before a pull request is merged, people want to see the change running. A shared staging environment gets crowded, and running the branch on a laptop is not open to everyone. A preview per pull request solves both, as long as it is isolated and does not stay forever.
- Isolated by default. Each preview gets a namespace with the restricted Pod Security profile, a ResourceQuota, a LimitRange and a default-deny NetworkPolicy. A namespace is a soft boundary, though: the security model says what Vesper protects against, and what it does not.
- Gone on time. A TTL from 1 minute to 7 days; when it ends, the namespace and everything in it is deleted. No orphans.
- Easy to follow.
vesperctl listandvesperctl getshow the phase, the URL, the expiry, the conditions and the events. Prometheus metrics included. - Verifiable. Releases ship checksums and build provenance attestations; the image runs as a non-root user and is pinned by digest.
- Quickstart, on kind, and Try Vesper on a server, with k3s, a domain and HTTPS
- Cheat sheet: the everyday commands
- vesperctl reference and CRD reference
- Architecture and the decision records
- Vesper, Argo CD and Flux: how Vesper compares, and when to choose which
- Security model and metrics
- Development: build and run Vesper from source
All the guides are listed in docs/, and published on the documentation site.
Today you create a preview yourself, and it runs one application. Two steps take Vesper to a preview of the whole pull request, opened and closed on its own.
A GitHub App receives the events of the pull request: the preview opens with it, follows each push, and closes with it. Vesper posts the URL on the pull request, like this:
Testing a change end to end needs more than one image. A preview will run several components side by side, a frontend, an API and a database seeded with test data, in the namespace of the preview, so the pull request is tested as it will run.
How it will work under the hood:
The GitHub integration is available to try from v0.2.0-rc.2: Previews from pull requests sets it up, and vesper-demo shows it live. The rest of v0.2 is in its milestone. The multi-service previews are concepts, planned in the v0.3 milestone, whose design starts with #162: the shape of the API is not decided yet.
- v0.2, GitHub integration. Previews from pull requests, private images, protected preview URLs.
- v0.3, multi-service previews. Several components and a seeded database per preview.
- Later, ideas rather than promises. Policies per team, other forges such as GitLab, previews that sleep when nobody uses them, the OpenSSF Best Practices badge and an application to the CNCF Sandbox.
v0.1.0 is the
first release. The API is v1alpha1 and may change before v1.0. What v0.1
covers, and how it was checked, is in the acceptance of v0.1.
Contributions are welcome. Read CONTRIBUTING.md first, and pick one of the good first issues. The project follows a Code of Conduct and a simple governance. Every change starts from an issue and ends in a small pull request that follows the template. AI agents also read AGENTS.md.
If Vesper is useful to you, a star helps others find it.
Apache-2.0. The name and the logo of Vesper are described in the brand guide.




