Quick start
Boot your first sandbox in 60 seconds.
1
Install + authenticate
npm install -g @kortix/froglet-cli # create a key on the dashboard's API keys page (starts with fl_) export FROGLET_API_KEY=fl_…
froglet auth login --token "$FROGLET_API_KEY" persists the key in ~/Library/Application Support/froglet/config.toml (Linux: ~/.config/froglet/) if you'd rather not export it every shell.
2
Boot a sandbox
$ froglet sb new --template ubuntu-24.04 --size xs --name demo ✓ created demo · id fb7e61a0-…
The sandbox boots from the stock ubuntu-24.04 template in ~1s. Size xs is 1 vCPU / 512 MB / 10 GB.
3
Run a command inside it
$ froglet sb exec demo 'uname -a' Linux fb7e61a0-… 6.6.62 #1 SMP … x86_64 GNU/Linux [exit 0 · 6ms]
Quote the whole command — clap eats stray flags otherwise. Use 'uname -a', not -- uname -a.
4
Tear it down
$ froglet sb rm demo ✓ destroying fb7e61a0-…
rm is final — no orphan resources. To pause and resume instead, use sb stop / sb start.
What's next
- CLI overview — every command, with the same per-resource grouping the README uses.
- TypeScript SDK — same surface, called from Node or the browser.
- Concepts → Sandboxes — sizes, slug vs UUID, lifecycle states.
- Concepts → Templates — including
builds newfrom any Docker image.