activate
Activation opens
with sales.
Licences are not on sale yet, so there is no key to paste and no form on this page.
Nothing to activate. Until sales open, no version of the tool enforces a licence, so there is nothing here you need. What follows is how activation will work, so that it is not a surprise. The pricing page explains the model.
01 · how it works
A key goes in.
A token comes out.
Paste the licence key from your purchase.
The key comes from the payment provider. It proves that your organisation's subscription is paid. It is not what the tool reads.
You get back a token beginning jal1.
It is a signed statement: who is licensed, for how many developers, and the date it is paid through. It contains no email address, because jiraagents doctor prints it and doctor runs in CI logs.
Set it as JIRAAGENTS_LICENCE, in any one of four places.
Your environment. Your repository's gitignored .env. A CI secret exposed to the steps that run apply or solve. Or the file ~/.config/jiraagents/licence, which works in every repository on that machine. A token that verifies always beats one that does not, so a junk value in a repository you are auditing cannot lock you out. If more than one verifies, the one paid through the latest date wins, so the short first token never shadows the full-term one.
Run jiraagents doctor.
Its entitlement row names your organisation and the date your licence covers releases through. From then on the check is offline: the tool never contacts this site, or us, again.
02 · what is sent, and to whom
One field.
No scripts.
The form has one field. The key is sent to this site, and from this site to the payment provider, to check it. Nothing about your repositories, your Jira or your GitHub is sent, because this page runs no scripts and has no way to know any of it. Beyond the key, the request carries only what every web request carries, such as your IP address.
The command line tool is not involved at any point. It never sees your key, and it never calls this site.
Treat the token like a team secret. Anyone holding it can run the paid commands as your organisation. If you lose it, paste the same key again.
03 · the first token is short
Paste the same key again
after the refund window.
For the first 14 days after you buy, you can ask for a refund. An offline token cannot be recalled once it is issued, so a token handed out while a refund is still possible has to be a short one: it is paid through to the end of the refund window and no further.
After that window, paste your key here again and you get the token for your full paid term. Nothing you are already running stops in the meantime: the check only ever looks at the release date of the version you run.
If you pay monthly, your full paid term is the month you have paid for. To unlock a version released after it ends, paste your key here again after your next payment, and again after each one that follows. If you pay yearly, that is once a year. A renewal payment can take a few days to settle. Until it has, this page gives you the token you already hold and tells you when to come back, and the 14 days of grace on every token cover the gap.
The refund policy has the terms.