Plans and usage.

The plans

Your personal space is on the Free plan, and each organisation has its own paid plan. The pricing page lists exactly what each includes.

• Personal (your personal space, on the Free plan) is for building and testing: write Definitions, run the Sandbox, Test runs and Comparisons, and deploy to Test with runtime keys to call it. Calls to Test use the same starter test tokens, up to 30 a minute and 1,000 a day, however many keys you use. For production, create an organisation (see Organisations).
• Founder is for one person or a small team, with production: one member included, and up to three people with extra seats. It starts with a 14-day trial, which needs a card. While it runs, production is limited to 5,000 calls, and the owners get an email three days before it ends. Each person, email address and card has one trial.
• Scale includes five members and takes up to 25 with extra seats, with larger allowances. Production calls past the month's allowance are still served and billed with the next invoice, rather than refused.
• Enterprise is agreed with TypeFuse, including Managed production, larger limits and longer record keeping.

Plans differ in how many production calls they serve each month, how much testing runs on TypeFuse's TypeSafe key, how many Decisions, environments and members an organisation can have, and how long the detail of each call is kept (see How long records are kept).

Extra seats

On Founder and Scale you can add people beyond the plan's members, at the seat price on the pricing page: up to 3 people on Founder and 25 on Scale. Owners add them under Extra seats in Settings → Plan, and the change is prorated. Seats add people only; the plan's allowances stay the same. You can't go below the people the organisation has (members and pending invites), and moving between plans keeps as many places as the new plan allows.

Your plan, usage and invoices

Open Settings at the foot of the sidebar; its Billing pages are Plan, Usage and Payments. In an organisation, Plan shows what it's on (when its trial ends, when it renews or when it cancels), its extra seats and every plan as a card, the same as the pricing page, with Cancel plan at the foot. Usage shows how much of each allowance the organisation has used this period. Payments, for owners and admins, lists its invoices (each opens the invoice, to download or pay), its billing details and the cards on file; Edit and Add new change them.

Owners change the plan from the cards: another plan's button moves the organisation to it, and choosing the other billing period on your own plan's card switches between monthly and annual. A change applies at once and the difference is added to, or taken off, the next invoice. Manage billing on your own plan opens the billing portal for payment details, invoices and cancelling. In your personal space, Billing shows what you've used and offers Create an organisation. Contact us on Enterprise writes to TypeFuse.

When the organisation passes 85% and then 95% of an allowance, owners and admins get a notification.

At a limit

When a limit is reached, the page or command that hit it says which limit it was and how to go on.

• Production calls. The runtime refuses a call the plan doesn't cover with 402 PLAN_LIMIT, until the month renews or the plan changes. The SDK raises it as PlanLimitError. In a personal space, calls to Test stop once the test tokens are used up, and once you've made your 1,000 calls for the day, its keys answer 429 DAILY_LIMIT until midnight UTC. Every refusal carries billingUrl, the page where the plan changes.
• Testing. When the testing allowance runs out, you can keep testing with your own TypeSafe key (below) or change plan.
• Counts such as Decisions, environments and members are checked when you add one, with a way forward in the message.

Your own TypeSafe key for testing

On any plan, you can test with your own TypeSafe key. Add it on your Account page, in Your own TypeSafe key for testing, and choose Save for this session. Sandbox runs, Test runs and Comparisons then use your key and don't count towards the testing allowance, and replays of production can compare every row. The key is kept only in your browser session, for every organisation you use, and is forgotten when you sign out. It doesn't change anything else about your plan.

In the CLI, pass --typesafe-key or set TYPESAFE_KEY; through MCP, send it in the X-TypeSafe-Key header.