Plans and module access

Plans differ on seats and on how much AI usage is included. Which modules a workspace shows is a separate thing: it is a per-workspace configuration, not a purchase decision made at sign-up.

For current prices, see the pricing page. This page covers only how access is decided technically.

Module access is a deployment setting, not a price tier

Which modules a workspace shows is controlled at runtime by its SystemManifest. When a module is switched off for a workspace, its navigation entry is hidden and its API endpoints respond accordingly.

That mechanism exists so a workspace can be configured to match how a business actually runs. It is not a paywall, and turning a module on is a configuration change rather than an upgrade.

See Manifest-Driven Gating for how the manifest is read and applied.

Deployment models

The other choice that affects what you administer is where your database lives. See Managed vs. BYOK.