Booths
Loading projects...
CodingBoothScan the QR code with an authenticator app, or enter the key manually.
CodingBoothTracked resources. Active items that linger may indicate a stuck or failed operation.
Loaded with resources above.
Manage available booth CLI versions. The "latest" version is used for new bare projects. Registering a version auto-triggers AMI builds for all variants.
A run that never reports ready is shut down once it has been alive this long, so a booth that fails to start can't burn credit unattended. Applies platform-wide, to every tenant. Note that a booth with no cached AMI compiles its image on the instance — Boothfiles that build tools from source (rust, haskell) can take 20–30 minutes to reach ready, so a limit near 30 will stop some legitimate first runs. Raise it if that becomes common.
Assign system roles to users. Role changes take effect on the user's next sign-in.
Add-only: to change a price, add a new row with a later start date. Earlier rows stay as history (historical runs bill at the rate in effect on their run date).
Manage storage pricing tiers. Tiers are evaluated in sort order. Use price/GB = -1 for "contact us" tiers.
Signup credit. A code can be redeemed once per account, and each account can redeem one code ever. Max uses of 0 means unlimited; leave the expiry blank for no expiry. Disabling a code stops new redemptions and leaves credit already granted alone.
Per-GB egress charge. v1 applies only to desktop variants (xfce, kde, lxqt, wayland) — others ship JSON, not pixels, and are absorbed by compute price. Updates create a new dated rate; older rows stay as history.
Each link is a throwaway account with a booth already seeded and a prefunded wallet — click it, no sign-up, no password. "Claimed" means the guest signed up for real and their trial booth's files (including anything never committed) were copied into that new account.
People who signed up on the marketing site. "Account" says whether that email has since registered here — matched on the address they signed up with, so someone who registered with a different address shows as "no".
All tracked resources. Active items and recent items from the last 30 days.
.booth/ folder yet, run with "Writable .booth folder" option,
then run ./booth config inside to set it up.
.booth/ folder yet, you'll be asked to Configure it first.
git status) first..booth/config.toml in charge.. _ -; spaces become hyphens.-p inside the booth (host port in parentheses). Public Expose is the port on the run hostname — change it to remap, including 443. Open puts it on the internet; HTTPS wraps HTTP (leave HTTPS off for Postgres). Public ports must not collide. Booth UI defaults to 443.
.booth/ is mounted read-only inside the booth.BOOTH_STARTUP. One line..booth/egress/allowlist.txt; created on first use). Unchecked leaves config.toml in charge. Booth 0.57.0+.Pin this booth to a specific booth-CLI version. Saving will re-bake the AMI on the next run.
Sync the latest saved snapshot with your Git remote. The booth must be stopped.
git push inside the booth.
Default credentials shared across all booths. Individual booths can override the Git token during import, and the password from each booth's Run Settings.
Your defaults for all booths. Leave blank to use platform defaults (10 min / 1 min). Per-booth and per-run overrides take precedence.
Your default for new booths. Pre-builds a bootable image after each run for faster starts; uses extra storage. Booths can override this individually in their Settings.
The password for this account — not the "Booth Password" field, which is what you type to open a running booth.
Optional extra sign-in step. After you turn this on, email + password sign-in asks for a 6-digit code from an authenticator app.
Pick a username for your account. This will be used in URLs, API paths, and the CLI.
To import Git repositories, you'll need to set up your Git credentials (personal access token).
You can always do this later from Settings.
This booth doesn't have a configuration yet (no Boothfile or config.toml).
Configure it first — this opens an interactive terminal to set up the booth variant and settings.
Creates a new repository under your account, pushes this booth's current content as the first commit, and switches the booth to git-backed — save-back pushes there from then on.
Pushes this booth's current content as the first commit into a repository you already made, and switches the booth to git-backed — save-back pushes there from then on. The repository must be empty (no README, no .gitignore, no licence). To adopt a repo that already has commits, use + Git Repo on the booth list to import it instead.
A desktop variant runs a full graphical session — window manager, compositor and usually a browser — on top of your own work. Below it stays usable but feels sluggish: slow window redraws and laggy typing.
You are billed per minute, so a bigger machine that you use for less time is not necessarily more expensive. You can change this any time in Settings.
A booth's image is compiled on the instance the first time it runs, then cached as an AMI. Expect several minutes — up to 20–30 for Boothfiles that build tools from source (rust, haskell). Later runs reuse the cached image and start in about a minute.
The instance is billed for that time. You can leave this page open — the booth card shows progress and the link appears once it's ready.
You will be redirected to Stripe to complete payment. Credit is added to your account after payment confirms (usually within a few seconds).
Apply a manual ledger adjustment. Use a positive amount to credit, negative to debit. Reason is recorded in the transaction log.