Plan capability matrix

Summary#

This page answers a narrower question than the pricing page does: for each capability, which plan unlocks it, and does the platform check that automatically or is it a published allowance we ask you to work within? Both kinds are real commitments, but only one of them will stop you mid-click, and support needs to know which is which before promising a customer anything.

Overview#

Five plans are sold and one more exists behind the scenes.

Starter is a real, billable plan. It has live prices and can be reached by checkout, and existing customers are on it, but no card for it appears on the pricing page. If a customer says they are on Starter, believe them and check the Account screen. See Plans and pricing.

Custom is a commercial agreement, not a separate tier. It is fulfilled by configuring one of the plans above with agreed figures.

Published prices, monthly and annual:

Quote Starter as $19 monthly and nothing else. It has a working annual checkout price, but no annual figure for it is published anywhere in the product, and Starter has no card on the pricing page at all. This table used to print an annual figure for it, which is exactly the number Plans and pricing tells you not to give a customer.

Plans are ranked, and every "minimum plan" check below compares against this order. Free sits below Starter, so a feature requiring Starter is unavailable on Free.

Free  <  Starter  <  Pro  <  Agency  <  Enterprise

Enforced automatically#

These are checked at the moment you act. If your plan is below the minimum, the action is refused and the message quoted here is what you see. Nothing is charged when a gate refuses.

The recommendations minimum plan and the per-plan recommendations allowance are configurable by an administrator, so a customer's figures can differ from the defaults above. Get Recommendations explains the feature and Runtime configuration the controls.

Published allowances#

These figures describe what a plan entitles you to. With one exception they are not checked automatically today, so the interface will not stop you at the number. Treat them as the agreed shape of the plan: stay inside them, and talk to us before planning work that exceeds one.

The exception is premium AI models, which are enforced: Agency and above run the AI features on Claude Opus and lower plans run them on the standard model, with nothing blocked either way. See AI models used across the platform.

Support and service commitments are also published rather than enforced by software: priority support from Agency, a dedicated account manager and an uptime SLA from Enterprise, and DPA, security review, data residency and dedicated infrastructure on a Custom agreement only.

SSO and SAML are available on request under a Custom agreement only. They are not part of any self-serve plan and are not something a customer can switch on. See Enterprise and custom agreements.

Included on every paid plan#

These need a paid plan of some kind but no particular tier.

Included on every plan, including Free#

Account states that override the plan#

A small number of internal test accounts resolve to an unlimited tier and bypass both the monthly allowance and the hourly limit. They are not customers and never appear in customer-facing figures.

What plan a customer is actually on#

One source decides it, and it is not the pricing page or the subscription state in Stripe on its own. In order of precedence: an internal override, then the plan recorded for that email address, then Free. A checkout writes that record through the billing webhook, and an administrator can set it by hand. If a customer has paid and the app still shows Free, the record is what to check.

See Plans and pricing for the full model, My plan did not update after paying for the symptom, and Customer lookup and billing for the administrator's view.