Forms and links are almost entirely uncapped

There's no per-plan limit on forms, fields, links, link-in-bio pages, or clicks — on any tier, including free. Create as many as you want and everyone sees full stats.

The one exception is form submissions, which count against the weekly usage cap below. Views, clicks, and the forms themselves are never capped — only a stored submission counts, and the counter resets every Monday.

What does differ

big has four plans: teeny (free), tiny, big, and bigger. The differences that matter for forms and links are:

• Branding. On teeny (free), public forms show a "Powered by big." footer. Every paid plan (tiny and up) removes it.
• File storage. Each plan includes a storage allowance for files: 250 MiB on teeny, 5 GiB on tiny, 25 GiB on big, and 100 GiB on bigger. This backs the Files feature, separate from forms and links themselves.
• Connected Instagram accounts. Relevant only once automations are enabled for your workspace (see below): 1 connection on teeny, 2 on tiny, 3 on big, 5 on bigger.

Pricing: teeny is free; tiny is $10/mo (or $6.90/mo billed annually); big is $30/mo (or $20.10/mo billed annually); bigger is $100/mo (or $66.90/mo billed annually). See your billing page inside big for the current, authoritative numbers.

Developer access (CLI, MCP, API)

This section is the single source of truth for what a plan buys you on the programmatic surface — the big CLI, both MCP servers, and the REST API. They share one entitlement, so a plan that can't read over the API can't read over MCP either.

The line is simply free versus paid: every paid plan gets the whole programmatic surface, reads and writes alike. There is no read-only paid tier.

• Read means anything that only fetches — listing automations, contacts, forms, links, posts, reading DM threads, pulling stats.
• Write means anything that changes something: creating a link, sending a DM, tagging a contact, publishing a form, syncing posts, deleting anything. Every write endpoint is identified by a :write scope.
• A request your plan doesn't cover returns 402, with a message pointing at your billing page — on today's plans that only happens on teeny. Missing a scope is a different error — that's 403, which is also what you get when your role is too low.
• On teeny, use the dashboard. Everything the CLI and MCP can read is on screen already: automations under Automations, DMs under Inbox, contacts and tags under Manage, form responses and stats on each form, and click stats under Manage → Links.

A paid plan is necessary but not sufficient: your token still needs the right scope, and writes still need an editor role or higher.

One exception: reading the documentation

The four documentation surfaces — GET /api/search, /docs/<path>.md, /llms.txt, /llms-full.txt, and the big docs:search / big docs:read commands and big_docs_search / big_docs_read tools that wrap them — are not plan-gated. Any valid token reads them on any plan, free included, and they need no scope.

Putting the manual behind the paywall it documents would be user-hostile, and reading documentation exposes no workspace data. On teeny there is one wrinkle: big login still fails with 402, because it validates your token through an endpoint that is gated, so pass the token in the environment instead — BIG_TOKEN=big_pat_xxx big docs:search "…". See Read the docs with a token.

Audit history

Per-plan audit history retention windows (7/30/90 days) are planned but not yet enforced — today every plan can query its full audit history.

The weekly usage cap

This is the one cap that applies to every workspace, including one that has never touched automations. Automation steps and form submissions share a single weekly budget:

The week is the ISO week: the counter resets at 00:00 UTC on Monday. Your current usage against the cap is on Settings → Billing, and you'll get an email when you cross 80% and again at 100%.

What counts, and what happens when you hit it:

• Automation steps count. Hitting the cap stops new conversations from starting; a conversation already mid-flow is allowed to finish, so some replies still go out afterwards.
• Stored form submissions count — but a submission is never refused. Over the cap, forms keep accepting and storing responses, on every plan, and the visitor sees the same thank-you screen either way. You never lose a lead to your billing state. What changes is when you can read it.
• Over the cap, a response is stored locked. You see that it arrived and when, and it still counts in your response total and conversion rate. The answers, the submitter's identity, and the link or campaign it came from stay hidden until it unlocks. Nothing is deleted and nothing is lost.
• Locked responses unlock at the weekly reset, oldest first, for as far as the new week's budget stretches. Upgrading unlocks every locked response immediately, whatever the backlog.
• The released backlog is served first, ahead of your automations. Unlocking draws on the new week's budget before any DM or comment automation does, so your automations only start firing again once the backlog has been cleared. If you are locking more responses each week than your cap covers, the backlog never clears and your automations stay quiet until you upgrade.
• What running out actually costs you is automations. Because the budget is shared, a form carrying heavy traffic can spend the allowance your DM and comment automations draw on, and those stop starting until the week resets.
• Nothing else counts. Form views, link clicks, link-in-bio views, and the forms, links, and pages themselves are all free and unlimited on every plan.

Automations limits (preview, gated)

Automations are a separate, limited-preview feature from forms and links. Beyond the weekly cap above, they add one limit of their own:

• Active automations — teeny is capped at 10 active automations; paid plans are unlimited.

Ask your account rep about automations early access for details.

Related

• Billing — change plan, see invoices, watch your usage.
• Your data — export everything, or delete the account.