Base44 Review: What the Code It Exports Actually Contains

None of the reviews ranking for base44 review on 14 August 2026 opens the exported code. They build one small app from a template, screenshot the editor, quote the plan prices, and close with a recommendation for something else. This one starts from a different place: 778 GitHub repositories confirmed as Base44 exports, with each one’s file tree and dependency list already recorded.

Base44 builds a working React app fast and hands back a real repository, and the code it exports is close to identical from app to app. Across 778 exported Base44 repos checked on 14 August 2026, 773 shipped React and 769 shipped Tailwind, on a scaffold that settles your architecture before you write a prompt.

That number needs a boundary around it. I have not built an app in Base44’s editor, so nothing here reports on prompt quality, editor feel, or how fast a credit balance drains. Those come from Base44’s documentation and from named third-party reviewers who did run a build. What I have is exported Base44 code at scale.

Base44, the Wix-owned AI app builder rather than Base64 the text encoding, is a real product owned by Wix, and the scam accusations attached to this query are billing arguments rather than breaches. Whether Base44 is safe owns the security reading of it. On money, the plans run from a free tier to $200 a month across five tiers, and the only tier that matters for anything below is Builder at $50, because that is where GitHub sync starts. What each Base44 plan costs per month does the credit arithmetic.

Is Base44 legit?

Yes. Base44 is a real product from a real company: Wix acquired it in June 2025 for roughly $80 million, six months after it launched. The complaints attached to this query are billing arguments about credits and refunds, not accusations that the product does not exist.

Wix’s own acquisition announcement, dated 18 June 2025 and checked again on 16 August 2026, puts the initial consideration at approximately $80 million plus earn-out payments through 2029, and says Base44 continues to operate as a distinct product and business. The company behind the charge on your card is Wix.com Ltd., which files publicly. That is the whole of the ownership question, and it is the part most people mean.

The rest of what legit is doing in that search is a question about behavior, and two things on this page bear on it. Of the 778 exported Base44 repositories checked on 14 August 2026, 744 carry product-specific pages rather than the default starter scaffold, which is not what a wall of abandoned demos looks like. And the certification claims are checkable rather than decorative: Base44’s trust center lists SOC 2 Type II and ISO 27001, checked 16 August 2026, which one review currently ranking for this query gets backwards. The correction is further down.

What none of that settles is whether any individual app built on the platform is secure. That is a different question with a different answer, and a legitimate platform can still hand you an app that lets one customer read another’s rows.

Does Base44 really work?

Base44 does work in the sense the question means: it produces apps that people ship. Of 778 exported Base44 repositories checked on 14 August 2026, 744 carried product-specific pages rather than the default starter scaffold, with a median of 201 counted source files. Working on the first prompt is a separate claim.

That second claim is where the reviewers who did run a build are worth more than I am. Martin Dubovic’s Base44 review, updated 5 June 2026, put a three-role group-exercise app on the Builder plan and reached a first working build in around ten minutes, then spent several hours and more than 40 prompts on debugging, using 48.4 of that plan’s 250 monthly message credits. He landed on 90 to 95 percent of the intended functionality and rated the product 4.9 out of 5. That shape, fast to something and slow to something correct, is what the complaints further down this page are made of too, whatever score a reviewer attaches to it.

The 744 repositories with product-specific pages say the same thing from the other end. They hold reservation systems, CRMs, marketplaces, dashboards and client portals, with page inventories that only make sense for the business each one was built for. A starter nobody came back to does not accumulate a page called CourseRevenue or ClientRemindersPage. Whether Base44 is good, then, splits by which half of the product you mean: the half that gets you to a running app, and the half you inherit afterwards.

What a Base44 export actually contains

AxonBuild keeps a candidate queue of AI-built repositories for its code review work. After a cleanup pass on 27 July 2026 it held 2,392 kept repositories, and the internal note from that pass recorded the thing that sent me here: Base44 exports were 58.7 percent of the queue and shared a near-identical scaffold, which raised the question of whether reading one tells you what the next says.

Re-derived on 14 August 2026, the queue breaks down like this.

Those 778 are the strict set, and everything below is measured only on them. They were found two ways: a GitHub repository search for the description string Base44 writes when it syncs, Base44 App: <name>, and a code search for filename:base44Client.js. Each one was then confirmed against the recursive git trees API, so the fingerprint is a file listing rather than a marketing badge. What the pipeline stored per repository is the tree, the counted source files, the package.json dependencies, and the first eight page names in alphabetical order.

Counted source files run from 39 to 7,092, median 201. The uniformity in that first block is the finding. Five of the 778 do not report React, and the entire set fits inside one stack: React, Vite, Tailwind, with TypeScript in about four out of five. So a Base44 export is one scaffold with your pages dropped into it, whatever the app turned out to be.

The base44/ directory is where the platform lives inside the repository. Base44’s project-structure documentation, checked 14 August 2026, places entities, functions, agents, connectors and auth configuration under it, with config.jsonc defining resource paths and .app.jsonc linking the local project back to the Base44 app. Every screen reaches the backend through src/api/base44Client.js, the SDK entry point that appears in all 778.

Two questions people normally answer with a showcase gallery fall out of the same set. The examples are the repositories: 744 of the 778 carry a page inventory that differs from Base44’s default five-page scaffold, so apps built with Base44 are public and countable rather than curated. The AI behind them is not a Base44 model. Its trust center, checked 16 August 2026, names OpenAI and Anthropic as the subprocessors handling API calls to the language models. The data sits in Base44’s own store rather than a Supabase project you connect: Base44’s entities documentation, checked the same day, describes each entity as a schema for documents in a collection in Base44’s MongoDB-compatible NoSQL database.

Now the part that matters for anyone who plans to hand this repository to a developer. The Admin page count is a floor rather than a rate, because the stored page list is capped at the first eight names alphabetically and Admin sorts early. Even as a floor, at least 334 of these apps ship an admin route as a client-side page in the bundle. Nothing in the repository decides who may open it. Base44’s data-permission documentation puts that decision in Row Level Security rules configured per entity in the app dashboard, and the repository carries those entities as declarations that Base44’s runtime enforces.

A Base44 export tells you what the app does. It does not tell you who is allowed to do it, because the rules travel as declarations and the thing enforcing them stays with Base44.

That is the honest limit of reading 778 repositories. The file trees establish what Base44 generates and how little it varies. They cannot establish whether any individual app’s permissions are correct, and the evidence fields were collected to screen repositories for eligibility rather than to audit them. One more limit belongs in the same breath: this is a set of public repositories, so it describes owners who turned on GitHub sync and left the result public, which is a slice of Base44’s users rather than all of them.

How that export compares with what Lovable hands back is a separate comparison and owns that ground.

What are the limitations of Base44?

Base44’s limitations are boundaries more than bugs. Repository sync starts at the $50 Builder plan, a cloned project still needs the app’s ID and backend URL to run, and an eject arrives with an empty database. Across 778 exports checked on 14 August 2026, 773 shipped React whether or not React suited the job.

Each of those has a documented source, and the first three are the ones people discover after they have committed.

The durable one is the last two lines of that list read together. The scaffold decides your architecture and the meter decides your ceiling, and neither is a bug anyone will fix, because both are how the product is designed to work. What Base44 integration credits cost at runtime works the meter through in detail.

There is a limitation the platform cannot help with either. Testing whether one signed-in customer can reach another customer’s records takes two accounts and someone willing to change an ID in a request, and that is not a thing a non-technical owner can settle by reading the dashboard. The two-account test is written out step by step on the safety page.

Base44 reviews and complaints: what the ratings are about

Read the complaints on this query and they sort into two piles that have almost nothing to do with each other.

The first pile is money. The r/Base44 thread asking whether Base44 actually works led its Google snippet on 14 August 2026 with “Base44 is complete garbage. It looks cool for the first 5 minutes, and then it becomes a nightmare.” The Trustpilot snippet Google displayed for the same query on the same day was about instruction-following: “It often does not follow my instructions correctly. Sometimes I ask it to remove one feature, but other parts are affected.” Both of those become billing complaints one step later, because a bug the model cannot fix costs message credits every time you ask again and nothing rolls over at the end of the month.

The second pile is code, and it is much quieter, because almost nobody writing about Base44 has opened the code. A stuck prompt loop and a permission rule that lets the wrong person read a row are different failures with different fixes, and only one of them shows up in a rating.

One correction belongs here, because it is currently ranking. Zite’s Base44 review, on the first page for this query on 14 August 2026, tells readers Base44 lacks SOC 2 and ISO 27001. Base44’s trust center lists both, checked 5 August 2026. Zite sells a competing AI app builder, which is worth knowing when a review of a rival ends with a recommendation to use the reviewer. What those certificates actually cover, and what they leave to your app, is Base44’s compliance scope.

Is Base44 worth it, and who does it fit?

Base44 is worth it when the app is an internal business tool and the platform running the backend is a feature rather than a debt. It fits poorly when someone must maintain the code independently, because all 778 confirmed exports checked on 14 August 2026 land on the same React scaffold and the backend still runs on Base44.

What this review cannot tell you is worth stating plainly rather than burying. It has nothing to say about how Base44’s editor feels to use, how good its prompts are on a hard feature, or what a month of real building costs in credits, because I did not do any of that. It says nothing about whether any of those 778 apps is secure. It is not a comparison against other builders, and it makes no claim that Base44 generates safer or less safe code than anyone else.

One question stayed open through all 778 of them. Base44 includes a security scan on every plan, and a repository gives no sign of whether its owner ever ran one. Every file in those trees is public, and the single most useful fact about each app is not in them.

Common questions about Base44

Is Base44 legit?

Yes. Wix acquired Base44 in June 2025 for initial consideration of approximately $80 million plus earn-out payments through 2029, and runs it as a distinct product. Its documentation, trust center and certification claims are public and checkable. The scam accusations attached to this query are disputes about message credits and refunds, not claims that the platform is fake.

Does Base44 really work?

Yes, with a split down the middle. It reliably gets you to a running app, and getting that app correct takes many more prompts than the first one. Of 778 exported Base44 repositories checked on 14 August 2026, 744 carried product-specific pages rather than the default starter scaffold, so people do finish and ship. Martin Dubovic’s hands-on test for allaboutcookies.org, updated 5 June 2026, reached a first working build in around ten minutes and then spent several hours and more than 40 prompts on debugging.

Can you really build an app with Base44?

Yes, and the evidence sits in public. Across the 778 GitHub repositories confirmed as Base44 exports on 14 August 2026, 744 carry a page inventory built for one specific business rather than the default five-page scaffold, and counted source files run from 39 to 7,092 with a median of 201. Those are working products with real page names, not template demos parked after an afternoon.

Can you make money from a Base44 app?

Yes, by charging for it. Base44’s payments documentation, checked 16 August 2026, says Stripe is available on the Builder plan and above, sets the integration up in a test environment first, and creates the live API keys once your Stripe account activates. Base44 builds the checkout flows from the products and prices you create in Stripe, so the pricing, the tax position and the refund policy stay yours.

Two things follow that reviews tend to skip. The same documentation tells you to send a signed-in customer to Stripe Checkout and then confirm the payment and update their account on the success page rather than relying on a webhook, which is logic you own and have to test. And paying customers turn the permission rules from a convenience into an obligation, because the day someone else’s card is on file is the day a cross-customer read stops being a bug.

What are the pros and cons of Base44?

The pro is speed to a real repository; the con is that the repository is always the same one. Across 778 confirmed exports checked on 14 August 2026, 773 shipped React, 769 Tailwind and 754 Vite, so the scaffold settles your architecture before you write a prompt. Sync to GitHub starts at the $50 Builder plan, a cloned project still needs the app’s ID and backend URL to run, an eject arrives with an empty database, and the backend keeps running on Base44 whatever the repository says.

Set against that: the export is real code you can read, the platform carries auth, storage, hosting and payments, and 744 of those 778 apps carry pages built for one specific business, which is what shipping looks like. The trade is worth making when the platform running the backend is a feature. It is a poor one when somebody has to maintain the thing independently.