> ## 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.

# Billing & Plans

Each [team](/admin/teams) 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](https://www.frontic.com/pricing) — it's the source of truth for what each tier costs.

## Plan tiers

<CardGroup cols={2}>
  <Card title="Launch" icon="rocket">
    The free starter tier — get a project running, ingest data, build
    a typed API, ship a frontend. Suitable for small projects and early
    prototypes. Unlimited users, projects, and API endpoints.
  </Card>

  <Card title="Grow" icon="chart-line">
    Pay-as-you-go. Everything in Launch plus AI Frontend Studio. Above
    the included allowance, additional usage is billed per unit as it's
    consumed.
  </Card>

  <Card title="Plus" icon="star">
    Everything in Grow plus [Release Control](/releases/overview) for
    staged rollouts and Preview Releases. Available monthly or yearly.
  </Card>

  <Card title="Scale" icon="building-columns">
    Enterprise tier with custom limits, dedicated support, and bespoke
    commercial terms. [Get in touch](mailto:support@frontic.com)
    to discuss.
  </Card>
</CardGroup>

## 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](/reference/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

| Metric       | Launch | Grow                | Plus | Scale  |
| ------------ | ------ | ------------------- | ---- | ------ |
| API Records  | 10K    | 10K + pay-per-unit  | 100K | Custom |
| API Updates  | 100K   | 100K + pay-per-unit | 100M | Custom |
| API Requests | 100K   | 100K + pay-per-unit | 5M   | Custom |

### What counts against the quota

[Release Control](/releases/overview) 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.

<Screenshot name="admin/billing-usage" caption="Billing — current-period usage against the plan allowance, with previous periods listed below" alt="Settings Billing page showing usage charts for API Records, Updates, and Requests against the included allowance, plus a list of previous billing periods" />

## 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.

<Screenshot name="admin/billing-plans" caption="Billing — current plan with the comparison grid below" alt="Settings Billing page showing the current plan card on top and a comparison grid below for Launch, Grow, and Plus" />

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](mailto:support@frontic.com) when you want to start that.

## Who can change the plan

Only **Owners** can change the plan or update billing details. [Admins and Members](/admin/members-and-roles) 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

<CardGroup cols={2}>
  <Card title="Members & Roles" icon="users" href="/admin/members-and-roles">
    Owners change the plan; Admins and Members see it.
  </Card>

  <Card title="Release Control" icon="code-merge" href="/releases/overview">
    The staged-rollout system gated to Plus and Scale plans.
  </Card>

  <Card title="Pricing" icon="dollar-sign" href="https://www.frontic.com/pricing">
    Current per-tier pricing on the Frontic website.
  </Card>

  <Card title="Teams" icon="building" href="/admin/teams">
    Plans are per team; switching teams switches plans.
  </Card>
</CardGroup>