Free while it's in beta. Including the part where we tell you what it will cost.
There is no card form on this site and no billing wired to it. Every repository connected today is reviewed at no charge, and will be until we say otherwise — in an email, before it applies, not on an invoice.
Today
One number, and it is the honest one.
$0
Every repository, every pull request, every plan. Nothing is metered, nothing expires, and there is no trial to run out.
If you install during the beta, you keep your access. When there is a price, the repositories you already have connected are not the ones it starts with. We will tell you what changes and when, and you will hear it from us first.
A billing problem will never block a merge. The check run BlastRadius posts can fail your build for exactly one reason — your plan destroys data — and an unpaid invoice is not that. If a subscription ever lapses, the reviewer stops commenting. It does not start blocking.
What we intend to charge, when we charge
Written down now because deciding whether to put this in your CI is deciding whether you can afford it in a year. These are intentions, not a price list — there is nothing to buy, and the line between the two tiers is genuinely not settled.
Team
$99 / repository / month
Intended. Not yet charged.
The product as it stands: every rule, one comment, one check run.
- Severity-ranked review on every pull request
- The merge gate, and your own policy in
.blastradius.yml - Findings kept for 30 days, then deleted
Organisation
$249 / repository / month
Intended. Not yet charged, and not yet built.
For repositories where the review has to satisfy somebody other than the person merging.
- Policy set once for an organisation rather than per repository
- A longer window on what was found and what was overridden
- Single sign-on, and a support commitment in writing
None of the second tier exists yet. It is listed because it is what we expect the difference to be, and a pricing page that hid the fact that the expensive tier is unbuilt would be the first thing you found out we were wrong about.
What we will not do
Three shapes of pricing that would make this a worse reviewer. Saying so now is cheap; saying so after we have shipped one of them is not.
- Charge per plan, per finding, or per comment. The pull request you most want reviewed is the enormous one, and metering the review is how a team learns to skip it on exactly those. The price should not move when your terraform does.
- Put the merge gate behind the paid tier. The check run is the product. A reviewer that will tell you your database is being destroyed but only block the merge if you upgrade is not a safety tool, it is a hostage.
- Charge per seat. Adding a reviewer to your team should not cost more, because a review nobody is looking at was worth nothing. What we do costs us per plan, and per repository is the closest honest proxy for that.
Questions this page ought to answer
- When does billing switch on? When enough people have installed it that the answer matters, and not before. Nothing is scheduled, and this page changes when it is.
- Will open-source repositories be free? That is the intention and it is not a commitment yet. Ask, and it will be answered in a sentence rather than with a form.
- What happens to my data if I never pay? The same thing that happens now: findings are deleted after 30 days, and uninstalling deletes everything we hold for you immediately. Billing does not change either.
- Can I get an invoice, a DPA, a security review? Ask. There is no self-serve version of any of those yet, which is the honest state of a private beta rather than a policy.