Own your Base44 app. All of it.

The whole app, not just the code Base44 already lets you download. Your React frontend, a backend that answers the same API your app already calls, every record in every table, your users and their passwords, backend functions and their secrets, automations and workflows, AI features and agents, uploaded files, email, connectors, access rules, realtime updates and SEO settings. The result is a private repository in your GitHub account, deployed to hosting and a database you control.

No. You sign in with Base44, choose where the app should run, and follow click-by-click instructions to open or connect each account. Most of your time goes into creating those accounts; the migration itself runs on its own. If you work with a developer, they get a conventional, documented codebase instead of a platform to learn.

The migration itself usually runs in minutes. Add the time it takes to open any provider accounts you don’t have yet, and a little longer for apps with a lot of uploaded files, which take longer to copy.

You sign in with the Base44 account that owns the app, and the analysis tells you up front if your plan limits anything we can read automatically. The main example is secrets: their values can be read automatically while your plan includes backend functions. If it doesn’t, you paste them in from your app’s settings on Base44.

The analysis lists everything your app uses before you pay, and flags anything that needs attention. If something would block the migration, you find out then and you aren’t charged. Unusually large or complex apps get a personal quote by email instead of an instant price.

No. Base44 never hands out password hashes, so each user’s first sign-in on the new app is checked against Base44 once and then stored as your app’s own securely hashed password. From then on Base44 isn’t involved. That is why you keep the Base44 app published until your active users have signed in once. Their passwords never pass through Unbase44: the check runs from your own server.

We read your app; we don’t edit it. There is one exception, and we would rather say it plainly: to copy the values of your secrets (the API keys your functions use), Unbase44 may add a small temporary helper function to your Base44 app, read the values, and remove it straight away. If your plan doesn’t allow that, you paste the values in yourself and nothing is added.

No. Your Base44 app keeps running, untouched, while the new copy comes up on your accounts. Nothing changes for your users until you point your domain at the new app, and you decide when that happens.

From Base44 to your own accounts, through our migration workers. Nothing is kept on our side once the migration completes, apart from the analysis summary (counts and sizes) we use for your quote and for support.

Yes. You choose the provider and the region during setup, and the app, its database and its files run there. Our guide to GDPR and data residency explains where Base44 keeps data today.

On accounts you own. The stack is your original React frontend plus our open, documented Base44-compatible backend (Deno and TypeScript) on MongoDB. Railway is the recommended host because the app, its database and its file storage live in one account; you can also use Hetzner or any Linux server you can reach over SSH. MongoDB Atlas and AWS are coming soon.

A private repo in your GitHub account with the whole app: your frontend, your app’s definitions (tables, functions, agents and workflows), the backend runtime, a Docker setup, and documentation, including a README plus AGENTS.md and CLAUDE.md so AI coding tools understand the project from the first prompt. Pushing to main redeploys the app.

Yes. Open the repo in Claude Code, Cursor, Codex or any editor; the documentation is written for coding agents as much as for people. A chat-based AI editor, similar to building on Base44, is coming soon. And because it is standard React, TypeScript and Docker, any developer can pick it up.

Yes, both. Base44’s newer workflows and its older automations are supported: schedules, data triggers, conditions, waits and the backend functions they call run on your own server. How workflows migrate goes into the detail.

They come across, pointed at accounts you control. AI calls go to the AI provider you connect and email goes out through your email provider, billed to you. Google or Microsoft sign-in and connectors such as Google Sheets or Slack need authorizing once with your own credentials, because Base44 keeps OAuth tokens to itself; the steps are spelled out for you.

Yes. Your domain stays wherever you bought it. When you are ready, you change its DNS records to point at the new app; the page you land on after the migration shows exactly which records to add.

Not on Unbase44: nothing routes through us once your app is live, and it keeps running if we disappear. On Base44, only for the short password window described above. Once your active users have signed in on the new app, you can switch the Base44 app off.

After the migration, not before. While your plan is active, secret values can be read automatically. Once your app is live on your accounts, you can cancel: the Base44 app stays up on the Free plan, which is all the password check needs. Our guide to cancelling Base44 has the details.

A one-time price per app, shown after you sign in and before you commit to anything; it depends on what your app contains. A second app gets 25% off its quote, and each one after that 50% off. During the beta, migrations are free.

Whatever your providers charge, paid to them directly; there is no Unbase44 subscription. Before you choose, you see what each option is expected to cost for your app. AI and email usage is billed by those providers to your own accounts.

You don’t pay. You are paying for a migrated app, not for an attempt.

Keys you enter are checked with the provider on the spot, encrypted at rest and used only for your migration. You can delete them from Unbase44 at any time and revoke them at the provider whenever you like; your running app doesn’t need us to hold them.

Base44’s terms say you own the code and apps it generates for you, and the migration uses only the access you grant with your own Base44 sign-in, to the app you choose. We are not lawyers and can’t give legal advice; our reading of the terms walks through what they say.