For QA and release managers
A release candidate that stands still
Clone the environment for the release, pin its versions and protect it, so nobody's afternoon edit changes what is under test. Run as many copies as you have suites, side by side, and reset any of them to a clean state in minutes.
What you get
One known build, start to finish
Protection means only a maintainer can change the definition. What passed on Monday is what ships on Friday.
Suites in parallel, not in a queue
Regression, performance and acceptance each get their own copy of the same candidate.
A clean slate on demand
A test that wrecks its own data is one Reset away from a known state: same versions, fresh volumes, same URL.
How it works
- 01
Clone and pin
Clone dev into release-1.4 and set the image tags. Versions are part of the environment, so every copy runs the same ones.
Cloning → - 02
Protect it
A maintainer marks the environment protected. Editors can still clone it, deploy it and run against it, but not change it.
Protected environments → - 03
Record the verdict
Findings go on the instance as checks linked to their runs, and the candidate is approved or rejected on the record.
Checks and the verdict →
Other use cases
Running on your own host in 10 minutes
Two containers. Works offline. Your data never leaves your infra.