How to export a Base44 project and keep building with your own AI

• A GitHub account.
• A Claude, ChatGPT or Cursor plan, or an API key. InstaWeb runs your own coding agent and sells no AI.
• A Mac, Windows or Linux computer. InstaWeb runs there, and you use it in your browser.

Not sure it is worth moving? See how InstaWeb and Base44 compare, including when Base44 is the better choice.

• Connect the app to GitHub

  On Builder or higher, turn on GitHub sync. Base44 syncs both ways through a branch that must be called main. The repository holds the frontend, the backend functions and the table definitions.

• Or download the code

  On Builder or higher you can also export a zip: a standard React project built with Vite, with the same backend functions and table definitions.

1. 1

   Install InstaWeb

   Sign in at instawebai.com with Google and paste the one command it gives you into a terminal. It installs InstaWeb and finds the coding agents you are already signed in to: Claude Code, Codex, Cursor or OpenCode.

2. 2

   Import the project

   On the Projects page, click + in the new-project box and choose Import from GitHub, then pick the repository. If you downloaded a zip instead, unzip it and choose Import from folder. InstaWeb runs the project on your computer with a live preview.

3. 3

   Keep building

   Type what you want, or click anything on the page and ask for a change. Your own agent edits the real source files, on the AI plan you already have, and each run is saved as a commit.

The repository holds the app's code. These live in Base44 and need moving, or setting up again, before the app works somewhere else:

• The backend comes in two stages

  The exported code uses the Base44 SDK to reach your app's backend on Base44, so it keeps working while your own agent builds on it. To leave Base44 completely, the database, sign-in and integrations have to be replaced, along with the code that uses them. Ask your agent to do this one piece at a time, for example onto Supabase.

• The data

  Export each table as a CSV file: Dashboard, then Data, the table, More actions, Export. There is no single export of every table, and the data isn't in the code export.

• Users

  Accounts are kept in Base44's built-in User table. We found no documented way to export users or their passwords, so plan for people to sign up again or reset their password on the new sign-in.

• Secrets

  Once a secret is saved, Base44 hides its value, even from you. Use your own copies of the keys, or create new ones.

• AI, email and image calls

  Calls to Base44's built-in AI, email and image services use its integration credits. Replace them with your own provider's key; Base44 says calls made with your own key don't use credits.

• Your domain

  Once the app is live on your host, point the domain's DNS records at it.

Base44 publishes no guide for moving off Base44. These steps are ours, based on what its documentation says the export contains and leaves out.

You can hand most of this to your agent: tell it which service the database and secrets are moving to, and it can make the changes in the code.

• Publish to your host

  Pick a host and the deploy agent builds the app, signs in through the host's own page and hands you the live link. Add the environment variables and secrets there. For a quick look before you commit to a host, you can get a free Cloudflare link without an account.

From here the app is plain code in your GitHub, running on your host. Nothing in it calls InstaWeb or Base44.

Everything said about Base44 here comes from the official pricing pages and documentation, read on 13 November 2026. Plans and features change: check them before you decide, and tell us if something here is out of date.

• Base44 pricing
• Base44 docs: credits
• Base44 docs: billing and plans
• Base44 docs: credit top-ups
• Base44 docs: AI chat modes
• Base44 docs: GitHub
• Base44 docs: developer tools and export
• Base44 docs: managing app data
• Base44 docs: app secrets
• Base44 docs: custom domains