For trainers
A lab per attendee, reset between sessions
One environment defines the lab. Each attendee gets their own instance of it, with their own seed data and URL, from the moment they sit down. The trainer can reset any lab in minutes, and every lab stops on its own after the course.
What you get
Start on the content
Nothing to install on attendees' machines. The lab is a URL that was ready before they arrived.
Theirs to break
Each lab is personal to its attendee. A wrecked one is reset to the starting state without touching anyone else's.
Nothing to tear down
Labs carry a lifetime and stop by themselves after the course, for in-house, partner and customer training alike.
How it works
- 01
Define the lab once
The environment holds the application, the seed data and, where attendees differ, the variables a deployer may set on their own copy.
Environments → - 02
One instance per attendee
Each attendee, as a deployer, creates their own copy — personal to them, so nobody resets a neighbour's. The trainer, an editor, operates all of them.
Personal instances → - 03
Reset, extend, let expire
Reset gives a clean start on the same URL, Extend keeps a multi-day course alive, and expiry stops the rest.
Reset →
Other use cases
Running on your own host in 10 minutes
Two containers. Works offline. Your data never leaves your infra.