Priced per engineer who opens pull requests.
Not per person on the team. If someone opened nothing this month, you do not pay for them this month. Running tests and browsers costs real compute, so the heavy work carries an allowance rather than being priced into everybody.
Free
$0 no card, no end date
Open source, and trying it on one private repository
- Unlimited public repositories
- One private repository
- Full assessment with confidence and gaps
- Community support
Where most teams start
Team
$24 $30 per engineer, per month
Saves $72 per engineer per year
The team adopting it through one engineer who is tired of the queue
- Everything in Free, on every repository
- Codebase map and standards citation
- Intent check and blast radius
- Test execution, with an allowance
- Capped browser validation
Enterprise
Talk to us
Organisations with procurement, and a security team with questions
- Everything in Team
- Full browser validation with higher allowances
- Single sign on and detailed permissions
- Custom or metered usage
- Procurement and audit support
What each tier does not include.
The exclusions matter more than the inclusions when you are choosing, so they are in the same table rather than in a footnote.
| Feature | Free | Team | Enterprise |
|---|---|---|---|
| The assessment | |||
| Merge safety position A stated view on whether the change is safe to merge, not a list of findings. | Included in Free | Included in Team | Included in Enterprise |
| Confidence and gaps A confidence level on every finding, and a list of what was not checked. | Included in Free | Included in Team | Included in Enterprise |
| Specialised passes Separate reviews for logic, security, performance and clarity. | Included in Free | Included in Team | Included in Enterprise |
| Tunable confidence threshold You set how certain a finding has to be before it reaches you. | Not included in Free | Included in Team | Included in Enterprise |
| Context | |||
| Codebase map An index of what calls what, so findings are specific to your system. | One repository | Included in Team | Included in Enterprise |
| Standards cited by name Findings name the rule of yours they came from. | Not included in Free | Included in Team | Included in Enterprise |
| Intent check against the ticket Compares what was built against what the ticket asked for. | Not included in Free | Included in Team | Included in Enterprise |
| Blast radius What else the change reaches, across files and services. | Not included in Free | Included in Team | Included in Enterprise |
| Evidence | |||
| Test execution Runs the part of your suite the change affects. | Not included in Free | Included allowance | Custom |
| Tests written for gaps Proposes tests for the parts of the change nothing covers. | Not included in Free | Included in Team | Included in Enterprise |
| Browser validation with recordings Runs the change in your staging environment and records what breaks. | Not included in Free | Capped | Included in Enterprise |
| Failure attribution Determines whether a failure was caused by this change or was already broken. | Not included in Free | Capped | Included in Enterprise |
| Administration | |||
| Single sign on and detailed permissions | Not included in Free | Not included in Team | Included in Enterprise |
| Procurement and audit support | Not included in Free | Not included in Team | Included in Enterprise |
Before you ask.
Is there a free trial, and do you need a card?
The Free tier is not a trial with an end date. It covers unlimited public repositories and one private repository, with no card. Move to Team when you want it on the rest of your repositories.
What counts as a seat?
An engineer who authored at least one pull request in the billing period. People who only read and approve are not billed. If someone opens nothing in a month, you do not pay for them that month.
What happens if we exceed the test or browser allowance?
Usage beyond the allowance is billed as overage rather than cut off mid review, and you are told when you cross the line rather than at the end of the month. Running tests and browsers costs real compute, which is why the heavy work is metered instead of being priced into everyone.
Can we change plans?
Up at any time, effective immediately. Down at the end of the current term. Team is USD 30 per active engineer on monthly billing, or USD 24 per active engineer per month when billed annually, a twenty per cent discount.
How do we cancel?
Uninstall the GitHub App, or ask us. There is no retention call, no notice period, and no clause that makes leaving harder than arriving.
Is this price final?
It is our list price and it is what we will quote you. We are early enough that we are still learning what the browser evidence tier is worth to teams that use it heavily, so if your usage pattern is unusual, say so and we will work it out rather than pretend the table covers every case.
Try it on one repository, free.
The free tier covers unlimited public repositories and one private repository, with no card. If it earns the rest of your repositories, move to Team.
Nothing to host. Reviews begin on the next pull request opened.