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 the current period into three figures:

• Usage - everything consumed this 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.
• 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.

​

On the Billing page

The Billing page in the admin app (Settings → Billing) shows the team’s current-period consumption - the three API metrics against the included allowance, and the AI usage breakdown - so you can see where you sit before the period closes.

​

Who can change the plan

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

​

Related