Getting started
Step-by-step setup for each plan. Free needs no account.
Admin setup · Enterprise
Enterprise Sovereign. Everything in Team, plus identity, isolation and records. Start it yourself; no sales call needed.
- 1
Install brindle
One command on macOS or Linux. Free to use, no account needed.
curl -fsSL pawdelta.com/brindle/install | sh - 2
Sign in to your account
Connect the CLI to your account so paid features and your settings follow you.
brindle account login - 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
Connect SSO
Verify your domain with one DNS record, then connect Okta, Entra or Google. Members then sign in through it.
- 5
Define roles
Create roles with exactly the permissions you pick. Each permission unlocks specific pages in the dashboard.
- 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
Invite members and split budgets by team
Give each team a share of the month and let its manager run it.
- 8
Turn on air-gap mode if you need it
No outside traffic; only models on your network.
- 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.
CodexSupervisor or workers; a good second-opinion reviewercodex login brindle --provider codexGoogle AntigravitySupervisor or workerscurl -fsSL https://antigravity.google/cli/install.sh | bash agyOpen-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:30bHow 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 testsMediumA normal feature or bugfixHeavyDesign-heavy or cross-cutting work, subtle bugsCheck what's ready
brindle doctor
Looking for more?
Guides and next steps that fit this setup.
Air-gap mode, the signed audit trail, managed models and remote shutdown.
Read the docs →DocsConfigurationPer-repo settings: merge checks, reviewers, routing by task weight and more.
Read the docs →GuideMilestone checks for autopilotWrite checks that let agents run until the work is really done.
Read the guide →