Networking
Every lab starts private. Only devices you have registered can reach it, over an encrypted tunnel. Nothing listens on the internet until you decide it should.
There are two directions, and they are set up separately.
| Direction | Who gets in | What you set up |
|---|---|---|
| Private | You, from your own laptop, phone or server | A device — once per machine |
| Public | Anyone with the address | A domain, then publish a port on the lab |
HTTPS on public domains is automatic — see HTTPS certificates.
VS Code in the browser works with no device and no domain. Add a device when you want SSH or local tools; add a domain when someone else needs to see your work.
Where things live
All of these are under Connectivity in the sidebar, except where noted.
| Page | Use it to |
|---|---|
| My Devices | Register machines, download tunnel configs, reserve addresses |
| My Network | See reserved addresses and the private networks you can use |
| My Domains | Add platform subdomains and your own domains |
| SSL Manager | Check certificates — reached from the SSL badge on a domain card |
| The lab's Preferences | Choose which domains and ports a lab publishes |
In this section
Devices
Manage the machines that reach your labs - status, addresses, configs, keys and limits.
Domains
Add a platform subdomain or your own domain, and attach it to a lab so it is served over HTTPS.
HTTPS certificates
How certificates are issued and renewed for your domains, and how to read and fix them in the SSL Manager.
Publishing ports
Put an app running in your lab on the internet - over HTTPS on your domains, or as a raw TCP port.
Private networks
Reserved addresses, the shared network, and separate private networks for an organization's devices and labs.