Why teams leave Base44 in 2027, and when they should stay
Five pressure points appear in Base44's own documentation once an app carries real business records. Each one has a different remedy, and not every remedy means leaving.

Contents
Base44 is growing quickly and remains a capable way to build a first app. The reasons teams look elsewhere are not complaints about quality but structural features of a hosted builder, and Base44 documents most of them itself. This guide sets out each one, with its source, and what it means for a business app.
1. Credits that are counted after the work
Base44 bills in two currencies. Message credits are spent when the AI builds or changes the app; integration credits are spent when the live app sends an email, calls a language model, runs a workflow step or invokes a backend function1. Base44 publishes typical figures: about 0.5 credits for a small text change, 3 to 4 for an app-wide change, about 1 integration credit per email, and about 1 credit per 100 backend-function invocations1.
Three details shape the bill. The exact cost of an action can vary and is calculated only after it runs, and there is no way to preview an integration credit cost in advance. Unused credits expire at each monthly reset. And when the balance runs out, the actions that use credits pause until the reset, unless the plan is upgraded1. For a hobby project that is a minor inconvenience. For an app that sends customer confirmations, it means a production feature can stop on a predictable date.
2. Code you can take, a backend you cannot
On the Builder plan and above, Base44 syncs code to GitHub in both directions and offers a ZIP download containing the frontend, the backend functions and the structure of each table23. Its pricing page states that customers own their code, data and users4.
The documentation is precise about the limit of that ownership. The exported code uses the Base44 SDK to reach its backend for data, logins, backend functions and integrations; a ZIP is "a copy of your code, not a way to move your app off Base44"; and Base44 does not support self-hosting of the database, login system or integrations3. Records come out separately, one table at a time as CSV, while secrets and app users stay in Base4435. In practice, leaving means rebuilding the backend, which is why the migration guide starts with an inventory.
3. Limits that appear as the data grows
Base44 hosts and scales the app, with no limit on how many people use it at once. The limits are on data and requests6:
| Limit | What Base44 documents |
|---|---|
| Records per request | Up to 5,000 on every plan; longer lists must load in pages6 |
| Database size per app | 200 MB (Free), 2 GB (Starter), 5 GB (Builder), 10 GB (Pro), 25 GB (Elite), 50 GB (Business), none on Enterprise, for apps created from 18 October 20265 |
| Largest single record | 100 KB up to Builder, 250 KB on Pro to Business, 1 MB on Enterprise5 |
| Requests | A per-minute allowance per signed-in person; visitors on one office network share one; admin calls share one per app6 |
When the database is full, the app cannot add records until data is deleted or the plan is upgraded5. Most internal apps never reach these figures. An app that logs every order, message or sensor reading eventually will.
4. Access controls on the higher plans
Every Base44 app has data permissions, a security scan and encrypted secrets, and the platform states SOC 2 compliance7. The controls most businesses ask for later sit higher up. SSO for apps requires Business or Enterprise (Elite only for workspaces created before October 2026)7. Data residency comes with Business, and audit logs and activity monitoring with Enterprise8.
The permission model also asks for care. Base44 sets permissions automatically as it builds, but warns that if they are wrong, "the wrong people could view or change data", and a rule set to All Users allows the action without signing in9. Base44 places responsibility for these settings on the app owner7. Independent research shows why that matters: Escape found more than 2,000 vulnerabilities and more than 400 exposed secrets across some 5,600 public apps built on vibe-coding platforms10. In July 2025, Wiz also found a platform-level flaw that let an outsider register on private Base44 apps; it was fixed in under 24 hours and Wix reported no evidence of past abuse11.
5. A product inside a larger company
Wix agreed to buy Base44 in June 2025, when it had six employees and had raised no outside money, for an initial $80 million plus milestone payments due in 202912. Base44's website now carries a Wix.com copyright and links payments to Wix Payments13. In its second-quarter 2026 results, Wix credited Base44 with much of its growth and said it had expanded the Base44 team and its advertising14.
That is a sign of commitment rather than risk. What changes is the nature of the dependency: pricing, plan limits and roadmap now reflect the priorities of a listed company with its own targets, including a stated aim of raising Base44's gross margin to about 60%14. Teams that want those decisions in their own hands look for a system they can host and change themselves.
When staying is the better decision
Signs a higher Base44 plan is enough
- The app serves one team, holds modest data and stays well under the record and size limits above.
- Nobody needs SSO, audit logs or data residency, or the Business plan's cost is acceptable.
- The integration credits the app uses each month are stable and known from the usage page.
- No one on the team would maintain a separate backend if the app moved.
A path to deciding
- Open the credit usage page and record a typical month of message and integration credits by source1.
- Check each table's size against the plan's database and record limits5.
- List the access requirements the business now has: SSO, roles, approvals, audit trail.
- Write down the reason for leaving in one sentence. Cost, lock-in, scale, access or mobile each point to a different builder in our ranking.
- Export a full copy now, code and every table, whatever you decide, so the decision is never forced by an incident.
If the answer is lock-in or access control, the comparison in the main guide shows which builders address each. If it is cost, the cost guide sets out the numbers.
Questions buyers ask
Why are people leaving Base44?
The reasons documented in Base44's own pages are credit-based billing whose cost is known only after an action runs, exported code that still depends on Base44's backend, no self-hosting, per-request and database size limits, and SSO and audit logs reserved for higher plans. Some teams also weigh Wix's ownership. Which one matters depends on what the app has become.
Does Base44 lock you in?
Partly. You can sync code to GitHub or download it on the Builder plan and above, and export each table as CSV. But Base44 says the exported code still relies on its backend for data, logins, functions and integrations, and it does not support self-hosting, so running the app elsewhere means replacing that backend.
Did Wix change Base44 after buying it?
Wix bought Base44 in June 2025 and has since invested heavily: in its second-quarter 2026 results it credited Base44 with much of its growth and increased Base44 advertising and engineering. We found no published plan to discontinue or restrict Base44. Ownership matters mainly as a question of whose roadmap and pricing decisions the app depends on.
Sources
- Credits. Base44 Docs. Accessed 8 Nov 2026.
- Sync your app with GitHub. Base44 Docs. Accessed 8 Nov 2026.
- Base44 developer tools (working with code, GitHub and exporting your code). Base44 Docs. Accessed 8 Nov 2026.
- Base44 Plans & Pricing. Base44. Accessed 8 Nov 2026.
- Managing your app data (database limits and exporting data). Base44 Docs. Accessed 8 Nov 2026.
- Optimizing app performance (scaling and usage limits). Base44 Docs. Accessed 8 Nov 2026.
- Base44 security: an overview. Base44 Docs. Accessed 8 Nov 2026.
- Base44 for enterprises. Base44 Docs. Accessed 8 Nov 2026.
- Managing data permissions. Base44 Docs. Accessed 8 Nov 2026.
- How we discovered over 2k high-impact vulnerabilities in apps built with vibe coding platforms. Escape, 29 Oct 2025. Accessed 8 Nov 2026.
- Critical vulnerability in AI vibe coding platform Base44. Wiz Research, 29 Jul 2025. Accessed 8 Nov 2026.
- Wix acquires Israeli vibe coding co Base44. Globes, 18 Jun 2025. Accessed 8 Nov 2026.
- Turn an idea into a working app or website with AI. Base44. Accessed 8 Nov 2026.
- Wix beats expectations as AI platform Base44 drives 15% revenue growth in Q2. Ynetnews. Accessed 8 Nov 2026.
Updated 8 Nov 2026: First published.