forge

verified milestones, live in your clan's terminals

Your clan sees what you actually shipped.

Forge is a terminal sidebar for small groups of founders. Progress bars only move when a milestone is verified through GitHub, Stripe, or a live uptime probe. Nothing is self-reported.

curl -fsSL https://forge.thecamelclub.co.uk/install.sh | sh

01 · quickstart

Up and running in four commands

The installer clones the repo, builds the CLI, and puts forge on your PATH. Requires Node 22+, pnpm, and git.

  1. Install the CLI

    One line. Inspect it first if you like: it only touches ~/.forge and ~/.local/bin.

    curl -fsSL https://forge.thecamelclub.co.uk/install.sh | sh

  2. Sign in with GitHub

    Opens your browser once. Forge asks for repo access so it can verify merges and CI, never to write code.

    forge login

  3. Register your project

    Run inside your project repo. Links the GitHub origin and installs a post-commit hook that keeps the sidebar warm.

    forge init

  4. Open the sidebar

    Best in a split terminal pane. It pins to the top right, updates live, and works offline with last-known state.

    forge

02 · the point of it

Clans: 2 to 6 friends, one shared feed

A clan is a small invite-only group. Everyone's verified milestones print in everyone's terminal within seconds. Rows sort alphabetically, there is no ranking, and live numbers like MRR stay private to the owner.

  1. Create your clan

    Prints a one-time invite code.

    forge clan create night-shift

  2. Send friends this page

    They install with the same one-liner up top, then join with your code.

    forge clan join <code>

  3. Check in weekly, ask how

    forge checkin is a three-field weekly ritual. When a clanmate hits a milestone, forge how sarah revenue2 shows the verified evidence and the story behind it.

    forge how sarah revenue2

03 · how bars move

Milestones fire from evidence, not claims

Each vertical is a ladder of rungs. Every rung names its verification source, and each fired milestone is a permanent dated event you can inspect with forge how. Connect sources as you need them: forge connect stripe, forge connect deploy, forge connect domain.

Build

via GitHub
  • Repo connected, first commitGitHub OAuth
  • First merged PRGitHub OAuth
  • CI passing on default branchGitHub OAuth

Ship

via probes
  • Deployed URL live with SSLPlatform probe
  • Custom domain verifiedDNS TXT challenge
  • Publicly launchedRegistry lookup

Revenue

via Stripe
  • Payments connected, checkout liveStripe
  • First dollar: first successful chargeStripe
  • First 10 customersStripe

Commits only gate Build rung 1, because commits are easy to fake. PRs, CI, probes, and charges gate everything else. Stripe access uses a restricted read-only key you create yourself.

04 · boundaries

What Forge sees, and what it never does

Forge stores milestone events, not your code and not your numbers. GitHub access verifies merges and CI. Stripe access is a read-only restricted key. Your clan sees that your first charge happened, never the amount, and live metrics stay owner-private. Uninstall by deleting ~/.forge, ~/.local/bin/forge, and the post-commit hook in your repo.

05 · start tonight

Ship with your friends watching.

One command to install. One code to join a clan. The next milestone that fires could be yours.

curl -fsSL https://forge.thecamelclub.co.uk/install.sh | sh