// Pricing
Self-host Crux for free. Pay when you want hosted retention, organization controls, fleet-wide policy rollout, approvals, and support.
// Pricing
The Apache-2.0 core is complete enough to self-host. Commercial tiers add hosted operations, retention, org controls, support, and fleet-scale compliance.
Local Crux CLI, server, worker, gateway, MCP governance, console, adapters, and exports.
Hosted control plane for small fleets that need sync and short retention without running infrastructure.
The organization tier for shared fleets, policy rollout, approvals, SSO, and audit export.
Dedicated hosting, regulated retention, support, and hardened delivery for large or sensitive fleets.
Crux Enterprise packages the cloud operations layer for air-gapped and dedicated environments with hardened images, policy packs, and compliance evidence.
// How we price
Provider tokens remain billed by the provider. Crux charges only for operational control-plane services.
Agent count and trace retention map directly to operational load and storage cost.
The CLI, local server, worker, MCP gateway, core policy, and self-hosted console stay Apache-2.0.
Commercial value is shared org operations: SSO, RBAC, audit export, retention, support, and fleet sync.
// Add-ons
Reviewed MCP server descriptors, policy templates, signing, and recall signals.
per server / month
SOC 2, HIPAA, FedRAMP, policy, approval, trace, and AgBOM evidence exports.
annual
Single-tenant Crux Cloud deployed in your cloud or dedicated region.
capacity-based
Organization-local MCP catalog mirror with private descriptors and replication.
annual
// Pricing FAQ
Yes. The Apache-2.0 distribution includes the local CLI, server, worker, MCP gateway, core policy, adapters, and self-hosted console.
An agent is one registered fleet record: one managed CLI agent, one custom SDK agent, or one deployed agent profile.
Cloud Team includes execution and retention allowances, then meters overage by capacity tier. Self-hosted OSS does not meter executions.
Yes. Fleet profiles, policies, traces, and AgBOM records export through the same Crux control-plane model.
Never. Provider authentication and token billing remain with the provider unless a custom agent explicitly routes through a Crux gateway.