Billing & Plans

Each team is on a single plan. The plan determines which features the team can use, the usage allowance the team consumes each billing period, and the invoice cadence. For the current pricing, see the Frontic pricing page - it’s the source of truth for what each tier costs.

​

Plan tiers

​

Plan-gated features

A few capabilities sit behind specific tiers:

• Experience Designer - the single-page design surface. Grow, Plus, and Scale.
• Context Base - the Skills, Rules, Commands, and Guides your agents read from. Grow, Plus, and Scale.
• Design Library - your brand published as tokens. Grow, Plus, and Scale.
• Frontic Studio - Plus and Scale. Launch and Grow ship without Studio.
• Release Control - staged previews and promote-to-public flows. Plus and Scale.
• Drafts - isolated sandboxes that merge back into develop. Scale only, a tier above base Release Control, and still in Preview.

​

Usage

Three metrics meter your team’s monthly consumption. Each plan ships with an included allowance; usage above the allowance follows the plan’s overage rules.

• API Records - a snapshot of how many records currently exist across your project’s Blocks. The total is sampled regularly; whichever records are present at sampling time contribute, whether or not anything is reading them. To bring this down, delete records you no longer need.
• API Updates - ingest events delivered to your project: upsert and patch records arriving via the Ingest API or pulled by a Data Feed run. Deletes don’t count.
• API Requests - read activity from your frontends and tooling: every call to a Block, Listing, Page, Tree, or Context endpoint counts as one request.

​

Quotas

​

What counts against the quota

Release Control gives you develop, preview, and public stages running side by side. Each metric handles them differently:

• Records are counted from public whenever a project has been promoted, otherwise from develop. preview is excluded - running multiple Preview Releases never inflates your record count.
• Updates are counted once per inbound record update, not once per stage. The three stages each process the record afterwards, but the meter only ticks at the inbound point.
• Requests are counted per Fetch API call, scoped to the team. Each stage has its own version token, so calls to develop, preview, and public are distinct requests and each one counts. A frontend hitting public plus a CI job hitting preview is two requests against the meter.

​

AI usage

Frontic Studio and the Experience Designer consume AI usage, metered separately from the three API metrics and denominated in your team’s billing currency rather than in units. Grow and Plus include an AI credit: an allowance that offsets AI usage before any of it becomes chargeable. On Scale, the credit is part of your commercial terms. The Billing page splits each period into three figures:

• Usage - everything consumed in the period, settled and live together.
• Included - how much of that the AI credit covers, shown against the credit’s total, with a bar that fills as the credit is spent and the amount left.
• Chargeable - the remainder above the credit. This is the part that gets billed.

Launch reaches neither Studio nor the Designer, so nothing meters against it.

​

Where the usage went

Below the three figures, the AI usage panel breaks the period down by agent: Studio, Designer, Buddy, and the admin app’s smaller AI features, each under its own name - Context Setup, Commit Messages, Value Composer, Descriptions, Generated Texts, Data Crawls, and Summaries.

• Group by project or user. Once a period has usage from more than one project or more than one user, you can group by Project or User instead, and filter to a single project or user. A grouping that would only ever show one value isn’t offered.
• See what’s behind a group. Expand a group to list the jobs, experiences, threads, or projects that spent it, by name. Jobs, experiences, and projects link straight to them.
• Rows worth nothing are hidden; the panel says how many and lets you show them.

​

Past periods

Use the arrows next to the period name, or click a bar in the period chart, to step through past billing periods. Each period shows its own Usage, Included, and Chargeable figures and its own breakdown. A period with nothing to break down says why:

• No AI activity in this period - no agents ran and no tokens were consumed.
• Activity recorded, nothing metered - the tokens were used before metering started, so no cost was attributed.
• AI usage was not tracked yet - the AI usage metric didn’t exist in that period.

​

On the Billing page

The Billing page in the admin app (Settings → Billing) shows where the team stands in the current period, so you can see it before the period closes:

• Overview - how far through the period you are and when the plan renews, the billable spend so far split into AI usage and API usage above the allowance, and how many records you hold against the allowance.
• Requests and Updates - a meter for each against the included allowance, with a chart of past periods.
• Plan and AI usage - your plan and what it includes, next to the AI usage panel.

​

Who can change the plan

Contact us to change your plan or discuss any custom requirements.

​

Related