Question 1

Do you charge per user, per risk, or per document?

Accepted Answer

No. There are no per-seat charges and no metering on assets, risks, incidents, suppliers or documents. Per-unit pricing on a management system creates a bad incentive: it makes you cheaper by recording less. A risk register that stays small because each row costs money is worse evidence, not a smaller bill. The fleet is priced per organisation so that logging one more incident or assessing one more supplier is free.

Question 2

Four agents are prototypes. Am I paying for unfinished software?

Accepted Answer

You are paying for nine agents, four of which are labelled prototypes on the fleet page rather than described as finished. Those four produce real output and are used in real compliance work. What "prototype" means here is that their contracts can still change: the shape of what they write, the fields they expect, and the questions they ask are still settling as they meet more real management systems. They are included rather than held back because a prototype you can use and argue with is worth more to you, and to us, than a roadmap entry. The alternative would be shipping them a year later with the same uncertainties and a more confident label.

Question 3

I bought the Risk Investigation Agent. Does that come off the fleet price?

Accepted Answer

Talk to us. The single-agent purchase is deliberately priced as the cheapest honest way to find out whether this suits you, and a customer who did that and then wants the whole system is exactly the path the pricing is designed to encourage. Get in touch before you subscribe rather than after, so it can be handled as one conversation.

Question 4

What happens to my data if I cancel the fleet subscription?

Accepted Answer

Nothing happens to it. The agents run inside your own Claude Code against registers you already own, so there is no Askara-hosted tenant holding your risk register, your incident log or your documents. Cancelling stops your access to the agents and to future releases; it does not touch the records they wrote. That is a deliberate consequence of how the fleet is built rather than a policy we could change. The agents propose and a person commits, and the commit goes to your system. We never become the custodian of the thing you would need to get back.

Question 5

Why is the fleet a subscription when the single agent is a one-time purchase?

Accepted Answer

Because the fleet is not finished, and a one-time price for an unfinished thing forces a dishonest choice: either freeze the product at the version you bought, or charge you again later and call it an upgrade. Agents are still being added. Existing ones change as real audits push back on them. The knowledge graph that will sit under all of them is being built now and is included in the fleet price as it rolls out, at no change in price. A subscription is what that arrangement actually is. The single agent stays a one-time purchase for the opposite reason: it exists so you can find out what this way of working is like without committing to the system. A trial that expires would be a worse version of that, so it is a real purchase with a real limitation, stated plainly. You keep the version you bought, and later releases are not included.

Pricing

Do you charge per user, per risk, or per document?▾

Four agents are prototypes. Am I paying for unfinished software?▾

I bought the Risk Investigation Agent. Does that come off the fleet price?▾

What happens to my data if I cancel the fleet subscription?▾

Why is the fleet a subscription when the single agent is a one-time purchase?▾