Packaging

The unit of purchase
is the module.

Not seats on a suite you mostly will not use. You license the modules you run, the product enforces exactly that, and adding the next one is a licensing change — not a re-implementation.


01/The mechanics

Licensing is a product fact

This page can promise module-at-a-time buying because the product genuinely enforces it — the same mechanism that gates which AI tools an org's chat can see.

License modules per organisation — buy one, add more later, with the product genuinely enforcing itorganizations.enabled_modules — the ceiling everything checks
Set permissions per role and override per userroles and per-user overrides inside each module

02/The catalogue

13 modules, one data model

Start with the one that hurts most. Cross-fire pulls the next one in when it is ready to.


03/What is not here

No price list, on purpose

Pricing is a conversation about your module set and your user count. What this page commits to is the shape: you will never be asked to buy the suite to get the module.