Plans and limits
What each plan costs and includes, what a pull request check and an AI credit pay for, how the Teams seat pool works, and what happens at a limit.
This page tells you what each plan costs, what it includes and where its limits sit, so you can pick one and predict what a month of work uses.
What each plan costs
Prices are in USD and exclude tax. An annual plan is charged once for the year; the monthly figure beside it is what that works out to each month, and annual billing saves 10%.
| Plan | Monthly | Annual | Members |
|---|---|---|---|
| Free | $0 | $0 | 1 |
| Pro | $11.99 | $129.48 a year, which is $10.79 a month | 1 |
| Teams | $9.99 a seat | $107.88 a seat a year, which is $8.99 a seat a month | Unlimited (3 minimum) |
| Enterprise | By contract | By contract | By contract |
The smallest Teams subscription is 3 seats, so Teams starts at $29.97 a month or $323.64 a year.
Pro and Teams carry a 7-day free trial, with a card taken up front and one trial per workspace. The trial carries the plan's full allowance.
Enterprise is sold by contract. Seats, checks and credits are set in the contract, and there is no self-serve price. Email hello@spectrace.io to talk about it.
What each plan includes
| Allowance or limit | Free | Pro | Teams | Enterprise |
|---|---|---|---|---|
| Pull request checks per month | 10 | 60 | 50 per seat, shared | By contract |
| AI credits per month | 100 | 1,000 | 1,000 per seat, shared | By contract |
| Members | 1 | 1 | Unlimited (3 minimum) | By contract |
| Projects | 2 | Unlimited | Unlimited | Unlimited |
| Repositories per project | 1 | Unlimited | Unlimited | Unlimited |
Every plan, Free included, carries:
- GitHub pull request verification and GitLab merge request verification, within the check allowance.
- Extraction, acceptance criteria and test generation, within the credit allowance.
- The VS Code extension.
- GitHub Issues sync.
- Export in every format.
- Roles and permissions, which work the same on every plan.
- Audit recording, with the Activity and Requirement history views.
- Email support.
Pro adds Cycles for sprint planning, the MCP server that lets an AI coding agent read the spec, Jira sync, Linear sync, unlimited projects and unlimited repositories per project.
Teams adds the Audit view and export, Slack, team insights in Cycles, and any number of members.
What a pull request check is
A check covers up to 20 changed code files and 80,000 characters of their changes. Each push that gets a fresh verdict uses a check. A pull request past either limit is split into several runs and costs one check for each, up to 4 for a single verdict.
These runs cost no check:
- A push that reuses the previous verdict because nothing the verifier reads changed.
- A pull request that matches no requirement.
- A run excluded by the project's path filters, or one whose diff contains no code files.
- A run superseded by a newer push.
- A run that fails before it reaches a verdict. A retry of the same run is never counted twice.
- A second run on a commit that was already charged, such as a duplicate trigger or an edit to a merge request description.
Re-verify, inline verification from an AI agent over MCP, and GitLab merge requests all use checks. See How PR verification works for the mechanics.
What an AI credit pays for
A credit pays for the AI work that is not verification: extraction, acceptance criteria, test generation, analysis, import and enrichment. One credit is one action, whatever that action costs to run, and the same action draws the same credit in the web app, in the VS Code extension and over MCP. Semantic search, the suggestions offered while you write, and the progress hints the VS Code extension sends draw nothing. See AI credits for the full table.
How the Teams seat pool works
Every workspace member is billed as a seat, with a minimum of 3. A seat is a member, or an invite that has been sent and not yet accepted, revoked or expired. Spectrace sets the quantity from the workspace itself and resynchronises it whenever an invite is sent, accepted, revoked or expires, and whenever a member leaves. Neither Checkout nor the billing portal offers a seat picker.
Checks and credits are counted per seat and pooled across the workspace, so a Teams workspace of 4 seats has 200 checks and 4,000 credits a month for everyone in it to share, and a 3-seat workspace has 150 checks and 3,000 credits.
Free and Pro are sold as one-member plans, and Teams is the plan that carries more than one member. Inviting a second member is not blocked today, so a Free or Pro workspace that invites one is asked for nothing and keeps working. See Seats on the Teams plan.
When allowances reset
Checks and credits reset on the 1st of each month, UTC, on every plan, annual plans and trials included. The reset date comes from one shared helper rather than from the subscription's billing period, so an annual plan resets monthly like any other. Settings → Billing shows what the workspace has drawn so far, its allowance and the reset date.
What happens at a limit
Nothing is billed as overage. A limit stops the work instead of charging for it.
- Checks. Verification stops until the allowance resets. The run is recorded as
limit_reached, the check run concludes neutral with the reset date in its title, and an existing Spectrace comment is edited to say that nothing was verified at that commit. A commit that already has a verdict keeps it. A verdict is never cut short part-way, so the run that takes the last check finishes and a workspace can end the month up to 3 checks over its allowance. - Credits. An action you start refuses with a message naming what it needed and what is left, and nothing is charged. Background work records itself as skipped with the reason and leaves the requirement as it was, so it can run later with nothing to undo.
- Projects. Creating one past the plan’s limit is refused, with a message naming the limit. The repository and member counts in the table above are what each plan is sold with; neither is enforced at the moment, so going past one is not refused.
- A feature the plan lacks. The action is refused with a sentence naming the plan that includes it.
Upgrading
Every upgrade prompt names the cheapest plan that includes what you reached for, and opens the plan picker in Settings → Billing with that plan chosen. You pick monthly or annual billing there, and the picker shows the amount and when it is charged before you confirm. Connecting Jira, Linear or Slack on a plan that lacks it ends with the same upgrade offered beside the refusal. Until paid plans open, no upgrade prompt, button or link is shown.
The sidebar's Account section shows Upgrade to owners and admins of a workspace on Free, and it opens the same picker with Pro chosen. Everyone else sees Billing, which opens Settings → Billing.
A workspace already on a paid plan opens the same picker from Change plan. A change of plan keeps the billing cycle unless you choose annual, and an annual plan stays annual. Teams moves to Pro only once the workspace is down to one seat, so remove the other members and cancel any open invites first.
Only owners and admins can upgrade, change or cancel a plan; members see Settings → Billing read only.