Plan tiers
Launch
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.
Grow
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.
Plus
Everything in Grow plus Release Control for
staged rollouts and Preview Releases. Available monthly or yearly.
Scale
Enterprise tier with custom limits, dedicated support, and bespoke
commercial terms. Get in touch
to discuss.
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 youdevelop, preview, and public stages running side by side. Each metric handles them differently:
- Records are counted from
publicwhenever a project has been promoted, otherwise fromdevelop.previewis 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, andpublicare distinct requests and each one counts. A frontend hittingpublicplus a CI job hittingpreviewis two requests against the meter.
Who can change the plan
Contact us to change your plan or discuss any custom requirements.Related
Release Control
The staged-rollout system available for Plus and Scale plans.
Pricing
Current per-tier pricing on the Frontic website.
Teams
Plans are per team; switching teams switches plans.