Pricing
Everything is free while Axela is in beta, and nothing here starts charging you on its own. These are the prices we expect to set; moving onto a paid plan will be a new agreement you actively accept, with at least thirty days' notice first, per the terms.
Personal
For individuals: your own machines, your own skills. One organisation, up to 10 active machines, one marketplace. Unlimited scanning on your own machine. Community support on GitHub. Not a trial — personal use stays free after the beta too.
Team
For companies, per organisation: up to 50 active machines and 3 marketplaces. Email support. For an organisation whose agents run skills it did not write itself.
Enterprise
Unlimited machines, SSO, an SLA, and help running notaryd yourself where the events must not leave your network. axela@system5.dev
The words on this page
- Skill
- A folder of instructions your coding agent reads and follows.
- Catalog
- One signed list: every skill in a repository and the exact bytes of each. Computers fetch it and refuse anything that does not match.
- Publishing
- Signing a catalog and handing it to Axela, so the computers in your organisation can use those skills.
- Machine
- One computer that checks its skills and reports what it found. Priced per machine, as below.
What counts as an active machine
A machine whose signed report reached the notary in the last thirty days. A laptop that stops reporting stops counting on its own; nothing needs deregistering. The fleet dashboard separately shows which computers have a fresh check right now.
Every publish is read before it is signed
Before adding its signature, Axela downloads your repository at the exact commit the publish came from, checks that every skill in it really is the bytes your catalog claims, and reads what those skills do. If any of that fails — the download, the check, or the reading — Axela does not sign, and nothing is published.
What stops a publish is behaviour in executable files — a script that pipes a download into a shell, reads credentials, or erases its own tracks. What a skill says never stops one. We tried the other way first: matching worrying strings refused four skills out of eleven, and every one of the four was documentation — including a security skill refused for quoting the address it teaches you to block. So wording is reported for a person to read, never blocked, and a report you have read can be marked accepted inside the skill, where your signature covers it.
It is included, not an add-on. Personal accounts get 100 scanned publishes a month; publishing once a day uses about thirty of them, so the allowance is not something you would normally reach. Team accounts get ten times as many. The limit exists because reading skills costs us real money in model time, and it is set high enough that normal publishing never meets it.
Self-hosting is always free
The client and the notary are open source under Apache-2.0. These prices buy the hosted service: the always-on notary, the console, and somebody else carrying the pager.