For support
Reproduce on the customer's version, not on main
A customer on last quarter's release reports a bug. Support brings up a copy pinned to that exact version, reproduces the report in minutes and pastes the URL into the ticket. The developer opens the same URL and starts the hotfix from what they see.
What you get
Reproducing stops being a request
Support has the versions in hand: pinning one is a field on the copy, not a build somebody has to make.
One URL for the whole ticket
The reproduction is a running stack anyone on the ticket can open, and the ticket is linked on the instance.
Engineering time goes into the fix
The developer skips rebuilding an old environment and starts on the hotfix branch. The copy expires when nobody deploys to it for a week.
How it works
- 01
Open the version for pinning
Whoever maintains the environment lets deployers set the application's image tag per copy.
What deployers may change → - 02
Bring up the customer's version
Support creates a copy with the tag pinned to 1.3.2, names the ticket as its purpose and links it on the instance.
Purpose and links on a copy → - 03
Hand over the URL
The developer sees the same thing on the same URL. Reset it to a clean state to try again.
Reset →
Other use cases
Running on your own host in 10 minutes
Two containers. Works offline. Your data never leaves your infra.