Is Base44 Legit? The 7 Checks Before You Pay

Yes. The terms of service on base44.com name Wix.com Ltd. as the company you are contracting with, and the footer of the pricing page carries the same copyright: Base44 has belonged to Wix since June 2025. Legitimacy is settled. Reversibility is not, and that is the check worth running before you enter a card. Here it is in seven steps.

The seven checks, in order

The first three cost nothing and take twenty minutes of reading. The last four cost one month of a paid plan, the honest price of finding out.

1. Read who is on the contract. Open the footer of any page, then the first paragraph of the terms of service. You want the legal entity that takes your money, not the brand on the logo. Both say Wix.com Ltd., and the terms carry a date, June 22, 2026. A tool whose terms name no entity and show no date is where the answer is actually no.
2. Find the tier that owns your exit before the tier that fits your budget. On the pricing page today, GitHub integration shows up in the plan highlights from Builder up, at 40 dollars a month billed annually. Starter, at 16, stops at unlimited apps, in-app code edits and a connected domain. Buy for the feature you need on your worst day.
3. Price the failure, not the build. The terms state that fees are non-cancelable and non-refundable, and that a chargeback counts as a breach of your payment obligations, after which your access may be automatically disabled. Pick the amount you can lose without arguing, and call that the cost of the trial.
4. Build the ugliest true version of your data model, then change it. Twenty real rows, then one schema change: a free-text column becomes four fixed statuses. Three prompts is the ceiling. If it still fails, revert to the last good version instead of prompting a fourth time.
5. Turn the sync on before you need it. Clone the repo and try to run it. The frontend and the backend functions travel. The entity schemas your app stands on do not, and the data leaves table by table.
6. Take your own backup on day one. The terms make you responsible for your own backups, and let the company delete customer data at its sole discretion once your subscription ends. Export every table once, by hand, so you know how long it takes.
7. Open the sharing settings before you send the link. The terms warn that default configurations may permit public access to your data or your app. Check them on the app you just built, not the one you plan to build.

Who is on the other side of the contract

The question gets asked because the category churns: an AI app builder wants a card number before it has earned anything, and half of last year's names are gone. The answer takes sixty seconds. The terms open with a binding agreement between you and Wix.com Ltd., "which operates the Base44-branded services". Wix bought the company in June 2025 for a reported 80 million dollars.

That buys you a counterparty with an address, an auditor and a support obligation someone can be held to. It does not buy you response times, an uptime guarantee below the enterprise tier, or a promise the product keeps its shape. Acquisition moves the risk from "they take my money and disappear" to "this drifts away from what I needed". Only the second one is still yours to manage.

If a star rating sent you here, the distribution is its own subject, and I went through it in Base44 reviews: the star rating is a timestamp, not a verdict.

“

Legit is not a company question. It is a question about what leaves with you when you stop paying.

”

The exit door starts two tiers up

Here is the gap a legitimacy check exists to find. The pricing page FAQ says: "Two-way GitHub sync exports the full source code to your own repo at any time. Nothing is locked to the platform." The plan grid on that same page lists Github integration in the highlights for Builder, Pro and Elite. The Starter list stops at in-app code edits and a connected domain.

The promise and the grid disagree, and the disagreement costs 24 dollars a month. That is not fraud. It is the ordinary distance between a marketing answer and a feature row, and it is why step two exists: the exit is a feature, the feature has a price, and you learn that price before you pay the first one.

Then read what leaves. The code does. The entity schemas, the part your app actually stands on, stay on the platform, and your rows come out as per-table exports. The terms are plain about the rest: exported data leaves at your sole risk, with no warranty about "the functionality, compatibility, or usability" of it anywhere else. Nobody hides this, and almost nobody reads it before the month they need it. Whether the trade suits you depends on who owns the backend you build on, which is the argument in Base44 vs Lovable: the difference shows up in week two, and it is the test I apply to every tool in Replit alternatives: pick the one you can leave.

Non-refundable, and the move that makes it worse

Three money rules sit in the fine print, and they compound. Fees are non-cancelable and non-refundable unless local law says otherwise. Credits are non-refundable for the model's own mistakes, so a generation that breaks your app is billed like one that works. And a chargeback is defined as a breach of your payment obligations, which can automatically disable your account.

Read them together and the trap is obvious. The user who feels cheated does the instinctive thing, disputes the charge with the bank, and takes down the app they were angry about, with the data still inside it. The order that protects you is the reverse: export first, cancel from account settings, then argue. Cancellation takes effect at the next cycle and your apps stay live meanwhile, which is exactly the window the export needs. Never dispute the card of a platform that is still hosting your data.

The test that settles it in an afternoon

Legit is not a company question. It is a question about what leaves with you when you stop paying, and one small test answers it better than any review.

Rebuild your real data model, badly and quickly, with twenty rows of true data in it. Then make the change nobody makes on day one: turn one free-text column into four fixed statuses, and watch the rows that already carry values. That is where the honeymoon usually ends: the first build is where all of these tools look identical, and the second week is where they stop. Give it three prompts, then revert and believe what you saw.

If the schema change lands and the cloned repo runs on your machine, pay for the year with a clear head. If neither happens, you found out for the price of one month instead of the price of one quarter.

FAQ

Is Base44 a scam? No. It is a real platform operated by Wix.com Ltd., with dated terms of service and a working product behind the demo. The complaints you find concern credit consumption, support speed and export limits, which are contract problems, not fraud.

Who owns Base44? Wix, since June 2025, for a reported 80 million dollars. The terms of service, updated June 22, 2026, name Wix.com Ltd. as the operator of the Base44-branded services.

Can I get a refund from Base44? Assume no. The terms say fees are non-cancelable and non-refundable unless local consumer law requires otherwise, and credits spent on a failed generation are not returned. Where statutory cancellation rights exist, that carve-out is the door, not the chargeback.

Can I export a Base44 app and run it elsewhere? Partly. GitHub sync gives you the frontend and the backend functions from the Builder plan up. The entity schemas stay on the platform and data comes out per table, so running the app elsewhere means rebuilding the backend it talked to.

Is Base44 safe enough for client data? It can be, but the contract puts the responsibility on you: backups, access controls and sharing settings are the customer's job, and the terms warn that default configurations may expose data publicly. Check the defaults on every app before sharing a link.