Labs
A lab is a private Linux machine. You get root, persistent storage, an address on your private tunnel, and optionally a public domain with HTTPS.
The lab page
Everything about one lab lives on its page in the dashboard, across these tabs:
| Tab | What is there |
|---|---|
| Dashboard | Connection details, live CPU and memory, the Code button |
| Deployments | Every deploy attempt, with status, duration and errors |
| Domains | The domains this lab serves |
| Preferences | Startup script, passwords, keys, always-on |
| Activity | Lifecycle events and who caused each |
How many you can run
| Plan | Labs running at once |
|---|---|
| Free | 2 |
| Paid | 4 |
The counter in the catalogue header shows how many you are using. Stopped and paused labs do not count.
Organizations may have their own limits. Your exact numbers are in Account Settings → Account Limits.
Resources per lab
CPU and memory come from the lab's template and your plan, not from a slider at deploy time. Live usage is on the lab's Dashboard tab, including a CPU-throttle figure that tells you when a lab is being held back rather than simply busy.
Sustained heavy CPU use gets you a warning first, then the lab is stopped.
Extra copies
Some labs let you run more than one independently — each with its own address, storage option and settings. See Running extra labs.
Sharing a lab
You can give someone else access to a running lab without handing over your account.
| Role | What they can do |
|---|---|
| Viewer | See status, stats and connection info — not credentials |
| Operator | Also start, stop, pause and redeploy |
| Manager | Also change preferences and share it onward |
Only the owner can terminate a lab. Sharing requires a paid plan or 7,500 Zeal, and can be granted to a person or to a whole team.
Deploy history and failures
The Deployments tab lists recent attempts with status, duration, exit code, who triggered it, and the error text when one failed.
It also flags the confusing case explicitly: a deploy that failed while a container is nevertheless running.
In this section
How labs work
What a lab is, how you reach it privately, and how you publish it when you want to.
Connect to a lab
Four ways in - browser VS Code, SSH, your own editor, and a graphical desktop.
Lab settings
Startup scripts, passwords, SSH keys, always-on and the custom error page.
Stop, pause and delete
What each way of shutting a lab down keeps, and what it throws away.
Running extra labs
Run more than one copy of the same environment, each independent.
Scale groups
Run several copies of one lab behind a single URL, with optional autoscaling, health checks and canary releases.
Sharing and workgroups
Give other people access to a lab without handing over your account, and share with a whole group at once.