Host your projects, test runs, and generated code on your own infrastructure. Sign in
with the email on your subscription to download the release and activate your license.
Each download shows its own version. Appliance images are published separately from containers and Kubernetes.
Deployments used
—
Subscription
—
Activate an install
Your instance generates its own install ID on first boot. Find it in Settings → Administration
under License, paste it here, and we issue a license bound to it.
Re-issuing for an install you already activated is free and does not use another
deployment.
Checksum — TestVibe shows the same value if the paste
arrived intact.
Your deployments
Registry access
The TestVibe images are private. If your first install stops with denied,
manifest unknown, or a pod in ImagePullBackOff, check the image
reference and registry sign-in. We issue you your own token: pull-only, scoped to
your subscription, revocable on its own.
Where you run it
What to do
Docker Compose
docker login testvibe.azurecr.io -u <token-name>, then paste the
token as the password. Once per host.
Kubernetes
Create a pull secret and name it in your values: kubectl -n testvibe create secret docker-registry testvibe-registry
--docker-server=testvibe.azurecr.io --docker-username=<token-name> --docker-password=<token-password>
then --set global.imagePullSecrets[0].name=testvibe-registry.
Appliance (VHDX / OVA)
Nothing. The appliance runs the stack natively from software already inside the
image — it never pulls from a registry.
Set up your installation
On an appliance, first boot generates the installation secrets. Open the application address shown on the VM console.
For Docker or Kubernetes, provide the database password, blob signing key, blob admin key and runner key using your deployment configuration.
Open TestVibe and choose Create an account. The first account becomes the instance administrator; no default password or email relay is needed.
Configure email, sign-in, AI models and licensing in Settings → Administration.
For an existing installation, appoint an existing user through host recovery after upgrading.