Skip to content
Unbase44

Free analysis · From $99, once per app

Own your Base44 app. All of it.

Unbase44 copies your whole Base44 app to accounts in your name: code, backend, data, users, functions, automations, AI agents and files. Start with just GitHub and get the full code in a private repo in a few minutes. Putting it online on your own hosting is included, now or later.

Sign in with Base44 to see what your app contains and its exact price, free. You pay only when you get your code.

  • Users keep their passwords
  • Your code in GitHub first, hosting later
  • Your Base44 app keeps running
  • If it fails, a full refund
The same app before and after the move: first at your-app.base44.app, hosted on Base44; then at your-app.com, running from a GitHub repo, a database and hosting in your own accounts.
Unbase44

The catch

Base44 lets you download the code. Not the app.

The ZIP download and GitHub sync give you the frontend and your function files. Everything that makes that code work stays on Base44’s servers, so an exported app still calls Base44 for every sign-in, every record and every email.

What the export gives you

  • Your React frontend source
  • Your backend functions’ code, without the server that runs it
  • Table definitions (ZIP only, not GitHub sync)

Run it on your own machine and it still talks to Base44.

What stays behind on Base44

  • The backend your code calls
  • Every record in your database
  • Users, roles and their logins
  • A place for functions to run
  • Automations and workflows
  • AI features and agents
  • Secret values
  • Realtime updates
  • Uploaded files

Unbase44 moves this column too. That is the difference between exporting code and owning an app.

Every way to export from Base44, and what each leaves out

How it works

Your code in your GitHub in five steps. Online whenever you’re ready.

The first three cost nothing and commit you to nothing. After step 5 the code is yours. Steps 6 to 8 put the app online on your own hosting, now or later, included in the price.

Start with step 1
  1. 01

    No commitment

    Sign in with Base44

    Approve Unbase44 on Base44’s own sign-in page. We never see your Base44 password.

  2. 02

    No commitment

    App analysis

    We read your app and list what it’s made of: pages, tables, records, users, functions, workflows, agents and files.

  3. 03

    No commitment

    See your price

    A fixed, one-time price for this app, with anything that needs attention flagged before you go further.

  4. 04

    A few minutes

    Connect GitHub

    Connect your GitHub account. It’s the only account you need to get your code.

  5. 05

    One-time

    Pay, get your code

    Pay once for this app. Its full code, a Base44-compatible server and docs go into a private repo on your GitHub. Nothing changes on Base44.

Then, whenever you want

  1. 06

    Included

    Pick hosting

    Choose where it runs (Railway or your own server) and in which region, right away or later. It’s included in the price.

  2. 07

    Automatic

    Move to your hosting

    Connect your hosting with click-by-click steps. Your data, users and files are copied and the app is deployed. You can follow every step.

  3. 08

    Yours

    Live

    Your app runs on your accounts. Point your domain at it whenever you’re ready.

Your options

Three ways forward, side by side.

Staying put is a real option, and so is a rebuild. Here is how they compare with moving the app you already have.

Recommended

Move with Unbase44

What you pay
Once per app, from $99, plus hosting at your providers’ prices
Before you decide
A free analysis, a security check of your app and your exact price, before you connect any account
Getting your code
Connect GitHub, pay, and the full code is in your private repo in a few minutes; hosting can wait
Time to live
Minutes for the migration, plus time to open accounts
Where code and data live
Your GitHub, your database, your hosting
Your users
Same accounts, same passwords
How the app behaves
Same code, same API, same data
Switching over
The copy starts in test mode: no emails, texts or payments go out until you switch
Limits
Settings you control, on a server you size
Region and compliance
Pick your region; a HIPAA-ready AWS setup is coming soon
Keep building with AI
Claude Code, Cursor, any developer; AI editor coming soon

Stay on Base44

What you pay
A monthly plan for as long as the app runs, with credits that reset each month
Before you decide
Nothing to decide
Getting your code
ZIP or GitHub sync of the frontend and function files, on the Builder plan and up
Time to live
Already live
Where code and data live
Base44’s servers; code exports on the Builder plan and up
Your users
Unchanged
How the app behaves
Unchanged
Switching over
Nothing to switch
Limits
Plan credits, per-request caps and run-time limits
Region and compliance
US by default; EU or UK for new apps on top plans
Keep building with AI
Base44’s AI builder

Hire someone to rebuild it

What you pay
A project fee, usually in the thousands
Before you decide
A quote once someone has scoped the app
Getting your code
When the rebuild is finished
Time to live
Weeks to months
Where code and data live
Wherever the new stack runs
Your users
Usually everyone resets their password
How the app behaves
A new app that has to be re-tested
Switching over
A cutover once the new app is tested
Limits
Whatever the new stack imposes
Region and compliance
Your choice, built from scratch
Keep building with AI
Depends on the new stack

Comparing migration tools? Ask each one whether users keep their passwords, whether you see the price before connecting accounts, whether you can test the copy before switching, and whether you get the code before setting up hosting. Unbase44 vs EscapeBase44, point by point

Pricing

One price per app. Paid once.

The migration is priced once, per app. It isn’t a subscription. After that, your hosting and other providers bill you directly for what your app uses.

What the price covers

  • Your exact price after sign-in, before you connect anything or pay
  • Priced to what your app contains, once, never monthly
  • The whole app: code, data, users, functions, workflows, AI, files
  • A private GitHub repo you own, with documentation
  • Going live on your own hosting, now or later
  • If the migration fails, a full refund

First app

From $99, quoted for your app

Second app

25% off

Every app after that

50% off

Hosting, database, email and AI usage are billed by those providers to your own accounts, at their prices. You see what each option is expected to cost before you choose.

Compare with your Base44 plan

One-time, per app

From $99

You pay when you get your code.

Your app’s full code lands in a private repo on your GitHub in a few minutes, and nothing changes on Base44. Putting it online on your own hosting is included, now or later. If the migration fails, you get a full refund.

See my price

Questions first? Read the FAQ

Trust

Built to be trusted with your app.

You are giving us access to something that matters. Here is precisely what we touch, what we keep, and what happens if something goes wrong.

If the migration fails, you get your money back.

You pay for a migrated app, not for an attempt. If we can’t deliver your repo, or the move to your hosting fails and we can’t fix it, we refund you in full.

  • Read-only on Base44, with one disclosed exception

    We read your app and change nothing. To copy your secret values, we may add a small temporary helper function to your Base44 app and remove it as soon as the values are read. If your plan doesn’t allow that, you paste them in and nothing is added.

  • Your keys, encrypted and revocable

    Provider keys are checked on the spot, encrypted at rest and used only for your migration. Delete them from Unbase44 whenever you like, or revoke them at the provider.

  • Nothing routes through us afterwards

    Your live app runs entirely on your accounts: no proxy, no shared domain, no Unbase44 server in the path. If we disappeared tomorrow, it would keep running.

  • Your data isn’t kept

    Code, records and files pass through our migration workers on their way to your accounts and aren’t retained once the migration completes; we keep only the analysis summary (counts and sizes). Your users’ passwords never pass through us at all.

  • No downtime, no forced switch

    Your Base44 app keeps running during and after the move. You check the new one, then point your domain at it when you’re ready.

What moves

Everything your app is made of comes with it.

Not a copy of the frontend with nothing behind it. The whole app, top to bottom, running the same way on accounts you own.

  • Your frontend

    Your original React code, unchanged apart from where it points.

  • The backend

    An open, documented Base44-compatible server that speaks the API your app already uses.

  • Every record

    All tables and rows, with IDs and relationships intact, in your own MongoDB.

  • Users and logins

    Accounts, roles and passwords. Email, one-time codes, Google and Microsoft sign-in.

  • Backend functions

    Your Deno functions run as they are, with their secrets.

  • Automations and workflows

    Schedules, data triggers and multi-step workflows, including Base44’s newest engine.

  • AI features and agents

    LLM calls and in-app agents, running on the AI provider account you connect.

  • Files and uploads

    Copied into storage you own, and served from there.

  • Email

    Sign-in codes and app emails go out through your own email provider.

  • Integrations and connectors

    Built-in integrations and connected services, re-authorized once under your name.

  • Access rules

    Row- and field-level security, roles and private pages, enforced by your server.

  • Realtime

    Live updates and subscriptions keep working as before.

  • SEO settings

    Titles, descriptions, sitemap and robots rules, written into your pages by your server.

  • The code, in your GitHub

    A private repo with docs, a Docker setup and push-to-deploy.

  • You pick where it runs.

    Railway, or any Linux server you can reach over SSH, in the region you choose. Hetzner, MongoDB Atlas and AWS are coming soon.

What you gain

What changes when the app is yours.

Owning the stack removes a list of limits that come with renting a platform. Each one has a longer explanation if you want the detail.

  • No platform ceiling

    No shared credit pool that pauses features mid-month, and no platform rate limits on your traffic. Limits such as request size and function run time start at Base44’s values, so nothing behaves differently, and become settings you control.

    Read: Production readiness
  • No monthly platform fee

    Pay hosting and database providers directly, at their prices. Many small apps fit in low-cost tiers.

    Read: Cancelling Base44
  • Your region, your choice

    Run the app, its database and its files in the EU or wherever your users and your obligations are.

    Read: GDPR and data residency
  • Coming soon

    A HIPAA-ready option

    Put the app, database and files in your own AWS account, where you can sign the agreements HIPAA requires.

    Read: Base44 and HIPAA
  • Real SEO control

    Your server writes each page’s title, description and social tags, and you decide on redirects, caching and rendering.

    Read: Base44 SEO
  • Coming soon

    Your app in the app stores

    iPhone and Android apps built from your repository: one click for Android, and iPhone builds straight to TestFlight without a Mac.

    Read: Base44 and the App Store

Security

See what your app exposes. Fix it as you move.

In an app built with AI it’s easy to leave data open: a table with no read rule, a function that never asks who is calling. The free analysis checks your app before you decide anything, and the move can close what it finds.

What the free check looks at

  • Tables with personal details, like emails or phone numbers, that anyone can read
  • Tables where anyone can edit or delete other people’s records
  • Backend functions that run with full access without checking who called them
  • Webhooks that accept requests from anyone
  • API keys written into the code, where every visitor can read them

What the move can fix

  • Functions only your automations, workflows or agents run are locked, so nothing outside the app can call them
  • Tables you pick are limited to each record’s creator and admins
  • Functions you pick are limited to signed-in users or admins
  • Every moved app is served over HTTPS only, limits function calls from each address, and shows no internal details in errors
  • docs/SECURITY.md in your repo lists every change and how to undo it
Check my app for free

The check reads your app’s rules and code. It doesn’t try anything against your app or change it.

Keep building

Keep building your way.

Your app becomes a normal, well-documented project. Point an AI coding agent at it, hand it to a developer, or open it yourself.

  • Ready for AI coding agents

    A README, plus AGENTS.md and CLAUDE.md, explain the project to Claude Code, Cursor or Codex from the first prompt.

  • Push to deploy

    Merge to main and your hosting redeploys. No dashboard to click, no platform to publish from.

  • Runs on your laptop

    The Docker setup starts the app and its database locally with one command.

  • Any developer can pick it up

    React, TypeScript, Deno and MongoDB, documented. Nothing proprietary to learn first.

github.com/you/your-app · private
your-app/├─ src/├─ base44/├─ server/├─ docs/├─ Dockerfile├─ docker-compose.yml├─ README.md├─ AGENTS.md└─ CLAUDE.md
$ git push origin maindeployed

AI editorComing soon

Describe a change in chat and watch it happen, like building on Base44. The difference is that the changes land in your own repo, where you can see and keep every one.

FAQ

Questions before you move.

Something we haven’t answered? Write to hello@unbase44.com. A person reads every email.

Before you start

What is Unbase44?

Unbase44 is a migration tool for apps built on Base44, the AI app builder. It moves the whole app, including its backend, data, users with their passwords, functions, workflows, AI agents and files, into a GitHub repository, hosting and database in the owner’s own accounts. Unbase44 is made by Codama and is independent of Base44 and Wix. You sign in with Base44, get a free analysis and a one-time price from $99, and pay once, when you get your code.

What exactly does Unbase44 move?

The whole app, including everything Base44’s own export leaves out. 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.

How is Unbase44 different from other Base44 migration tools?

Compare them on four things. Your users keep their passwords with Unbase44; a move that copies only the user list leaves everyone to reset their password or switch to sign-in codes. You see your exact price, and a free security check of your app, before you connect any account. You get the full code in your GitHub after connecting only GitHub, and put the app online later, included. And the copy starts in test mode, so nothing goes out to your users until you switch. Our comparison with EscapeBase44 goes point by point.

Do I need to be technical to use Unbase44?

No. You sign in with Base44 and see your price. To get your code you connect one account, GitHub; if you don’t have one, a free GitHub account is enough, and the app shows you where to open it. Putting the app online later works the same way, with click-by-click steps for each account. If you work with a developer, they get a conventional, documented codebase instead of a platform to learn.

How long does a Base44 migration with Unbase44 take?

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.

Which Base44 plans does it work with?

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.

What if my app uses something you can’t migrate?

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.

Your users and your data

Will my users have to reset their passwords after leaving Base44?

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.

Does anything change on my Base44 app?

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.

Will my Base44 app go down during the migration?

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.

Where does my data go during the migration?

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.

Can the app run in the EU, or in another region I choose?

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.

After the move

Where does my app run afterwards, and on what?

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 any Linux server you can reach over SSH. Hetzner, MongoDB Atlas and AWS are coming soon.

What do I get in the GitHub repo?

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.

Can I keep building with AI after I leave Base44?

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.

Do workflows and automations come across?

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.

What about AI features, email, Google sign-in and connectors?

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.

Can I keep my custom domain?

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.

Do I still depend on Base44 or on Unbase44 afterwards?

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.

When should I cancel my Base44 subscription?

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.

Price and trust

Who makes Unbase44, and is it legit?

Unbase44 is made by Codama (Codama Advanced Engineering, Inc., a Delaware company) and is independent of Base44 and Wix. You sign in through Base44’s own device sign-in, so Unbase44 never sees your Base44 password, and the free analysis shows your price before you connect any account or pay. You pay by card through Stripe when you get your code, with a full refund if the repository can’t be delivered or the move to your hosting fails and can’t be fixed. The server code in your repository is MIT-licensed, and after the move the app depends on nothing of Unbase44’s.

How much does Unbase44 cost?

A one-time price per app, from $99, shown after you sign in and before you commit to anything; it depends on what your app contains. You pay it when you get your code, and going live on your own hosting is included. A second app gets 25% off its quote, and each one after that 50% off.

What will hosting cost each month?

Whatever your providers charge, paid to them directly; there is no Unbase44 subscription. As of October 2026, Railway’s Hobby plan is $5 a month and includes $5 of usage, and you pay more only if your app uses more. Before you choose, you see what each option is expected to cost. AI and email usage is billed by those providers to your own accounts. The cost calculator compares your Base44 plan with running the app yourself over one to three years.

What happens if an Unbase44 migration fails?

You get your money back. You are paying for a migrated app, not for an attempt: if we can’t deliver your repository, or moving the app to your hosting fails and we can’t fix it, we refund you in full. Write to us within 30 days of paying.

How do you handle my provider keys?

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.

Does the move make my app more secure?

It can. The free analysis checks who can read and change each table, which backend functions skip the access rules, which webhooks accept anything, and whether keys are written into the code. During the move, functions only your app runs are locked, and you can limit tables and other functions with a tick. Every moved app is also served over HTTPS only and limits function calls from each address. Your repo’s docs/SECURITY.md lists every change.

Is it allowed to move my app off Base44?

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.

See what your app is made of, and what moving it takes.

Sign in with Base44 and get the full analysis and your price. Nothing moves, and nothing is charged, until you say so.

Free analysis · Your Base44 app keeps running throughout