Billing, credits and invoices
Settings → Billing is where a workspace admin sees what the workspace would pay, the credits that cover it, each month’s invoice, and the details that go on it. Only admins and platform admins see this page; everyone else sees a short summary and “Ask an admin”.
A workspace starts on the Free plan and is never charged on it. Pick Team or Business and usage is metered daily from the next day; the first invoice comes at month end for what credits did not cover.
The one number you pay for
Section titled “The one number you pay for”Groundrule bills per active contributor: a person who committed to a connected repository in the last 90 days. Repositories, rules, readers and the open-source CLI are never charged.
How the count is made, from CLI 0.20.0: every scan --upload and check --upload carries a contributor digest, one salted SHA-256 hash per distinct commit author on the repository’s default branch in the last 90 days. The workspace counts distinct hashes across its repositories. No email, name or commit reaches Groundrule, and a hash cannot be read back. Until a repository has uploaded with that CLI, its count is estimated from pull-request authors and labelled so on the page; the first upload replaces the estimate. --no-contributors keeps the estimate for a repository.
| Plan | Who it is for | Price |
|---|---|---|
| Free | Up to 5 contributors and 3 repositories, 30 days of evidence | Free, never expires |
| Team | Teams that want hosted checks and the full history | $18 a contributor a month, $15 on annual |
| Business | Compliance exports and AI checks, from 10 contributors | $35 a contributor a month, $29 on annual |
| Enterprise | Invoicing, purchase orders, a signed DPA | Quoted |
Every workspace is billed in USD. Prices exclude taxes your country adds.
The Plan panel
Section titled “The Plan panel”Choose the plan and the Billing period (annual or monthly). Every workspace is billed in USD. The panel says what the plan includes and what each allowance covers: sandbox minutes for hosted checks and an AI allowance, both per contributor per month.
Changes take effect at once; the daily usage line follows from the next day.
Annual terms, invoiced ahead
Section titled “Annual terms, invoiced ahead”An annual plan can be paid a year ahead. Write to hello@groundrule.dev with the contributor count to cover and the start date; Groundrule issues one invoice for twelve months of the annual rate times that count, after your credits, and the Plan panel shows the term: how many contributors are paid ahead and until when.
Inside the term, the daily usage line bills only contributors above the paid count; the hosted-check and AI allowances still scale with the full count, and overages past them bill monthly as usual. The term ends on its date; from the next day every contributor is metered again unless a new term is invoiced.
Credits
Section titled “Credits”Every charge the workspace would pay is deducted from credits first. Credits are granted on application, not automatically.
- Apply for credits opens a short form: company, website, how many people commit in a typical quarter, and what you want Groundrule to do for the team. The company, website and contributor count are pre-filled from what the workspace already knows.
- A person reads every application. We reply by email within three working days.
- The panel shows the current offer, usually launch credits, with the amount and how long they last. The eligibility is a company, not a personal account, with at least one repository connected.
- With a balance, the panel shows what is left, what it was granted as, and when it expires. Credits are spent oldest-expiring first.
- If an application is declined, the note explains why, and you can apply again when something has changed.
Usage this month
Section titled “Usage this month”Active contributors with the per-repository breakdown, hosted-check sandbox minutes against the allowance, AI usage against the allowance, and the projected charge for the month, split into what credits cover and what would be due.
Two caps under Billing details and caps limit what you are willing to pay past the allowances. Set a cap to 0 to stop at the allowance; leave it empty for no cap.
Invoices
Section titled “Invoices”An invoice is written once a month, for what credits did not cover. It carries a number like GR-202610-0001, the net amount, any tax that applies, the total, and a due date 14 days out.
| Column | Meaning |
|---|---|
| Due | Unpaid; the due date is shown |
| Paid | Paid; the date is shown |
| Void | Cancelled by Groundrule; nothing is owed on it. The row is greyed out and has no buttons |
A due invoice has three buttons:
- Pay now opens the payment window in place: cards from anywhere. No card data reaches Groundrule; the payment page is Razorpay’s.
- Download invoice saves the invoice as a PDF, with the seller, your billing details, each charge and credit, tax and totals. Once paid, the same PDF shows the payment.
- Open goes to the hosted payment page, the same link as in the invoice email.
A paid invoice has Download invoice and Download receipt. The receipt is a one-page PDF with the amount received, the date and time of payment, the method (the card’s brand and last four digits), the payment, transaction and order references, who paid and who received it, and the totals with tax.
The invoice email goes to the Billing email under Billing details, or to every admin when that field is empty. The invoice PDF is attached to it. The email that follows a payment carries the receipt and the paid invoice.
Without an online payment page on a deployment, the email says to pay by bank transfer and gives the address to write to.
Billing details and caps
Section titled “Billing details and caps”What goes on the invoice: Legal name, Billing email, Billing phone (with the country code; shown on the payment page), Country as a two-letter code, and Tax ID (VAT, EIN or your country’s equivalent). All are optional; with no legal name, the workspace name is used.
What happens when an invoice stays unpaid
Section titled “What happens when an invoice stays unpaid”- On the due date, nothing changes yet. The invoice is overdue, and the dashboard shows a banner with the date.
- After the 14-day grace period the workspace becomes read-only. Everything stays visible and exportable: rules, scans, check results, evidence, the compliance report and the ledger.
- In read-only mode these are refused with the message “This workspace is read-only until its unpaid invoice is settled”: uploading scans and check results, hosted checks on pull requests (the check reports why, and runs again on the next push after payment), changes to rules, members and settings. Paying the invoice, leaving the workspace and deleting it always work.
- Paying the invoice ends read-only mode at once.
Nothing is deleted at any point.
The ledger
Section titled “The ledger”Every charge, credit and payment, newest first. Charges are positive; credits and payments negative. The same lines are what the invoice is made from, so both sides can check an invoice against them.
Limits
Section titled “Limits”| What | Limit |
|---|---|
| Grace after an invoice is due | 14 days |
| Credit application | One open at a time |
| Invoice payment page | Expires 30 days after the due date; the PDF and the ledger stay |
| Contributor window | 90 days |