Grid82
grid82.comJoin the waitlist
Get startedBilling and plans

Billing and plans

Exact limits for Free, Starter, Pro, and Custom plans, how seats, workflow steps, and AI credits are counted, and available add-on packs.

Every plan limit applies at the organisation level. Suites, apps, storage, seats, workflow steps, and AI credits are pooled across an organisation’s workspaces. Inspect live usage in the Studio under Billing or via billing.get.

Plan comparison

FreeStarterProCustom
Price (monthly billing)€0 / mo€42 / mo€289 / moContract
Price (annual billing)€0 / mo€29 / mo€199 / moContract
Studio builders11030Contract
Suites1210Contract
Apps (across all suites)31050Contract
App users (across all suites)350500Contract
Records per app1,00050,000200,000Contract
File storage1 GB5 GB25 GBContract
Custom domains0010Contract
Monthly AI credits0 (+ one-time welcome bonus)150,0001,000,000Contract
AI budgets per roleNoNoYesYes
Custom AI model selectionNoNoYesYes
Workflow steps / UTC month1,00010,000250,000Contract
Max workflow steps / run2002,0002,0002,000
Editor workflow tests / day502001,0001,000
Activity event detail kept2 days7 days90 days90 days
Activity daily totals kept30 days365 days730 days730 days

All plans include REST API, MCP servers, and CLI access.

How each quota is counted

App users and builders

  • App users are end users who can sign in to any suite in your organisation (invited directly, joined via link, or signed up). Each person counts once per organisation, even if their email appears in multiple suites. Pending invitations reserve a seat until accepted or revoked.
  • Builders are team members who open the Studio (studio.grid82.app) to configure schemas, permissions, pages, workflows, and billing. Builder seats are counted separately from app user seats.
  • When an organisation hits its user seat limit, existing members keep working while new sign-ups and invitations are paused until a seat is freed, a pack is added, or the plan is upgraded.

Apps, records, and storage

  • Apps are counted across all suites in the organisation (3 total on Free, 10 total on Starter, 50 total on Pro).
  • Records per app apply independently to each app: on Starter, each of your 10 apps can store up to 50,000 records.
  • File storage sums record attachments across every app in the organisation.

Workflow steps

A step is one SDK action executed during a live workflow run (db.*, ai.*, http.*, step.*, or approval.ask). Each iteration of a for...of loop counts its own executed steps. Triggers, skipped branches, editor test runs (workflows.test), and automatic retries of a failed step are free.

Steps reset on the 1st of each UTC month. Organisation admins receive an email alert at 80% usage. At 100%, in-flight runs finish normally while new runs halt (402 payment_required) until the month resets, you add a step pack, or you upgrade. Nothing is billed automatically beyond your plan.

AI credits

Assistant turns and ai.* workflow steps consume AI credits (10,000 credits equal $1.00 of underlying model usage at list price). Monthly plan allowances reset each month. One-time credit grants (welcome bonus, referral rewards, and top-up packs) are consumed only after the monthly allowance is depleted.

You can also store your suite’s own OpenRouter key as the OPENROUTER_API_KEY secret so workflow AI steps bill your own OpenRouter account directly.

Add-ons and one-time credit top-ups

Billing changes, add-on packs, and credit top-ups are managed interactively by an organisation admin from Billing in the Studio (API keys and connected agents can inspect quotas with billing.get and billing.workflows, but cannot make purchases).

One-time AI credit top-ups can be purchased on any plan (including Free) under Billing > Add-ons > AI credits > Once. Top-up credits expire 1 year after purchase:

PackCredits includedOne-time price
100k AI credits100,000 credits€10
250k AI credits250,000 credits€25
1M AI credits1,000,000 credits€90

Monthly capacity add-ons are available on Starter and Pro (the Custom domains add-on is Pro only) so you never have to jump tiers just because one quota is tight. Workflow steps and AI credits packs are self-serve in the Studio Billing page; all other capacity packs can be requested directly from the Add-ons dialog in Studio or by emailing hi@grid82.com:

Add-onCapacity per packMonthly pricePlansHow to add
Workflow steps+50,000 workflow steps / month€25 / moStarter, ProSelf-serve in Studio Billing
Monthly AI credits+250,000 AI credits / month€25 / moStarter, ProSelf-serve in Studio Billing
App users+50 / +250 / +1,000 app users€50 / €200 / €600 / moStarter, ProRequest via Billing or support
Builders+5 builders€15 / moStarter, ProRequest via Billing or support
Apps+20 apps€15 / moStarter, ProRequest via Billing or support
Suites+5 suites€25 / moStarter, ProRequest via Billing or support
Records+100,000 records per app€19 / moStarter, ProRequest via Billing or support
File storage+50 GB file storage€10 / moStarter, ProRequest via Billing or support
Custom domains+5 custom domains€10 / moProRequest via Billing or support

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Grid82 documentation and read it in full, instead of answering from memory.

https://grid82.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://grid82.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.