pricing
Reading is free.
Writing is paid.
Undo is always free.
A licence unlocks the two commands that write outside your machine. Everything else runs with no key and no account, in every version released so far.
Licences are not on sale yet. There is no price on this page and no button to press, because there is nothing to buy. Until sales open, no version of the tool enforces a licence key. Versions that carry the check say so in words, in the entitlement row of jiraagents doctor. This page describes the model the tool will be sold under, so that nothing about it is a surprise later.
The licence file has not caught up with this page. The licence text inside the package today reserves all rights and grants the right to use the software to nobody outside the vendor. The licence that grants free use of everything on the free side of this page, and the right to read the shipped code for security review, is being drafted and has not shipped. Until it ships, this page describes how the tool behaves and the model it will be sold under. It is not a grant of rights.
01 · the rule
The line is drawn at
somebody else's system.
If a command only looks, or only changes files on your own machine, it is free. If it writes into a Jira or a GitHub repository, it is paid. If it takes back something the tool wrote, it is free again, on purpose.
Everything that reads, and everything that undoes
Not a trial: nothing in an installed version switches off after a number of days.
scanruns the scanners and prints what survived the prefilter.planprints the reconcile table with zero writes.ingestreads a vulnerability report you already have into the same pipeline.explainandstatustrace one finding, and show the funnel.- The dashboard's views: findings, what was filtered and why, runs, agents.
sarif exportandaudit export: your findings and your audit trail, in files you keep.revertundoes a run, and never needs a licence. So dobaselineandconfirm, which only record a decision.- Dry runs.
applywithout--yesandsolve --dry-runwrite nothing outside your machine, so they are free too.
Writing outside your machine
These two, and adding a third would be a decision, not an accident.
apply --yesfiles the planned Jira issues.solvefixes tickets on a branch and opens draft pull requests.
plan prints the exact table apply would execute. So the free tier is the
demonstration: you can read every ticket the tool would file against your own repository
before you pay for anything, and if the table is wrong you found that out for nothing.
02 · what a licence is
One per organisation,
billed yearly.
Business customers only
A licence is sold to an organisation, not to a person, and not to consumers. One licence covers that organisation, for the number of developers written into it.
Yearly, and only yearly
There is no monthly plan. You pay for a year, and the date that year ends is your paid-through date. Everything below is defined against that one date.
03 · what a licence covers
Versions, not days.
And it never calls us.
Every version up to your date
A licence covers every version released up to your paid-through date, plus 14 days of grace, so a release that lands just after your renewal date is not a trap.
It does not expire on you
Your licence to run those versions does not end when you stop paying, apply and solve included. What lapses is the right to newer versions.
Checked offline
The token is a signed statement that your copy verifies on your own machine. The tool never calls us, for licensing or for anything else. The security page lists the hosts it does contact, and says where that list is not yet complete.
No clock in the check
It compares two fixed dates: the one in your token and the release date stamped into the version you run. Nothing about a version you have pinned changes when a day passes.
It cannot break a pinned job
A lapsed licence can only refuse a version you have not paid for, at the moment somebody upgrades to it. There is no licence server to be down.
Undo is never held back
revert, explain and both exports run whether or not you hold a licence, and whether or not it has lapsed. They sit in a table of commands the licence check never touches, and a test keeps them there. Nobody should hold tickets they cannot roll back because a payment lapsed.
04 · what we cannot promise
Read this part
before the part with a price.
We promise the right to run an old version, not that it keeps working
Every version calls services we do not run: Jira, GitHub, Anthropic and the scanners' own registries. Those change, and model names get retired. We do not promise that any of them keeps accepting an old version. A pinned version that stops working for that reason is not something a licence can fix. A current version is.
What is free is free in the versions released so far, not in perpetuity
Every version released so far runs everything on the free side with no key, and the check reads no clock, so an installed version does not change when a day passes. What a future version makes free is a decision we have not made, so it is not promised here.
You bring your own Anthropic key, and you pay that bill
The model-backed stages (the review lenses, triage, reading a prose report, and solve) call the Anthropic API with your key. That spend is between you and Anthropic and is not included in a licence. With no key there is no spend: the run says so on its own line and continues.
This is closed-source software from a small vendor
What ships is readable JavaScript, and you cannot fork it. There is no large company behind it. If that is the wrong risk for your organisation, this is the wrong tool, and it is better that you hear it here.
Nobody has measured this tool's precision yet
The README says so in those words. There is no number, anywhere, for how often a filed ticket is a true positive or how often a solver pull request merges without a human editing it. Use plan on your own repository and judge the table yourself.
The licence check is a courtesy gate, not copy protection
The package is readable JavaScript and removing the check is one line. It exists to tell an honest organisation where it stands, in the same voice as every other doctor row. What governs use is the licence agreement, not the gate.
05 · before it is on sale
Want to run it on something real
and tell us where it is wrong?
That is all a design partner is here. If your team wants to use apply and solve on a real repository before licences are on sale, write to dhillonvo@icloud.com and say what you would point it at. We will agree terms in writing before you run anything.
There is no waiting list, no counter and no launch discount to miss. When licences go on sale, this page will say so and will show the price.