Limits

The Change it column says how to go past a limit:

• You — a setting you change yourself (the link shows where).
• Upgrade — a higher plan has a higher limit (plans and prices).
• Ask us — Totalum can raise it for your account or project: write to support with what you need and why.
• No — fixed for everyone.

Plans are named Free, Starter, Builder, Professional and Enterprise. All amounts are per calendar month (UTC) unless the row says otherwise.

The plan belongs to the account: one plan covers every project on it. Most limits below are counted per project; the ones counted for the whole account say so.

#Limits and safeguards

What stops runaway spending or traffic, in one list. The details and every number are in the sections below.

• Site requests: each published site answers up to about 3,000 requests per 10 seconds on Free, 30,000 on Starter, Builder and Professional and 60,000 on Enterprise; above it that site answers 429 for a few seconds (Site requests).
• Built-in features per minute: on Free, Starter and Builder the per-minute amounts are shared by all the account's projects; on Professional and Enterprise each project has its own (Built-in features).
• Emergency stop, per project: a project that spends more credits in one hour than its plan allows (40 on Free up to 4,000 on Enterprise), or passes a 5-minute ceiling of site requests or database rows read or written, is paused on its own — the account's other projects keep running (Emergency stop).
• Account spending caps: everything the account spends in one hour and in 24 hours is capped on every plan (Enterprise also per calendar month); past a cap every project of the account pauses until the spend is back under it (Account spending caps).
• Project monthly budgets: each project has a monthly development budget and a monthly infrastructure budget that you set. At the development budget new prompts and paid builder actions are refused (403 PROJECT_CREDIT_LIMIT_REACHED) and a running prompt stops after at most 5 more credits; at the infrastructure budget the app's built-in features (AI, e-mail, file uploads, web scraping…) are refused while the site and its database keep running, and at the budget plus a reserve (10 % of it, at least 5 credits) only that project is paused: its site and preview show a paused page and its API keys answer 429 PROJECT_CREDIT_LIMIT_REACHED. Both reset on the 1st at 00:00 UTC (Monthly budgets).
• Unusual database usage: a sudden jump in a project's database usage is charged as usual and alerts you once a day (e-mail, chat, project.usage_spike webhook); it is not paused on its own, so set an infrastructure budget on every project (Unusual database usage).
• Negative balance: at a balance of 0 or below the built-in features stop while the sites keep serving; the sites pause at −30 on Free and, on paid plans, at once at −400 to −2,000 depending on the plan; on every plan, at −300 you get an e-mail and the sites pause 48 hours later unless you add credits. They come back at a balance of 0 or more (Balance and suspension).
• Monthly fees: 3 credits a month for each project on a paid plan that was published and online in the month, and 3 credits a month for each active custom domain (adding the domain costs 4 credits once) — the handbook has every charge.

#Account

#Plan limits

• A deleted project frees its slot at once. Creating too fast answers 429 RATE_LIMIT_EXCEEDED; wait a moment and retry.
• New projects and prompts share one per-minute allowance: a prompt over it, or over the prompts running at once, answers 429 RATE_LIMITED with Retry-After; nothing is started, so send it again after that many seconds. A prompt stops counting as running as soon as it finishes, fails or is stopped. If your account has a higher new-project rate from us, its prompt limits rise with it (running at once = twice the per-minute figure).
• A key over its requests per second answers 429 RATE_LIMITED with Retry-After (counted each second, Enterprise over 10 seconds: spread a burst over a few seconds).
• A pending invitation holds a seat until it is accepted, revoked or expires.
• Code editing, source download, GitHub, custom domains and mobile apps need a paid plan; reading your code and connecting Figma work on every plan.
• The API and MCP work on every plan. Any paid action needs a balance of at least 1 credit (reads and deleting a project always work).
• The API key the platform gives an app-builder project (handbook): 600 requests a minute and 300 prompts an hour (Ask us); its project creates count against the account's per-minute rate above.

#Account spending caps

To protect your balance from a runaway app or script, the whole account pauses when everything it spends — prompts, publishes and every project's running app — passes a cap:

While your balance is 0 or below, the caps are at most 100 credits an hour and 500 a day. The pause lifts by itself once the spend is back under the cap and the balance is above 0. Your caps are in Get Account Usage (account.accountCaps).

#Balance and suspension

Hosting, the database and other infrastructure keep running when the balance reaches 0, so a balance can go below 0. Then:

Nothing is deleted. Add credits (or turn on auto-recharge) and the sites come back by themselves within a minute.

#Project

#Monthly budgets

Every project has two monthly caps, in credits: development (prompts, publishes and project actions) and infrastructure (what the running app spends). New projects get:

Set them at creation (creditLimits in Create Project) or later in the project's Usage & limits or with Update Credit Limits. You can also switch any built-in feature off or give it its own budget (Feature Limits).

• What counts: development = the AI agent's prompts and the project's paid builder actions (publishes, rebuilds, restores, exports, code edits…); infrastructure = what the running app uses (hosting, database and every built-in feature). Get Credit Limits shows both for this month; List Projects at Their Limit lists the projects that reached one.

• Reset: the 1st of each month, 00:00 UTC.

• At the development budget: a new prompt or paid builder action answers 403 PROJECT_CREDIT_LIMIT_REACHED and costs nothing. A prompt already running when it crosses the budget is stopped: it finishes the step in progress and wraps up so that what it built works; it can go past the budget by that step plus at most 5 credits, all charged.

• At the infrastructure budget, two steps (the budget counts hosting, the database, files, AI, e-mail and every other built-in feature):

  1. When this month's infrastructure spend reaches the budget, the app's built-in features answer 429 FEATURE_LIMIT_REACHED: AI, e-mail, file uploads, web scraping and search, browser sessions, document scanning, PDFs and screenshots, speech, real-time rooms, vectors, connected accounts, and creating or changing scheduled jobs. The site, its database, hosting and stored files keep running.
  2. Hosting and the database still use credits. When the spend reaches the budget plus a reserve of 10 % of the budget (at least 5 credits: a budget of 300 pauses at 330, one of 20 at 25), only that project is paused: its site and preview show a paused page and its API keys answer 429 PROJECT_CREDIT_LIMIT_REACHED.

  Raising the budget re-checks both steps at once: the pause lifts when the new budget plus its reserve is above this month's spend, and the built-in features come back when the new budget is above it. Removing the budget (null) lifts both, and both end at the start of next month (UTC). The reserve is fixed.

• Changing a budget applies from the next prompt (a running prompt keeps the one it started with).

• Values: a budget is a number above 0, or null for none; 0 is refused. Infrastructure budgets (the app's and the development environment's) are applied as the whole number at or above the value, at least 1 (0.4 → 1, 12.5 → 13); the development budget exactly as set.

• Notice: the first time a project reaches a budget in a month you get the project.credit_limit.reached webhook and an e-mail, once per project, budget and month; the infrastructure budget sends one at each step (stage: builtins_stopped, then project_paused, with pauseAt).

#Development environment budget

Every project's development environment — the preview, the development database, the preview's scheduled jobs and the built-in calls made from the preview — has its own monthly budget: 100 credits unless you change it (maxDevInfrastructureCreditsPerMonth in Update Credit Limits or the project's Usage & limits; null = none). It is part of the infrastructure spend, and protects you from a preview job that keeps rewriting data.

When it is reached, only the development environment stops: the preview shows a paused page, its scheduled jobs are skipped and its built-in calls answer 429 DEV_INFRASTRUCTURE_LIMIT_REACHED. The published site, its database and its scheduled jobs keep running. You get a line in the project's chat, and once a month the project.credit_limit.reached webhook (category: "development_infrastructure", stage: "dev_stopped") and an e-mail. Your next prompt resumes it with one more full budget; raising the budget above this month's spend, removing it, or the next month (UTC) resumes it too.

#Built-in features

What each project's app may use. Each cell is per month · per minute.

• Change it: Upgrade. Monthly amounts are per project. On Free, Starter and Builder the per-minute amounts are shared by all the account's projects (except file uploads); on Professional and Enterprise each project has its own.
• Over a limit, the app's call answers 429 with Retry-After (per minute) or errorDetails.resetsAt (per month). Every call also costs credits, so the budgets above usually stop spending first.
• AI text answer length: up to 4,096 tokens per call on Free, 32,768 on Starter, Builder and Professional; no ceiling on Enterprise (32,768 when the call does not ask for one). A call that names no length gets that amount or the model's own maximum, whichever is lower. Upgrade.
• Cloud browser: 1 session open at a time on Free, 3 on paid plans (Ask us); a session lasts up to 15 minutes on Free, 60 on Starter, 180 on Builder and 360 on Professional and Enterprise (Upgrade).
• Web scraping: 1 call at a time per project; a call waits in a queue for its turn (Ask us).
• All built-in calls together: 100 a second per project (Ask us).
• Per visitor of the published site: 20 paid built-in calls a minute (AI, web, browser, screenshots), so nobody can spend your credits by calling a public AI page in a loop — ask the agent to change it (You); and 5,000 requests a minute, adjustable from 10 to 60,000 on paid plans with Update Rate Limit (You).

#Site requests

Each published site answers up to about this many requests, counted over 10 seconds; above it the site answers 429 Too many requests with Retry-After: 10, and nothing else of the project is affected:

#Emergency stop

A project whose app suddenly uses far more than normal is paused: its site shows a paused page, its built-in calls answer 429 PROJECT_PAUSED_RUNAWAY, and you get an e-mail and the project.kill_switch.fired webhook. It trips on any of:

It also trips on unusually costly use of built-in features within one hour. Prompts never count, nor does the hour's single largest call (one long video paid up front).

• Halfway: once the app has spent half of its hourly credits above, its image, video and speech AI calls answer 429 AI_MEDIA_PAUSED_THIS_HOUR until the hour ends; text AI and everything else keep working.
• Lifting it: the pause lifts by itself after 24 hours. Fix the cause, then lift it at once with Bring it back online in the project's workspace or with Release Runaway Pause (free, also clears the halfway pause).
• Change it: Upgrade. The thresholds are not raised per project; releasing the pause is in your hands.

#Unusual database usage

When a project's database suddenly uses far more than normal — its credits for the UTC day so far reach 3 × its usual day (the average of its last 7 days, once it has 3 days of history), or one hour reaches 10 × its usual hourly rate, and at least 5 credits above normal — you are alerted, once per project and UTC day:

• an e-mail, a line in the project's chat, and the project.usage_spike webhook ({ projectId, metric, value, normal, window, usedThisMonth, limit }).

The usage is charged as usual and nothing is paused by it: it continues until the project reaches its monthly infrastructure budget (then its built-in features stop, and at the budget plus its reserve the project is paused, see Monthly budgets) or your account runs out of credits. The usual cause is a scheduled job or a sync that rewrites whole tables on every run: ask the agent to update only what changed and to run it less often.

We recommend setting a monthly infrastructure budget on every project (in the project's Usage & limits, or with Update Credit Limits): it is what stops runaway usage.

#Database

Each project has a development and a live database (SQL, SQLite on Cloudflare D1).

How to write code that fits them: Design for the Limits.

#Files and storage

Over the storage limit an upload answers 429 STORAGE_LIMIT_EXCEEDED. The scheduled database backups are billed as file storage (rates) but do not count against this limit. Files uploaded through the API: 20 MB each and 300 a minute.

#Real-time

Change it: Upgrade. One room handles about 1,000 messages a second in total.

#Scheduled jobs

A job pauses after 3 failed runs in a row, unless it sets its own number.

#Domains

A domain's first year can cost less than its yearly renewal: both prices are shown before you buy.

#Agent, prompts and code

All API request limits: Errors & Limits.

#Idle projects

Any project wakes from a short idle period by itself on its next prompt.