How licensing works
Bravos is one npm package. The same code runs on every machine, and what it will do depends on the licence the machine holds. With none, it is on Free. Signing in is optional: Free needs no account.
Free and Team plans
Section titled “Free and Team plans”| Plan | Unlocked |
|---|---|
| Free (researcher) | one person researching their repositories, each on its own and with no limit on how many: context, annotate, templatize, env, prove, recheck, report and watch, including the threat-model and authorized testing loop. No licence, no account |
| Team, per developer (Solo is one seat) | everything on Free, plus the pre-PR gate and autopilot, the CI and nightly workflows, scheduled upkeep, multi-repository workspaces, campaigns, SAST and the code graph |
bravos account activate starts a 30-day Team trial, with a free account and
no card, when your account has no plan. Using Free separately in several
repositories does not link them; linking them is the Team workspace feature.
Prices are on account.bugb.io/pricing.
The session banner states Free, Team trial with days left, Team with seats,
or expired. Free labels the graph graph locked; bravos next and the
briefing state the plan and offer the free research steps first. The
dashboard threat-model tab works on
Free, with its Code graph tab locked until Team is active.
How a machine gets its licence
Section titled “How a machine gets its licence”bravos account activate signs you in once in the browser and writes the
licence to ~/.bravos/licence.jwt (or $BRAVOS_HOME). An account with no plan
gets a 30-day no-card Team trial. bravos account import FILE installs a
licence downloaded from
account.bugb.io/dashboard/license
instead. The guided setup offers the same sign-in, and you can skip it. See
Install Bravos.
On a team plan the licence is yours and this machine’s. An owner or admin
assigns you a licence, and each machine you activate gets its own
short-lived token, which Bravos renews at session start and before a paid
command. bravos account devices lists your machines, bravos account revoke ID
signs one out, and bravos account logout signs this one out. Removing you
from the team, or taking your licence back, stops every one of your machines
at its next renewal.
In CI, the BRAVOS_LICENCE secret holds a CI licence an owner or admin creates
for that repository. The CLI never renews a licence that comes from the
environment.
Local verification and device renewal
Section titled “Local verification and device renewal”The licence is a signed token, and Bravos checks the signature on the machine against a public key it carries. Every time a paid feature runs it checks again. A signed-in device can also renew its licence through the account portal; local signature verification and device renewal are separate operations.
bravos licencePlan: Team (trial, 23 days left) — everything is unlocked until 2026-12-10 · https://account.bugb.io/pricing to keep itLicence: $BRAVOS_LICENCE (key bugb-license-2026a) tier team · 1 seat · expires 2026-12-10 (trial) · features sastUnlocked: the pre-PR gate, CI and nightly workflows, scheduled upkeep, multi-repository workspaces, campaigns, SAST, the code graphThis capture uses a Team trial supplied through BRAVOS_LICENCE; a signed-in
machine names its licence.jwt instead. The days left and dates are the
trial’s own.
bravos licence --json | jq '{schema, state, tier, seats, licensed, unlocked, locked}'{ "schema": "bravos.licence/v1", "state": "valid", "tier": "team", "seats": 1, "licensed": true, "unlocked": [ "pre-pr", "ci", "schedule", "workspace", "campaign", "sast", "codegraph" ], "locked": []}The command uses jq to select the fields shown. The full document also
carries expiry and grace times, trial details, the licence id, issuer and the
reason for any refusal. It leaves out the account id.
Grace after expiry
Section titled “Grace after expiry”After expiresAt, a licence keeps working for a grace period of 14 days or a
quarter of its term, whichever is shorter. A one-year licence gets 14 days. A trial gets no grace: it ends on its last day.
When a licence has expired past its grace, the machine is back on Free. Nothing in the repository is removed. The threat model, the annotations and the evidence stay where they are.
What a Team feature does without a licence
Section titled “What a Team feature does without a licence”-
A command or flag says what it would do and how to start the trial, and changes nothing:
bravos setup --ci needs a licence — it is on the Team plan: bravos account activate starts a 30-day trial (no card), or https://account.bugb.io/pricing -
A hook stands down with one line and never blocks.
-
A skill stops at its first step and says so.
Code graph access
Section titled “Code graph access”On a machine with no licence, this command refuses before building:
bravos graph build .bravos graph build needs a licence — it is on the Team plan: bravos account activate starts a 30-day trial (no card), or https://account.bugb.io/pricingThe code graph and SAST are paid. The account portal offers a 30-day no-card trial.
Two binaries come only through the licence
Section titled “Two binaries come only through the licence”The SAST analyzer and the code graph binaries are not on any public index.
bravos setup asks account.bugb.io for a short-lived
download link with the machine’s licence, and checks each file against Bugb’s
signature before unpacking it under ~/.bravos. A machine with no licence gets
no link. Every paid feature also checks the licence on the machine each time it
runs.
A licence names its seat count. Seats are licences an owner or admin assigns in the account portal.

