Terms of service. Short, because the product is small and free.
Last updated 24 August 2026. These are a founder’s terms written from a template, not a law firm’s, and this page says so rather than pretending otherwise.
What you are agreeing to
Installing the BlastRadius GitHub App, or uploading a plan to it, means these terms apply between you and whoever operates BlastRadius — see the unsettled note below on who that is.
Two things on this page are not settled yet, and pretending otherwise would be the dishonest part.
- Which legal entity you are contracting with. Today BlastRadius is one person, not a company.
- Which country’s law governs these terms, and where a dispute would be heard.
Both are answered before anybody is charged for this product, and if you need them answered sooner in order to install it, ask and you will get a straight reply rather than a form.
What the service does
BlastRadius reads the JSON output of terraform plan,
redacted in your own CI runner before it is uploaded, and posts one
comment and one check run on the pull request the plan belongs to. What
it stores, for how long, and what it sends where is described in full on
the data handling page, which is part
of these terms by reference.
You keep every right in your own code, your own plans and your own infrastructure. Nothing you upload is used to train a model, and we have no model of our own.
What it does not promise, and this is the important part
BlastRadius is a reviewer. A reviewer that implied it caught everything would make you worse off than having none, because you would stop looking.
- A clean verdict is not a statement that your plan is safe. It means no rule in the current rule set fired on the changes we could read. There are risks in a terraform plan that this product has no rule for, providers it has no rules for at all, and plans it will decline to review. Your own review is still yours.
- Redaction is best-effort and its gaps are published. The mechanisms are name-, mark- and format-based, and the list of what they do not catch is written out on the data handling page and in the source file that implements them. Do not treat uploading a plan as equivalent to it having no secrets in it.
- There is no uptime commitment during the beta. The service is offered as it is. What is engineered instead is that an outage cannot break your build: the Action never sets a failing exit code, and a review that could not happen reports as skipped rather than as a failure.
- Liability is limited to what you paid, which today is nothing. To the extent the law allows, neither party is liable to the other for indirect or consequential loss, and total liability is capped at the fees paid in the twelve months before a claim. This is the boilerplate clause; it is here because its absence would be worse, not because it has been negotiated.
What we ask of you
- Upload plans for repositories you are entitled to. An upload token authorises exactly one repository, and issuing one requires admin on it. Do not use somebody else’s.
- Do not attack the service, and do report it if you can. Security testing against your own installations is welcome and has a safe harbour — see the security policy. Load testing and denial of service are not covered by it.
- Do not resell the review. Use it on your own repositories, or your employer’s or client’s repositories on their behalf. Running it as the engine behind a competing service is the one use that is out of bounds.
Money
The product is free today and there is no billing wired to it — the pricing page says what we intend to charge when there is. Two commitments from that page are part of these terms:
If you install during the beta, you keep your access. When there is a price, the repositories already connected are not the ones it starts with, and you will hear about a change from us before it applies rather than on an invoice.
A billing problem will never block a merge. If a subscription ever lapses, the reviewer stops commenting. It does not start blocking a merge.
Ending it
Uninstall the GitHub App. That is the whole procedure, it takes effect immediately, and it deletes everything we hold for you — every foreign key in the database cascades from the installation row, so removing the App is one delete that takes your repositories, tokens, runs and findings with it.
We may suspend an installation that is attacking the service or uploading plans for repositories it is not entitled to. Anything less urgent gets an email first.
Changes to these terms
This page changes when the product does, and the date at the top moves with it. A change that reduces what you get — a price, a retention window, a promise withdrawn — is emailed to the address on your installation before it takes effect. A change that fixes a typo is not.
Questions, or a clause you think is wrong: security@blastradiusapp.com.