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. Everyone sees full stats, whatever they pay.

There is one flat ceiling, and it is the same on every plan: a workspace keeps at most 100 forms and 100 link pages. It bounds what you keep rather than what you do, and it is high enough that it only shows up on a workspace creating them from a script — creating one over the API or the CLI past 100 is refused, and from 70 the answer names the ones nothing has visited in the last 90 days so you know which to delete.

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. Automation DMs never carry big branding, on any plan — your reply goes out exactly as you wrote 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 once you use automations (see below): 1 connection on teeny, 2 on tiny, 3 on big, 5 on bigger.
• Integrations. How many of your other tools (Calendly, Discord and so on) a workspace can connect: 2 on teeny, 5 on tiny, 15 on big, 50 on bigger. This count is separate from connected Instagram and Facebook accounts, so connecting a tool never uses up a messaging slot. See Integration limits below.

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 the pricing page — or your billing page inside big, once you have an account — 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. Authorization refusals are 403 instead — your token is missing a scope, your role is too low, the endpoint is dashboard-only and accepts no token at all (below), or the workspace has been suspended, which pauses the whole programmatic surface whatever the plan. The message tells you which.
• Publishing is not on that dashboard-only list, but it does need a person. A token, a CLI command or an AI agent can ask to publish a link page or a form; it goes live only once someone signed into big approves the request in the browser, and the approval screen is session-only in exactly the way the governance surface is. No plan, scope or role changes that, and there is no publish scope to mint — see Approving a publish.
• The 100-forms and 100-link-pages ceiling above is enforced here rather than in the dashboard: a create over the API or the CLI is refused past it, with a 403 you report rather than a 429 you retry. See Forms and links are almost entirely uncapped.
• 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 Links → Short 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. And while the CLI and API are in beta, the personal-access-token surface — the CLI, the local MCP server, and the REST API — also needs your workspace to be enrolled: an unenrolled workspace gets a 403 with code: feature_disabled on every call, whatever its plan. Ask a workspace owner to request access, or email [email protected]. The remote MCP endpoint has no enrollment gate.

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, big login stores your token with a note that only these commands will answer, so big docs:search "…" works as usual (or skip the file with 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. When your workspace crosses 80%, and again at 100%, the workspace owner gets a notification in big and the same notice by email.

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.
• Back-filled Typeform responses don't count. Past responses you bring in with Back-fill past responses never count against the cap and are never locked.
• 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

Automations are a separate 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.
• Only switched-on automations count. A paused automation spends nothing against that cap, however many you keep. That includes the paused example automations a new workspace starts with — they cost you nothing until you turn one on, and switching both on spends two of your ten.

Integration limits

Integrations connect your other tools to big, with an API key or by signing in to the tool, so your own AI agent can get their context through big's MCP server.

• The limit counts every integration that isn't disconnected, including one in Error or Reconnect needed. A disconnected integration frees its slot straight away, and reconnecting one that needs it doesn't take a second slot.
• It is separate from Instagram and Facebook connections. Those have their own per-plan count above; the two never share a budget.
• Every provider is available on every plan. No tool is reserved for a higher tier.
• Downgrading never disconnects anything. If you move to a plan with a lower limit while you have more integrations than it allows, the ones you have keep working and can still be re-verified, rotated and disconnected; you just can't connect a new one until you're back under the limit. Disconnect the ones you no longer need, or upgrade. See Connect an integration.

Google Drive folder limits

Google Drive folders you link are synced into big on every plan, up to these limits, counted across the workspace:

• Linked folders don't use an integration slot, and synced copies don't count toward your Files storage.
• Past a limit, big keeps what it holds current and adds no new files; the folder shows Capped.
• Downgrading deletes nothing. Linked folders keep syncing; you can't link another, and new files aren't added, until you are back under the limits.

Scheduled posts

In testing, not available yet. Scheduling is visible only to big's team for now. These are the limits it will open with.

Scheduled posts are capped per calendar month, counted per account the post goes to, so one post sent to two accounts counts as two:

• The month is the one the post is scheduled for, not the month you wrote it.
• Downgrading cancels nothing. Posts already scheduled still go out; you can't schedule more that month until you're back under the limit.
• Publishing is not switched on yet. You can plan and schedule posts now; they go out once Instagram publishing is approved.

Beyond the four plans

Need big hosted privately for your company, or want the team to build your setup with you? big Enterprise is a private deployment of big with its own database, so every contact, response and message stays in a system you control, with custom integrations packaged in. big Services audits how your business wins customers and builds the automations, forms and integrations to run it. Neither is sold through checkout: both are priced per company after a strategy call. See Services or book a call.

Related

• Billing — change plan, see invoices, watch your usage.
• Your data — export everything, or delete the account.
• Integrations — connect your other tools and what each plan allows.