Move Your Base44 Website or Web App to Your Own Hosting

Review the Project for External Hosting

Before moving the hosting, identify which parts of the project can move and which Base44 services need to stay connected.

External Hosting Review

Identifies the frontend framework, build command and output directory, production environment variable names, how the project uses the Base44 SDK, and which Base44 services it depends on — then returns a short external-hosting checklist without migrating or replacing anything.

Review this Base44 project specifically for external production hosting. Identify: - the frontend framework and project structure - the production build command - the build output directory - every environment variable required in production — names only - how the project uses the Base44 SDK - whether it uses Base44 authentication - which Base44 database entities it uses - any backend functions - realtime features - storage or file uploads - AI features, integrations, payments, email, or external APIs - anything that depends on the final production domain Determine which parts can be hosted externally while continuing to use the existing Base44 backend. Do not migrate or replace the database, authentication, or backend services. Check that the production frontend build succeeds and that no private secrets are exposed in client-side code. Give me a short external-hosting checklist when finished.

Open Base44

Base44 apps currently use a React/Vite frontend with Base44-managed backend services including database, authentication, functions, and realtime. The frontend can be hosted elsewhere and continue communicating with Base44 through its SDK.

Connect Base44 to GitHub

In Base44, open the project and connect it to GitHub.

Use:

GitHub Connect to GitHub

Authorize Base44, then create a repository for the project.

The latest project files are available in GitHub

NOTE

Base44 supports two-way GitHub sync on the Builder plan or higher, and changes made in Base44 are automatically synced to the connected repository.

You'll use this repository as the source for the external deployment.

Get Hostinger Base44 Hosting

This tutorial uses Hostinger for the production hosting.

Get Hostinger Web App Hosting

Deploy your Base44 project from GitHub while keeping the services your app depends on connected.

USED IN THIS TUTORIAL

https://www.hostg.xyz/SHJyP

Deploy the Repository from Hostinger

In Hostinger:

Websites Add Website Deploy Web App

Choose GitHub as the source Connect your GitHub account Select the Base44 repository Review the detected build settings Add any production environment variables identified in Step 1 Deploy the project

Hostinger currently has a dedicated Base44 hosting workflow and supports GitHub, ZIP, and AI-assisted Web App deployments.

Start with the temporary live URL before connecting your real domain.

Test the Temporary Deployment

Open the temporary deployment and test the features that depend on Base44. Check:

Sign up and login

Database reads and writes

User-specific data

Backend functions

Realtime features

File uploads if used

AI or external integrations

Forms and important user flows

The external frontend should continue communicating with the Base44 backend through the SDK.

IMPORTANT

Do not assume that exporting the project also migrated the Base44 database or authentication infrastructure. Base44 explicitly states that managed hosting, authentication infrastructure, and database infrastructure are not part of the normal code export.

Fix any production configuration issues before connecting your real domain.

Connect Your Production Domain

Once the temporary deployment works correctly, connect your production domain in Hostinger. Verify:

The domain opens the correct website or web app

HTTPS is active

Authentication works

Database-connected features work

Backend functions still work

External integrations remain connected

Production URLs are updated where required

Your Base44 frontend is now running on your own hosting while its Base44 backend services remain connected.

Continue building normally in Base44.

With GitHub sync enabled, your workflow becomes Base44 → GitHub → Hostinger.

Changes synced to the connected production branch can then be rebuilt and deployed on Hostinger. Base44's current GitHub integration supports ongoing two-way sync rather than requiring a new export for every change.