Enterprise

Many organizations. One agreement. Clean boundaries.

Equation’s commercial model is built for enterprise structure: a parent can pay for covered organizations while every organization keeps its own data, workspaces and permissions.

What you get

Enterprise structure is the data model, not a bolt-on

The same organization and billing machinery that runs self-serve plans runs multi-organization agreements — no forked codebase, no private exceptions.

Multi-organization structure

An enterprise parent (agency group, holding company) can cover member organizations. Each organization keeps its own workspaces, people, permissions and data — coverage is commercial, not a data merge.

Consolidated billing, isolated entitlements

The parent pays; each covered organization gets exactly the product entitlements assigned to it. One organization’s plan never leaks into another’s.

Negotiated agreements

Enterprise subscriptions, commissions and capacity come from the same versioned commercial catalog as self-serve plans — overridden by named agreement, never by undocumented special cases.

Products enabled per organization

Each Equation product is enabled and billed per organization. A future product joins the same catalog and assignment model — your structure does not change.

Governance and audit

Organization-scoped roles and permissions, audit history with CSV/JSONL export, and scoped developer API keys with rotation, revocation and usage reporting.

Security that is not a tier

Authentication, tenant isolation and data ownership rules apply at every edition. Enterprise adds coverage and terms — it does not unlock basic safety.

How it works

From structure to signed coverage

  1. 01

    Tell us the structure

    Parent organization, member organizations, and which products each one needs.

  2. 02

    We draft the agreement

    Named terms: products, editions, commission or custom pricing, capacity, coverage and the organizations it applies to.

  3. 03

    Coverage activates on acceptance

    Entitlements are catalog records — the same records the console, billing and developer surfaces read. No parallel system.