← All guides

Base44 migration guide

Move your Base44 app from preview to a production VPS

Base44VPSDomain

Short answer

The same Base44 app running on your VPS with HTTPS, a stable deploy path, backups, and fewer monthly subscriptions.

Why this matters

The Base44 preview is fine, but the exported app still depends on platform defaults, hidden settings, or services you do not control.

Walkthrough

  1. 01

    Export the app into a repo you own

    Move the Base44 project into a codebase you can build, inspect, and deploy outside the builder.

    • Push the project into a GitHub repo you control.
    • Record the build command, runtime version, and package manager.
    • List every external dependency before you touch production.
  2. 02

    Recreate the runtime on the VPS

    The main production failure is usually missing configuration, not the code itself.

    • Add production env vars on the server or deploy panel.
    • Update callbacks, auth redirects, and webhooks to the live domain.
    • Run the app as a managed process with an auto-restart strategy.
  3. 03

    Deploy, smoke test, and measure savings

    A good migration gives you a live URL and a lower monthly bill.

    • Smoke test login, forms, API routes, and database writes.
    • Set up backups and a rollback note before launch.
    • Compare the old stack bills against the new VPS bill so the savings are obvious.

Where RepoAssistant fits

RepoAssistant moves Base44 apps to a VPS you own so production is cheaper, simpler, and actually under your control.