Quickstart.

1. Sign up and create a box

Sign up at prized.dev. New workspaces get $30 of free credit, once: the tour has you pick a box size, Nano through Small, and starts it on that credit, no card needed. Each size says how long the credit runs it; a Small, the suggested start, runs about nine days around the clock. Want a bigger box from day one? Pick it on the same step and start its plan; it launches when the payment lands. The box boots while you install the CLI, bills by the hour against the credit while awake, and pauses itself after an hour idle so the credit lasts.

When it does, boxes pause and the dashboard asks you to pick a plan; each plan is priced to run one size around the clock, and paused boxes start again from the dashboard. See Billing.

More boxes later come from the CLI (prized box new) or the dashboard; see Boxes.

2. Install the CLI

The onboarding tour shows you a command with a single-use link in it, in the shape for the machine you are on. Copy that one: it installs the CLI, signs it in, and connects your box, so prized ssh works the moment it finishes. The plain commands are the same installer without the sign-in.

macOS and Linux:

curl -fsSL https://prized.dev/install.sh | sh

Windows, in PowerShell or Windows Terminal:

irm https://prized.dev/install.ps1 | iex

This installs prized, its background daemon, and a managed copy of Mutagen, which powers sync; the CLI then updates itself from signed releases. It works on macOS (Apple Silicon and Intel), Linux (x86_64 and arm64), and Windows 10 1809 or later (x64 and arm64); a few commands are not on Windows yet, and prized mount is macOS-only.

• macOS and Linux install into /usr/local/bin when that is writable, otherwise ~/.local/bin, and add that directory to your shell's startup file; --no-modify-path (or PRIZED_NO_MODIFY_PATH=1) prints the export line instead.
• Windows installs into %LOCALAPPDATA%\Prized\bin, adds it to your user PATH, and needs no administrator rights; PRIZED_VERSION, PRIZED_CHANNEL, PRIZED_INSTALL_DIR, and PRIZED_NO_MODIFY_PATH=1 are its knobs. WSL is Linux: use the curl line inside it.
• Verification. The installer never installs a download it cannot vouch for. It checks the release signature with minisign when that is installed; otherwise it checks the release's checksum file against a digest served with the script itself, which Prized verified against the signature before serving. Pinning a release yourself (--version, or PRIZED_VERSION on Windows) needs minisign.
• Telemetry. Once signed in, the CLI reports command usage, never arguments or file contents; turn it off here.

3. Log in, only if the installer did not

If you used the tour's command, the installer already signed you in and connected your box (its output has ✓ signed in as you@… and ✓ fig connected lines): skip to step 4.

prized login

Your browser opens the dashboard to mint a CLI token; paste it back. The CLI stores it in ~/.config/prized (%LOCALAPPDATA%\Prized on Windows), sets up your SSH identity, and connects your box when your account has exactly one; with several, or none yet, prized setup connects one.

An install link is single-use and lasts 15 minutes; running that command again reports it as expired, which is expected. Upgrade with prized update, not the install link.

4. Set up

prized setup          # asks: auto or manual
prized setup auto     # everything, no questions

One command for the rest, safe to re-run, run on your machine in the folder you want on the box. Setup checks the box connection and repairs what its health check finds (a stopped daemon, a missing SSH Include, a box agent behind your CLI), stopping only on what it could not fix. Then one question: auto brings everything below without asking again; manual asks a yes or no card per step. The report ends with the prized ssh command that connects. The optional parts:

• Project. prized setup myproject creates ~/code/myproject on the box, mirrored to ~/Prized/myproject on your machine. Pass a path (prized setup ~/src/myproject) and one yes or no asks whether to sync it in place; --copy-once, --copy, and --clone answer from the command line. See Sync.
• Environment. Setup scans your machine read-only and asks a few yes or no questions: your shell, the same Python and Node, the CLIs on your PATH, your Docker images, the Postgres you run locally. Installs and secrets default to yes; data defaults to no. Skipped on Windows for now. See Bring your environment.
• Agents. The coding agents found on your machine (Claude Code, Codex, Cursor; --agent chatgpt for the ChatGPT app) sign in on the box after one card, over the SSH tunnel; gh and your git identity go along on their own. See Credentials.
• Session. With one runnable agent picked, setup starts it in a detached tmux session and prints the command that reattaches to it — your terminal stays where it is. --attach opens the session here instead; --no-start skips it.

Then connect any time:

prized ssh      # a persistent tmux session on the box
prized status   # box vitals, sync state, mirrored ports, daemon health

Or let an agent do it

Steps 2 through 4 are one paste into your coding agent: the prompt is on Agent setup.