Getting started

Step-by-step setup for each plan. Free needs no account.

← Enterprise: choose admin or member

Admin setup · Enterprise

Enterprise Sovereign. Everything in Team, plus identity, isolation and records. Start it yourself; no sales call needed.

  1. 1

    Install brindle

    One command on macOS or Linux. Free to use, no account needed.

    curl -fsSL pawdelta.com/brindle/install | sh
  2. 2

    Sign in to your account

    Connect the CLI to your account so paid features and your settings follow you.

    brindle account login
  3. 3

    Start Enterprise

    Start with the free 7-day trial for up to 10 seats, or pay by card for any number of seats. Already on Team? Upgrade from Settings › Billing and seats; members, budgets and policy carry over. The trial command is brindle account upgrade --enterprise --trial.

    brindle account upgrade --enterprise --trial --seats 10 --org halyard
  4. 4

    Connect SSO

    Verify your domain with one DNS record, then connect Okta, Entra or Google. Members then sign in through it.

  5. 5

    Define roles

    Create roles with exactly the permissions you pick. Each permission unlocks specific pages in the dashboard.

  6. 6

    Choose which agents and models your org can use

    Allow providers and models for the whole org or per role, route models through Bedrock, Vertex, Azure or your own endpoint, and block personal API keys.

  7. 7

    Invite members and split budgets by team

    Give each team a share of the month and let its manager run it.

  8. 8

    Turn on air-gap mode if you need it

    No outside traffic; only models on your network.

  9. 9

    Choose your agents

    Your org's admins choose which agents and models are allowed; brindle only offers those. Sign in to the ones you'll use. brindle doctor shows what's open to you.

    Claude CodeSupervisor (the default) and workers
    claude auth login
    CodexSupervisor or workers; a good second-opinion reviewer
    codex login
    brindle --provider codex
    Google AntigravitySupervisor or workers
    curl -fsSL https://antigravity.google/cli/install.sh | bash
    agy
    Open-weight modelsWorkers and reviewers, on your own machine. Qwen3-Coder 30B needs about 20 GB of GPU memory.
    brew install ollama
    ollama pull qwen3-coder:30b

    How work gets shared out

    The supervisor sizes each task, and brindle sends it to a signed-in agent for that size. Agents that aren't signed in, or are near their usage limit, are skipped.

    LightDocs, renames, simple tests
    MediumA normal feature or bugfix
    HeavyDesign-heavy or cross-cutting work, subtle bugs

    Check what's ready

    brindle doctor

Looking for more?

Guides and next steps that fit this setup.