Is Base44 production-ready? The limits to know before you scale

The limits, in one table

These come from Base44’s own documentation and pricing, checked in September 2026:

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;
• 1 to 15 credits per LLM call depending on the model, and at least 3 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 and version history you can download or restore, is an Elite and Enterprise feature. Below that, a bad bulk update is only as recoverable as your last export. If your data matters, schedule CSV exports or an API script, and keep the files outside Base44.

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.

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.
• 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.