Models and tiers

Every session needs an AI model. There are two ways to get one: the platform's models, which come with your plan, or a key from your own model provider.

The platform's models

With no provider of your own, sessions run on the platform's models, organised in tiers:

Which models sit behind each tier is set by the platform and can change as better models appear. A tier that isn't set up isn't offered.

Auto

Auto routes each step of a session to the tier that suits it:

• Steps that steer the work (planning and architecture, review, security, research and requirements) use the best tier you have allowance for: Premium, then Standard, then Economy.
• The code-writing step uses Standard first, then Premium, then Economy.
• Bulk drafting steps use Economy first.

That gets close to Premium quality while spending far fewer Premium tokens. When more than one tier is available, Auto is first in the list and is the default.

Choosing a tier

When you start a session under Develop → AI Sessions → New session, the Model tier list shows each tier with what's left, for example "2.1M tokens left this month". A tier your plan doesn't include shows "not in your plan"; one whose allowance is spent shows "used up this month". The list appears only when the workspace has no provider of its own and more than one tier is available.

Allowances

Each plan includes a monthly token allowance per tier (input plus output tokens). The current amounts are on the pricing page. Allowances:

• are shared by every workspace owned by the same account;
• start again on the 1st of each month (UTC);
• are shown under Measure → Usage in AI allowance this month: a bar per tier, amber from 80%, red when used up.

When an allowance runs out

If the workspace has credits, the session continues on credits and the real cost is taken from them. Otherwise it stops and says what ran out. To keep going, you can:

• start the session on another tier;
• add credits on the Billing page;
• connect your own provider key;
• move to a plan with a larger allowance.

Bring your own key

Workspace admins can add provider keys on the workspace Dashboard, in Bring Your Own Key. Keys that can run sessions:

• Anthropic (Claude)
• OpenAI
• Moonshot (Kimi)
• Z.ai (GLM)
• DeepSeek
• Groq
• OpenRouter
• Ollama Cloud

Google Gemini keys can be stored but can't run sessions.

When a workspace has its own key, sessions run on it first. The launcher then shows a Model list (default "Provider default") instead of tiers. Keys are encrypted at rest and shown masked.

Sessions on your own key are billed by that provider and don't use the platform allowance. Their cost still counts toward the workspace's cost budget.

Next steps

• Cost controls
• Sessions
• AI coding cost calculator