Plans & Tiers

Subscription plans are set at the organization level. There are four tiers — Free, Pro, Team, and Enterprise — each defining how many environments you get, how many rule-set runs are included per month, and how overage is handled.

The plans

The table below summarizes the tiers. Prices are in USD; verify current pricing in the app before relying on it, as plans evolve.

Pro, Team, and Enterprise can be billed monthly or annually and are activated through an in-app Stripe subscription; the annual price saves one month on Pro and Team and two months on Enterprise. Free needs no payment method.

Every paid tier also includes a number of author seats — 5 on Pro, 15 on Team, and 25 on Enterprise (Free includes 2). A seat is used only by someone who can edit rules; read-only, run-only, and debug-only access is free. Seat usage is shown on your organization page.

Enterprise organizations can raise their author seat limit above the included 25. Additional seats are billed monthly at a per-seat rate shown on the organization page, up to a maximum of 1,000. Other tiers show your current seat usage but do not offer paid seat overage.

Changing plans

A plan change is a change to your limits and nothing else. Upgrading and downgrading both leave every environment you already have exactly as it is — nothing is created, renamed, moved to different hosting, or removed in either direction, and a name you chose yourself is never overwritten.

Limits are read live but enforced when you create something. So downgrading while you are above the new plan’s environment cap keeps all your existing environments running; it is the next one you try to create that is refused. Upgrading lifts the cap immediately, and you can create the extra environments straight away.

Moving to Enterprise does not convert an existing shared environment into a dedicated one. A dedicated environment is always a new environment — see Hosting Modes. Your authored content is not tied to an environment, so projects, rule sets, conditions, action sets, tests, and versions are there the moment the dedicated environment exists. What you set up fresh is the per-environment operational state: settings, variables, schedules, API keys, and run history. Releases move across with the deployment pipeline.

Monthly run metering

Each tier includes a monthly allowance of rule-set runs, and each run you make is metered against that allowance. When you exceed it, runs are not blocked — they are covered by prepaid credits as overage, at a fixed conversion of one credit per 100 runs. Every tier supports this overage path. See Credits & Billing for how credits and overage work.

Metering applies to runs on the shared host. Runs on a dedicated environment are never metered, on any tier, because that environment executes in your own subscription.

Rate limits

A few operations that do a lot of work each time are limited per organization, so one busy organization cannot slow them down for everyone else. Each operation is counted on its own, over a rolling window, and the limit depends on your plan:

• What-if comparisons and trace explanations (What if? and Explain with AI on a trace) are limited on shared environments only. A dedicated environment runs in your own subscription and is not limited.
• AI project generations are the AI Project Generator. A generation refused by the limit costs no credit.
• Member data exports are an organization admin exporting one member’s records. Downloading your own data is limited separately, to five times an hour for each person, whatever the plan. See Your Account & Data.

When you reach a limit, the message appears where you pressed the button. It says which limit you reached, on which plan, and how long to wait before trying again, and below Enterprise it notes that a higher plan raises the limit. Nothing else is affected: rule-set runs, tests and everything else carry on as normal.

Data retention and correlation windows

Tiers also differ in how long they retain rule-set logs and audit log events, and how long a correlation ID stays valid for grouping related runs. Higher tiers keep more history.

Audit events are recorded on every tier, even where the log cannot be browsed, and each one expires when its plan’s retention runs out. Enterprise keeps them for seven years by default; an organization admin can keep them longer, or indefinitely, from the Audit Log page.

Enterprise

Enterprise is a flat monthly subscription rather than a per-environment charge. It includes 50 environments, 500,000 shared-host runs a month, 25 author seats, unlimited run-log retention, version history, and file storage, and seven years of audit history, or longer if you choose.

Up to 3 of those environments can be deployed into your own cloud subscription as dedicated hosts. Runs there are not metered and do not count against the monthly allowance, so the run limit and credit overage only ever apply to your shared environments. See Hosting Modes for the difference between shared and dedicated hosting.

Enterprise also unlocks a set of governance features not available on lower tiers, including audit log export, streaming and longer retention (Team can browse the Audit Log too), custom roles and access review, and Disaster Recovery. Enterprise organizations can add Compliance Archive as a paid add-on for a long-term, tamper-evident copy of their audit trail.