Pricing · per active contributor

Pay per person whose code the rules shape. Never per rule.

One number to understand: the active contributor, anyone who committed to a connected repository in the last 90 days. Repositories, rules, readers and the open-source CLI are never charged.

§ 01the plans

Per active contributor, per month. Annual billing shown first; monthly is a little more.

Five plans. Three of them cost nothing.

Open source

The CLI on its own. No account.

Free, alwaysno account, no limits
  • Rules in the repository, from the packs or your own
  • AGENTS.md, CLAUDE.md, Cursor and Copilot files from one command
  • Deterministic checks, locally and in CI
  • Hooks and the MCP server for coding agents: action policies before each tool call, the check when the agent finishes
  • Exceptions, overrides, SARIF and Markdown reports
  • Apache-2.0; works offline forever
Install the CLI
Free

A workspace for a small team.

$0up to 5 contributors
  • Everything in Open source
  • One rulebook across up to 3 repositories
  • The review inbox and rollout stages
  • 30 days of scan evidence
  • Groundrule for GitHub: results on the pull request
  • Up to 5 active contributors
Create a workspace
Business

Evidence for auditors, checks without CI.

$29per active contributor · monthminimum 10 contributors
  • Everything in Team
  • Compliance exports: SOC 2 and ISO 27001 mappings, pass rates per control, CSV
  • Signed check results, verified on every run
  • Hosted checks: 500 sandbox minutes per contributor a month
  • AI checks on hosted pull requests; $5 of AI usage per contributor a month
  • Priority support, by email, from the engineers
  • Single sign-on and an audit logplanned
Talk to us
Enterprise

For procurement, not for features.

From $20,000 a yearannual, invoiced
  • Everything in Business
  • Annual invoice, purchase order, bank transfer
  • A signed data processing agreement
  • Custom retention and allowances
  • A named contact and a shared channel
  • SCIM, a service level agreement, hosting outside the United Statesplanned
Talk to us

The Free workspace is not a trial: it never expires. All prices are in USD and exclude taxes your country adds. Items marked planned are announced, not yet built.

§ 02which plan fits

Answer five questions. The answer updates as you go; nothing is sent anywhere.

Find your plan in a minute.

The recommendation uses the same rules a person here would use, and says why. It is a starting point, not a contract.

03 · Do you want a shared rulebook, an inbox and rollout stages?Or is a rulebook inside each repository, run by the CLI, enough for now?
04 · Which of these do you need?
05 · Does procurement need any of these?
§ 03what counts

One metric, two allowances. Everything else is unlimited.

03.1 · the only thing you pay per

An active contributor

Anyone who committed to a connected repository in the last 90 days. Counted from the scans and check results the workspace already receives; never assigned by hand. Counted once a month; the invoice follows it up or down.

03.2 · metered, with an allowance

Hosted-check minutes and AI usage

Both cost us money per use, so both carry an allowance per contributor and a visible meter. Past the allowance: $0.05 a sandbox minute, and AI at the price the usage ledger shows. An admin can cap either at zero.

03.3 · never charged

Repositories, rules, readers, the CLI

Connect as many repositories and adopt as many rules as you like. Members who read the rulebook without committing are free. The open-source CLI, packs, checks, hooks and MCP server are free with or without a workspace.

Metered usageFreeTeamBusinessPast the allowance
Hosted-check sandbox minutes, per contributor a month–200500$0.05 a minute
AI usage, per contributor a month–$2$5At cost, as the usage ledger shows; never more than $0.50 for one hosted AI check

A typical hosted check takes under ten seconds. 200 minutes is about 1,200 pull-request checks per contributor a month.

§ 04side by side

Every row is true of the product today unless it says planned.

Everything, in one table.

FeatureOpen sourceFreeTeamBusiness
Rules and agents
The catalog: every pack and standard✓✓✓✓
Agent files: AGENTS.md, CLAUDE.md, Cursor, Copilot✓✓✓✓
Hooks: action policies before each tool call, the check when the agent finishes✓✓✓✓
MCP server, local✓✓✓✓
MCP server, hosted at mcp.groundrule.dev–✓✓✓
Your own standards, exceptions, overridesIn the repositoryIn the workspaceIn the workspaceIn the workspace
Rollout stages: Observe, Teach, Advise, Enforce–✓✓✓
Stages and severity per team or repository––✓✓
Repositories and people
RepositoriesUnlimited3UnlimitedUnlimited
Active contributorsUnlimited5UnlimitedUnlimited, minimum 10
Members who only read the rulebook–FreeFreeFree
Teams, seven roles–✓✓✓
API tokens–52525
Evidence and review
Scans: what the code already followsIn the terminal30 days keptFull historyFull history
The review inbox, proposals from agent files, lint settings, CODEOWNERS–✓✓✓
Promotion suggestions from scan history–✓✓✓
Document and Notion or Confluence imports–✓✓✓
Rules from pull-request review comments (Groundrule for GitHub)–✓✓✓
Dashboard: where violations are stopped–Last 30 days✓✓
Pull requests
Check in your CI, results uploaded to Pull requestsCheck only✓✓✓
Groundrule check posted on the pull request–✓✓✓
Hosted checks without CI (sandbox minutes per contributor a month)––200500
Signed results, verified on the run's pageVerify offline✓✓✓
Compliance exports: SOC 2 and ISO 27001 mappings, CSV–––✓
AI
Describe a rule, find rules in documents (usage per contributor a month)––$2$5
AI checks on hosted pull requests, advisory–––✓
Zero-data-retention mode–✓✓✓
Support and procurement
SupportCommunityEmailEmailPriority email
Single sign-on, audit log–––Planned
Invoice, purchase order, bank transfer, DPA–––Enterprise

Enterprise is Business plus procurement: invoice, purchase order, bank transfer, a signed DPA, custom retention and allowances, a named contact. SCIM, an SLA and hosting outside the United States are planned.

§ 05credits

Granted on application, spent before anything is due. The way cloud providers do it.

05.1 · what

A balance that pays first

Every charge a workspace would pay is deducted from its credits before anything is due. The billing page shows the balance, what used it and when it expires. Credits are not automatic: a workspace admin applies from Settings → Billing, a person reads every application, and we reply by email within three working days.

05.2 · launch credits

$500, valid 12 months

The standard grant for an approved application: enough for a team of ten on Team for about three months, long enough to see the dashboard fill with evidence. For a company, not a personal account, with at least one repository connected. Teams that commit to feedback calls and a reference can ask about design-partner credits.

05.3 · when they run out

You hear first

An admin gets an email at 20% of the balance and again when it is gone. Then the next month's invoice covers what the credits did not.

§ 06billing

How and when you are charged.

06.1 · when

The day you pick a plan

A workspace starts on Free, which is never charged. Billing begins the day an admin picks Team or Business on Settings → Billing: usage is metered daily from then, and the first invoice comes at month end for what credits did not cover. Switching back to Free stops the meter from the next day.

06.2 · how

One invoice a month, in USD

Usage is metered daily from your contributor count. Once a month, an invoice covers what credits did not, with a PDF, a payment page that takes cards from anywhere, and 14 days to pay. Every invoice is in USD; prices exclude taxes your country adds. Annual plans use the annual rate, and can be invoiced a year ahead for an agreed contributor count; Enterprise can also pay by bank transfer. Unpaid after 14 days, a workspace is read-only until it is settled; nothing is deleted.

06.3 · leaving

Everything stays yours

Open-source projects stay on Team for free. Your standards are YAML in an open format and the agent files are plain text; you can leave at any time with everything.

§ 07questions

The ones teams ask before they would pay.

When does billing start?

A workspace starts on the Free plan, which never expires and is never charged. Billing begins the day an admin picks Team or Business on Settings → Billing: usage is metered daily from then, and the first invoice comes at month end for what credits did not cover.

What is an active contributor, and how do you count it?

Anyone who committed to a repository connected to your workspace in the last 90 days. The CLI counts it from the repository's own history when it uploads a scan or a check result: one salted hash per commit author, never a name or an email, so nobody can be read back and nobody is assigned a seat by hand. Reviewers, managers and people who only read the rulebook are free.

What are credits, and how do we get them?

A balance that pays before anything is due, granted on application. A workspace admin applies from Settings → Billing; the form is three questions and is pre-filled from what the workspace already knows. Launch credits are $500 for 12 months, for a company with at least one repository connected. A person decides, and replies within three working days.

What happens if we don't pay an invoice?

You have 14 days. During them nothing changes. After them the workspace is read-only: everything stays visible and exportable, but uploads, hosted checks and changes to rules wait until the invoice is paid. Nothing is ever deleted for non-payment.

Why not per repository, per rule or per line of code?

Each of those punishes the thing we want you to do: split repositories sensibly, adopt more rules, write more code. The number of people whose code the rules shape is the honest measure of what Groundrule does for you.

What happens when our contributor count changes?

Usage is metered every day from the count, so the invoice follows it up or down within the month. A contractor who committed once in June and never again drops out of the count in September.

What if we go over a hosted-check or AI allowance?

You see it coming: the billing page shows the month's usage against the allowance, and an admin gets an email at 80 percent. Past it, hosted checks cost $0.05 a sandbox minute and AI usage is billed at cost, as the usage ledger already shows it. An admin can cap both to zero.

Can we use the CLI without paying anything, ever?

Yes. The CLI, the packs, the checks, the hooks and the MCP server are open source under Apache-2.0 and work with no account. A repository on the Free or Team plan can leave the workspace with one line removed from its configuration, and keeps everything it had.

Which currency will we be billed in, and how do we pay?

Every invoice is in USD. Each one comes with a PDF and a payment page that takes cards from anywhere. Enterprise can pay by bank transfer against an invoice. Prices exclude taxes your country adds.

Do open-source projects pay?

No. A workspace whose connected repositories are all public under an OSI-approved licence stays on the Team plan free of charge. Write to us with the links.

Is Business only about compliance?

Mostly. Team has every feature a team needs to roll rules out. Business adds what an auditor, a security lead or a platform team asks for: the compliance exports, larger hosted-check and AI allowances, AI checks on pull requests, priority support, and single sign-on once it ships.

∎ · sign-off

Start free. Decide later, with the numbers in front of you.

Create a workspace, connect one repository and let the scans run. By the time billing starts you will know how many people the rules reach, what the checks stopped, and whether Team or Business is the one for you.