Billing & Plans

Documentation Index

Fetch the complete documentation index at: https://docs.frontic.com/llms.txt

Use this file to discover all available pages before exploring further.

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:

• AI Frontend Studio — Grow, Plus, and Scale. Launch ships without Studio.
• Release Control — staged previews and promote-to-public flows. Plus and Scale.
• Context Documents — AI Studio’s Skills, Rules, Commands, and Guides authoring surface. Plus and Scale.

​

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 ingest event, 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.

The Billing page in the admin app (Settings → Billing) shows the team’s current-period consumption and a history of previous billing periods, so you can see where you sit against the allowance and how usage is trending.

​

Choosing or changing a plan

Open Settings → Billing in the admin app. The Billing page shows the team’s current plan, current-period usage, and the comparison grid; click any plan to start the switch. A few mechanics worth knowing:

• Upgrading takes effect immediately. The new tier’s allowance and features apply right away; the invoice is prorated.
• Downgrading takes effect at the end of the current billing period. If current usage exceeds the new plan’s allowance, the admin app warns before the change applies.
• Scale isn’t a self-serve tier. It’s set up by the Frontic team after a conversation about your needs — reach out when you want to start that.

​

Who can change the plan

Only Owners can change the plan or update billing details. Admins and Members see the current plan and current usage but can’t switch tiers or modify payment information. There’s always at least one Owner per team — that’s who’s responsible for the billing relationship.

​

Related