Getting started

Five minutes from sign-up to a live board. The app does no deploying on its own — it listens to your GitHub activity and shows you what's where.

1. Sign up

Visit the homepage and sign in with GitHub. The first sign-in creates a personal workspace automatically (you can rename or delete it later).

2. Pick a workflow template

When you create a workspace you're shown four templates. Pick the shape closest to how your team ships:

• Single staging — solo / pre-PMF teams shipping from main.
• Multi-slot reservation pool — QA-heavy teams reserving envs per branch.
• Trunk-based + preview — modern trunk teams with PR previews.
• GitFlow — release-train teams with develop and tagged prod.

Not sure? Pick Multi-slot reservation pool — it's the default and covers the most common case. Or pick Blank workspace to define your own envs from scratch.

You can reset to a different template later from Settings → Environments without recreating the workspace.

3. Install the GitHub App

On the Repos page, click Connect GitHub. GitHub asks which account or org to install on and which repositories to grant access to. Pick whatever the slots in your workspace will need to track.

The GitHub App needs at least:

• Contents: Read — to list branches and tags
• Metadata: Read — required by all installs
• Deployments: Read — to receive deployment_status events
• Contents: Read & write — only if you want to create or delete branches and tags from the app (optional but recommended)

See GitHub integration for the full permission list and what each enables.

4. Connect a repo

Back on the Repos page, the installation's repositories appear under Available to connect. Click Connect on the ones this workspace should track. They're scoped to this workspace — another workspace can connect a different set.

5. Bind slots to the repo

Go to Settings → Environments. Each slot has a Repo dropdown. Pick your repo. If you only have one connected repo, the page offers a one-click "Apply to all" button that binds every slot in one go.

Each slot also has a Pattern — the branch name, tag name, or deployment environment it tracks. The template you picked seeded sensible defaults; tune them if needed. See Trigger patterns for the syntax.

6. Watch the board

Open the workspace dashboard. Push to a tracked branch (or create a tracked tag) and the matching slot card updates in real time. The status flows:

Empty → Deploying → Available / In QA / QA-OK / Broken

The status list is workspace-configurable at Settings → Status workflow. You can also override a status manually from any board card — useful for "this slot is broken" or "QA-Bob owns this".

What's next

• The board — what each slot card means.
• Trigger patterns — the full pattern syntax.
• FAQ — does it deploy for me? (no), monorepo support, reservations.