Base44 AI app builder
By Mari Luukkainen · 8 min read · Last updated
On this page
The Base44 AI app builder turns a chat into a working app with pages, a database, user logins and hosting, with no code or setup from you. Wix has owned Base44 since June 2025. The trade-off is lock-in: exported code still runs on Base44's backend, and Base44 does not support self-hosting.
I have not used Base44. I build in Cursor and Claude Code. Everything below comes from Base44's documentation and pricing page, checked on 4 November 2026, and from press coverage, each linked where it is used. The test near the end is a small app you build to judge it yourself.
Ask AI about this pageChatGPTClaudePerplexityGoogle AI ModeGrok
What is Base44?
Base44's docs describe it as "an AI-powered website and app builder" where "You do not need any coding or tech skills." The AI designs the app and handles "design, databases, signups, user permissions, and hosting" (quick start). You start from a prompt, from plan mode, from a website you own, or from a Figma design.
Wix announced the acquisition on 18 June 2025: about $80 million upfront plus earn-out payments through 2029 tied to performance (Globes). Wix said Base44 would stay a separate product (TechRadar). The Wix connection shows up in the product: payments run on "Base44 Payments powered by Wix," and you can buy a domain through Wix inside the editor (docs index).
Base44 counts two kinds of credits. Message credits pay for the AI building your app. Integration credits pay for what your app does once it runs, such as calling AI models or sending email (pricing).
Who is Base44 for?
Base44's own examples are a to-do list, an event signup page with reminders, a survey, a sales dashboard, a booking system or CRM, private file sharing with clients and a community site (quick start). That list matches what it is good for:
- Internal tools for a small business, where the app does not need to leave the platform.
- Non-technical founders testing an idea with real users and logins.
- People already on Wix who want payments and domains from the same company.
It is a poor fit if you want to own the full stack. If there is a real chance the app becomes a product you will run yourself, read the lock-in section before you start.
How does a first Base44 session go?
These steps follow Base44's quick start, with prompts you can paste.
- Go to app.base44.com and sign up. Your work is saved to your account.
- Turn on plan mode and paste the first prompt. Talk through the plan before the AI builds.
- Let it build and click through the preview.
- Use Discuss mode for questions. Base44 says it uses fewer credits and changes nothing until you are ready.
- Ask for changes one at a time in the chat.
- Before publishing, set data permissions and run the security scan (prompt below).
- Publish. Change the free Base44 address or connect your own domain on a paid plan.
I want an equipment checkout app for a 15-person office.
Staff sign in with email. They can see the list of equipment (laptops, cameras, projectors), check an item out for a date range and return it.
An item cannot be checked out by two people for overlapping dates.
Two roles: staff and admin. Only admins add or remove equipment and see the full history.
Before building, show me the pages, the data tables and who can read and change each table.On the equipment list, add a filter for "available today". Do not change anything else.Review the data permissions for every table. Staff must only see their own checkouts; admins see all.
List each table with who can view, create, edit and delete rows.
Then run a security scan and explain each finding in plain language.Base44's security overview says it plainly: "You are responsible for your app's security settings." The scan checks data permissions, exposed secrets and login gaps on every plan; static code analysis only runs on Builder and above (security overview).
Prices and limits (checked 4 November 2026)
The pricing page shows prices billed annually. I could not find the monthly-billed prices on Base44's own pages, so they are not listed here.
| Plan | Price (billed annually) | Credits a month | What you get | Source |
|---|---|---|---|---|
| Free | $0 | 25 message (at most 5 a day), 100 integration | Up to 5 apps, authentication, database, analytics. You can view the code but not edit it | Billing docs |
| Starter | $16 a month | 100 message, 2,000 integration | Unlimited apps, in-app code edits, custom domain, badge removal | Pricing |
| Builder | $40 a month | 250 message, 10,000 integration | Plus backend functions, GitHub two-way sync, ZIP export, model selection | Pricing |
| Pro | $80 a month | 500 message, 20,000 integration | Plus early access to new features | Pricing |
| Elite | From $160 a month | From 1,200 message (up to 8,200), from 50,000 integration | Plus premium support | Pricing |
Paid yearly plans include a free domain for the first year (billing docs). When you cancel, the change takes effect at the next billing cycle, and the pricing page says your apps stay live and your data stays in your workspace (pricing).
Look at which features need Builder. Without it you have no GitHub sync, no ZIP export and no backend functions, so on Free and Starter your app lives only inside Base44.
What was the Base44 security flaw in 2025?
In July 2025 researchers at Wiz found that Base44's endpoints for registering and verifying new users required no authentication. Anyone who knew an app's app_id could create an account in that app's private environment, and the app_id was visible in the app's URL. Wix patched it within 24 hours of the report and found no evidence it was exploited (SecurityWeek, 30 July 2025).
The fix was on Base44's side, and customers did not need to act. Still, it shows that "private" in a builder means private as long as the platform's own login code holds. For anything with personal data, test access from a logged-out browser yourself.
Can you leave Base44?
Not easily, and Base44's docs say so. On exporting code: "The exported code still relies on Base44 to run, so a ZIP is a copy of your code, not a way to move your app off Base44." The code uses the Base44 SDK for data, logins, backend functions and integrations, and "Base44 doesn't support self-hosting." To run the app fully outside Base44 "you'd need to replace those parts with your own backend and change the code that uses them" (developer tools).
What you can take out:
| What | How | Plan needed |
|---|---|---|
| Source code | ZIP export from the More actions menu, or GitHub two-way sync | Builder or higher |
| Data | Export each table as CSV from Data in the dashboard | Any |
| Version history | Not included in the ZIP. After you connect GitHub, versions from before the connection cannot be restored | Not applicable |
| A separate copy of the app | base44 eject clones it into a new project with its own app ID and an empty database, still on Base44's backend | Base44 CLI |
Sources: developer tools, GitHub integration, eject.
If you decide to move, plan it as a partial rebuild:
- Upgrade to Builder for a month and connect GitHub. The repository's default branch must be called main.
- Export every table as CSV.
- Clone the repository and open it in an editor or coding agent.
- Ask for an inventory of every Base44 SDK call with the prompt below.
- Set up your own database and login (for example Supabase or PostgreSQL with an auth library), import the CSVs, and replace the SDK calls one feature at a time.
- Ask your users to reset their passwords, since the login system changes.
This app was built on Base44 and uses the Base44 SDK. Do not change anything yet.
List every call to the Base44 SDK, grouped by feature: data reads and writes per table, login and user management, backend functions, integrations (AI, email, files).
For each group, propose what to replace it with on a standard stack and estimate how many files change.Do the inventory before you build anything big. The number of SDK calls is your real switching cost.
A one-hour test you run before paying
I designed this test and have not run it. Build the equipment checkout app above on the Free plan, then check:
- Make two staff accounts. Can staff B see staff A's checkouts?
- Open the published app in a private window, logged out. Does any equipment or checkout data load?
- Try to check out an item that is already taken for those dates.
- Run the security scan and compare its findings with what you found in steps 1 and 2.
- Export a table as CSV and open it. Is everything there?
- Count the message credits you used. With 25 a month, note how many changes the Free plan allows in practice.
What are the alternatives to Base44?
| If you want | Look at | Read |
|---|---|---|
| A builder whose backend you can move to your own Supabase | Lovable | What is Lovable |
| A builder with files, a shell, zip download and native mobile apps | Replit | Replit AI app builder |
| More builders, with free tiers compared | Bolt.new, v0, Bubble | Best AI app builders |
| Full ownership on your own computer and hosting | Cursor, Claude Code, Codex | What is Cursor, best vibe coding tools |
Frequently asked questions
Can I move a Lovable or Bolt.new project into Base44?
Yes. Base44 documents migrations from Lovable and Bolt.new, and from Salesforce, HubSpot, Shopify and WordPress, with notes on which data, pages and code come over from each.
Can Base44 make a phone app?
Base44 apps run in the browser. Its docs describe letting people add your app to their home screen and open it from there. You can also build and edit your app from your phone.
Can I use Base44 only as a backend for my own frontend?
Yes. Base44 offers its backend as a separate service with a JavaScript SDK and a CLI, with quickstarts for React, Vue, Solid JS and Refine projects.
Can I test my app without touching live data?
Yes. Turn on test data in App settings, and your preview uses a separate test database. You can share a testing link with it.
Can Claude, ChatGPT or Cursor work with my published Base44 app?
Yes, through App MCP. You set up MCP access for the app, choose which tools assistants can use and connect the assistant.
Next guideWhat is Cursor? →