Is Base44 production-ready? The limits to know before you scale
Plenty of real businesses run on Base44. Whether yours can depends less on the builder than on a handful of documented limits: how many records a request returns, how long code may run, how credits meter your live app, and which backups you get. Here they are in one place.
Updated 8 min readBy the Unbase44 team
On this page
The limits, in one table
These come from Base44’s own documentation and pricing, checked in October 2026:
| Area | Limit | Where Base44 documents it |
|---|---|---|
| Records per request | 5,000 at most, since 27 November 2025, with no sign in the response that it was cut short | Managing app data, Apps API: entities |
| Dashboard table | Shows up to 5,000 records | Managing app data |
| Backend function run time | 5 minutes, whether called directly, by an automation or as a workflow step | Backend functions |
| Automation run time | 3 minutes per run, for apps on the older automations engine | Creating automations |
| Schedules | At most once every 5 minutes, for automations and workflows | Creating automations, Creating workflows |
| Integration credits | A monthly pool per workspace, from 100 on Free to 50,000 or more on Elite | Pricing, Credits |
| Backups | Automatic backups you can restore: 7 days on Elite, 30 days on Enterprise; 30-day restore of deleted records on all plans | Backup & Restore |
| Management API rate limits | Per workspace, from 1× on Free and Starter to 10× on Enterprise | Rate limits |
| Backend functions and workflows | Builder plan and above | Credits, Creating workflows |
| Storage | No overall limit; uploads through your live app up to 50 MB per file (100 MB for video) | Billing and plans, Using media |
| App users | No limit published on any plan | Pricing |
| Data location | US by default; EU or UK for new apps on Elite and Enterprise | Privacy and security |
None of these is unusual for a managed platform. What matters is knowing which ones your app will meet first.
What each limit means in practice
The 5,000-record cap
A page, report or function that fetches a whole collection in one request gets the first 5,000 records and no error. An admin dashboard’s totals quietly stop adding up, an export misses rows, a function that emails “all customers” skips some. Base44’s own advice is to paginate, loading 50 to 200 items at a time. Search your app for any list or filter call without a limit, and for anything that computes totals in the browser.
Five minutes for functions, three for automations
Long jobs have to be split into batches. Base44’s documentation gives its own example for automations: a run that should send 1,000 emails but only manages 600 in three minutes sends those 600 and stops. Imports, syncs with other systems, bulk emails and data clean-ups are the usual casualties. Design them to process a batch, save their position, and continue on the next run.
Integration credits meter your live app
Credits aren’t only for building. Every built-in service your running app uses draws on the same monthly workspace pool (Credits). Base44’s published estimates:
- about 1 credit per email (about 2 from a custom domain), per file upload, per image, and per push notification;
- about 1 credit per LLM call on the default Automatic model, and from about 3 on a model you choose, depending on the model and the length of the prompt and answer; about 3 or more per in-app agent message;
- about 1 credit per 10 workflow steps, plus whatever the steps do;
- about 1 credit per 100 backend function invocations, on workspaces billed that way.
Reading and writing your database is free. When the pool runs out, actions that need credits fail until the monthly reset, and the people using your app see a generic error that doesn’t mention credits. A successful launch, a marketing email or a busy agent can empty the pool mid-month. Watch the usage page, and know your upgrade path before you need it.
Backups depend on your plan
Deleted records can be restored for 30 days on every plan. Point-in-time recovery of your data, meaning automatic backups you can review, download as CSV or restore, is an Elite and Enterprise feature, kept for 7 days on Elite and 30 days on Enterprise (Backup & Restore). Those backups cover your table records only: uploaded files and your app’s users are left out. Below Elite, a bad bulk update is only as recoverable as your last export. Base44’s terms also make you responsible for your own data backups. If your data matters, schedule CSV exports or an API script, and keep the files outside Base44. Every route, step by step: how to export your Base44 database.
Storage: no overall cap, but per-file limits and credits
Base44 doesn’t set an overall storage limit per app or per plan (Billing and plans). The limits are per file. When people upload through your live app, images, documents, data files and audio can be up to 50 MB each, and videos up to 100 MB (Using media). Files you upload while building have their own, mostly smaller, limits.
Two things matter more than the cap. Each upload through the app costs about one integration credit, so an app built around photos or documents spends credits as it grows. And uploaded files sit outside the backups described above, and outside the EU or UK data residency option: Base44’s privacy page says media files stay in the US whatever region your data is in.
Users: no published cap
Base44 doesn’t publish a limit on how many people can sign up to your app, on any plan. What growth changes is everything around them: an admin page that loads every user in one request meets the 5,000-per-request cap, each email your app sends costs credits, and a busy sign-up day that triggers emails or AI calls draws on the same monthly pool as everything else. Sign-in sessions last up to 90 days by default, according to Base44’s store guide.
Rate limits are per workspace
Base44’s management API counts requests per workspace, not per person, with plan multipliers from 1× to 10×. Listing and counting records, for example, share a base allowance of 70 requests a minute per app. Limits for your app’s own traffic aren’t published, so bulk operations should back off and retry when they get a 429 response.
The platform sets the terms
Your plan, prices, credits and features can change, and Base44’s terms let it suspend access without notice in some circumstances. That isn’t a reason to avoid Base44, but it belongs in any honest production plan: keep exports, and know how you’d leave.
Testing and staging on Base44
Base44 has no separate staging deployment with its own address and database: your published app always uses production data. Two features cover most of what a staging environment is for.
Test data (Builder plan and above). Turning on Test Data in your app’s settings creates a second, empty database. The dashboard and the preview can switch between production and test data, and a testing link lets teammates or clients try unpublished changes against the test data only (Testing your app with test data). Nothing syncs between the two, so copy in the records you need for testing.
Branches. A branch keeps its own chat, preview, pages and code until you merge it into main, and you publish from main (Working with branches). What a branch doesn’t separate is just as important. Records are the same live data everywhere, and secrets, connectors, automations, workflows, in-app agents, settings and domains are shared with main. Changes to those happen on main. Base44’s advice is to switch the preview to test data while you work on a branch.
Put together: build on a branch, preview it against test data, share the testing link for review, merge, then publish. Be careful with anything that leaves the app, such as emails, payments or calls to other services. Those connections are shared with your live app, so assume a test that sends an email or calls another service really does it, unless that service is in its own test mode.
A production-readiness checklist for any platform
- Backups you’ve actually restored once, stored outside the platform.
- Pagination everywhere a list can grow.
- Batching for any job that could run long.
- A cost ceiling: an estimate of monthly credit or usage cost at your expected traffic, and an alert before you reach it.
- Monitoring: uptime checks, error reports and logs you look at. Base44 has app logs and an activity monitor; use them.
- Security review: every entity’s access rules checked against who should see what. Base44 offers a security scan, and our guide to Base44 security lists what to check.
- A platform outage: you know where to check Base44’s status and what to do while an outage lasts. See is Base44 down?
- Secrets stored as secrets, never in page code.
- Testing on a copy: Base44 offers test data and branches, so don’t try risky changes on production data.
- An exit plan: what you’d do, and how long it would take, if you had to move.
When it’s time to move
Owners usually move when a few of these line up: the 5,000-record cap and time limits force constant workarounds; credit usage turns growth into a billing problem; a customer asks for EU data, a BAA or a security review; or the monthly plan costs more than the infrastructure it stands for.
Unbase44 moves the whole app to accounts you own, and changes the nature of these limits rather than pretending they vanish:
- No credits. AI, email and storage are billed by the providers you connect, at their prices, and database reads and writes cost what your database costs.
- Limits become settings. The record cap and function time limit start at Base44’s values, so your app behaves exactly as it did, and you can raise them when your server can handle it.
- Capacity is a slider. A busier app needs a bigger server or database plan, not a different pricing tier.
- Backups and region are yours. Turn on your database provider’s automated backups, and put the app where your users and obligations are.
Questions and answers
Can Base44 handle thousands of users?
Base44 doesn’t publish a limit on app users for any plan. What usually constrains a growing app is the 5,000-records-per-request cap, the function and automation time limits, and integration credits consumed by the live app, for example by the emails it sends. Design around those and many apps run fine.
How much storage does a Base44 app get?
There’s no overall storage limit per app or per plan. Files uploaded through your live app can be up to 50 MB each, or 100 MB for video, and each upload costs about one integration credit. Uploaded files aren’t included in Base44’s backups.
What happens when integration credits run out?
Actions that need credits, such as sending email, AI calls, uploads and workflow steps, fail until your monthly reset, and your users see a generic error. You can upgrade your plan to get more straight away.
Does Base44 back up my data?
Automatically, on Elite (7 days of backups) and Enterprise (30 days), covering your table records but not uploaded files or users. On other plans you can restore deleted records for 30 days, and anything else depends on your own exports.
Is there a staging environment on Base44?
Not as a separate deployment: the published app always uses production data. On the Builder plan and above, Test Data gives you a second database for the dashboard, the preview and a shareable testing link, and branches let you build changes before merging them into main. Branches share live records, secrets, connectors and workflows with main, so switch the preview to test data while you work.
Sources
Checked on November 10, 2026. Base44 changes quickly; if something here is out of date, tell us.
- Managing your app data (5,000-item limit, deleted records)
- Apps API: entities
- Backend functions (5-minute limit)
- Creating automations (3-minute runs, 5-minute interval)
- Creating workflows
- Credits (integration credit costs)
- Base44 pricing
- Backup & Restore (Elite and Enterprise, retention, what is covered)
- Apps API: rate limits
- Billing and plans (storage)
- Uploading and managing media (per-file upload limits)
- Privacy and security (media files stored in the US)
- Testing your app with test data
- Working with branches
- Submitting your app to app stores (session duration)
- Base44 terms of service (suspension, your own backups)