Yes. On Builder or higher, you can export your Base44 app's code as a ZIP or connect it to GitHub, and you can host its front end elsewhere while keeping its existing Base44 services. Moving the website files does not require moving all of your data or replacing login. Leaving Base44 entirely is a separate project. This guide covers the export steps and the checks to make before changing your live domain. Base44 documents external frontend hosting.
What is Base44?
Base44 is an AI app builder. You describe an app in a prompt, and it generates a working full-stack application (a React frontend plus backend functions and data entities) that you keep refining through more prompts in its own editor. It is a different category from a website builder like Squarespace or Wix: the output is closer to a small web application with a database behind it than a marketing page. If you used Lovable instead, the question is the same but the mechanics differ. See moving a Lovable project to your own hosting for that platform's export path.
What plan do I need to export anything?
Builder or higher. Base44's documentation says: "Downloading a ZIP file and connecting to GitHub both require a Builder plan or higher" (Base44 docs, "Developer tools"). The Free and Starter plans sit below that line. Check Base44's pricing page for current plan prices. Data export as CSV is a separate feature, covered below, and the documentation does not gate it the same way.
How do I export my app's code as a ZIP?
In the app editor, open Code and click the Export project as ZIP icon at the top right of the code view (Base44 docs). You get a zip archive of your app's code.
Base44 also documents an API route to the same export: a GET request to /api/apps/{app_id}/coding/export-to-zip on app.base44.com, authenticated with an API key, which "downloads the app's source code as a zip archive" reflecting "the app's current saved code" (Base44 API reference). Base44 flags this endpoint as beta: "This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production." Use the in-editor button for a one-off export, and use the API only if you are automating exports and can tolerate that instability warning.
Once you have the zip, unzip it and confirm it runs on its own before you plan anything around it. That is the first check for any AI builder's export, and it is the fastest way to find a Base44-specific dependency before you rely on it in production.
How does Base44's GitHub sync work?
It is a separate mechanism from the ZIP download, with the same Builder-or-higher requirement: "GitHub 2 way sync requires the Builder plan or higher," and only app owners can make the first connection (Base44 docs, "GitHub Integration"). The setup:
- From the Dashboard, click the GitHub icon and select Connect to GitHub.
- Authorize the Base44 GitHub app and choose the organization and repositories it can access.
- Create a new repository for your app, or connect an existing one.
- Clone the repository locally, run
npm installandnpm install -g base44@latest, then authenticate withbase44 login. - Run
base44 linkto connect your local clone to the app, thenbase44 devto start local development against the hosted backend. - Push your local changes to the connected repository. Base44 describes the connection as 2-way sync, so they flow back into the app.
Base44 describes this as two-way: "When you connect your app to GitHub, your changes are synced to the connected repository automatically." Two limits matter before you connect. First, Base44's documentation adds "there's no option to manually push updates from your Base44 app to GitHub," so sync happens on Base44's own timing, not on a button you control. Second, it has an irreversible side effect: "After you connect GitHub to your app, you cannot use Version History to revert to versions from before the GitHub integration." Do not connect GitHub until you are past the experimental, prompt-and-discard phase of building the app, or you lose Base44's own undo history for everything that came before.
Base44's pricing page states the ceiling separately: "Two-way GitHub sync exports the full source code to your own repo at any time," alongside the broader claim "You own everything you build on Base44: your code, your data, your users" (base44.com/pricing). Read "at any time" as the sync's ongoing, automatic nature, not a manual export button. The documentation above is specific that there is no manual push.
How do I export my app's data?
Data exports separately from code. Click Dashboard in your app editor, then Data, select a table, click the More actions icon, and click Export. "Your data downloads as a CSV file you can open in spreadsheet software such as Excel or Google Sheets" (Base44 docs, "Managing your app data"). The documented steps work on one table at a time, so repeat them for every table your app uses. Base44 frames this as useful "for backup, analysis, or to use in other tools," such as handing data to an accountant or building a custom report outside the app.
What can't I take with me?
- An independent copy of every hosted service. A code export is not a transfer of Base44's running infrastructure. You can keep those services connected to an externally hosted front end. Replace them only if you also want to leave Base44's services.
- A verified connection on a new domain. External frontend hosting is documented, but each destination still needs a working build, permitted API access, and tested login redirects. Do not assume an uploaded ZIP is already a working deployment.
- Version history predating a GitHub connection. Connecting GitHub is a one-way door for Base44's own revert feature, as noted above.
How do I set up a custom domain?
Custom domains are "available on the Starter, Builder, Pro, and Elite plans," not Free (Base44 docs). You can connect a domain you already own by configuring DNS records Base44 provides, or buy a new domain through a Base44-integrated registrar. Base44 states it issues and renews the SSL certificate automatically once a domain connects. Documented limits: "up to 150 domains and subdomains to a single app, and up to 350 domains in total across your account."
What are the steps for moving hosting?
- Confirm your plan. Builder or higher for code export; Starter or higher for a custom domain.
- Export the code. Use the in-editor Export project as ZIP, or connect GitHub if you want ongoing sync while you are still iterating inside Base44.
- Keep the existing app and services active. A CSV backup is useful, but moving hosting alone does not require a database migration.
- Build the exported code before uploading browser files to a static host. A source ZIP and a built folder are different things.
- Test a temporary deployment. Check login, logout, saved data, user permissions, internal links, and direct page reloads. Keep server secrets out of browser files. If you also want to replace Base44's services, complete and test that separate migration first.
- Move the domain last. Update DNS only after the independent copy works on its own temporary URL, so your live domain never points at something broken. If your domain was registered through Base44 rather than connected from elsewhere, read transferring a domain away from your website builder first. Its general steps and DNS-record risks apply whichever builder issued the domain.
- Keep the Base44 app running until the standalone version works end to end. Exporting does not delete the original.
Apps that use Base44's hosted backend still need that service, and may keep its charges, wherever the front end is hosted. Do not cancel the original account until the features you need work on the new URL. For other builders, see moving an AI builder's project to your own codebase.