yourspace, the binary

The yourspace binary is real. Download the prebuilt binary for your platform from /docs/install, then run yourspace setup from your project directory to walk through naming your site, saving an API token, and your first deployment.

What you can run

$ yourspace deploy
packed 12 file(s), 4.8 KB — uploading to https://api.yo.urspace.net …
deployed my-site (v3) at https://my-site.yo.urspace.net

Eleven subcommands clustered into four jobs:

Update (2026-06): the command surface has grown since this launch post — update, rollback, and token have joined the customer commands. The CLI reference is the current source of truth for the full set.

The full reference lives at /docs/cli. One worth calling out: yourspace doctor runs a state checklist (token? config parseable? build output present? API reachable? site name available?) and reports each as OK / Warn / Fail / Skip. When a deploy fails for an unobvious reason, doctor is usually the fastest way to find out.

Flag conventions

POSIX. Long forms with a double-dash, short aliases with a single. Both parse identically; joined shorts work too:

yourspace logs --tail 200 --since 15m --json
yourspace logs -n 200 -s 15m -j
yourspace logs -n200 -s15m -j

Letter-to-meaning is consistent across commands where it can be: -n is --tail for logs (per the head/tail -n convention) and --name for init; -y is --yes; -d is --dist; -j is --json on every command that emits structured output. --dry-run, --yes-really-delete, and --yes-really-remove are long-only — destructive operations have no one-letter shortcut.

What --help looks like

--help names positional arguments, not just flags:

$ yourspace logs --help
Usage: yourspace logs [<site-name>] [flags]

Flags:
      --api string   API base URL ...
      --dir string   project directory ...
  -j, --json         print the raw server response as JSON
  -s, --since 15m    only return entries newer than this ...
  -n, --tail int     number of recent log entries to fetch ...

The [<site-name>] makes the optional positional discoverable from --help alone — no need to dig through the docs to learn that yourspace logs my-blog works from any directory.

Errors are flat. A 401 on token validation reads:

$ yourspace deploy
error: token rejected: invalid token
hint: your token may have expired or been revoked — run `yourspace login` to refresh

— one line of context, one line of recovery.

Try it

The fastest path through is the Quickstart: a short walkthrough from "I have a static site" to "it's serving at <name>.yo.urspace.net." The full CLI Reference covers every command, flag, and environment variable.

If you've already got a project with a build output, yourspace setup from inside it is the one-command shortcut: init + login + deploy in one walk, with retry on a bad token paste and pre-flight warnings if your build dir is empty.