Can you self-host a Base44 app? The complete answer
Base44 doesn’t offer a self-hosted or on-premises edition. You can host a frontend elsewhere, and Base44’s CLI runs a local server for development, but your live app’s database, sign-ins, functions and integrations stay on Base44’s servers. A real self-hosted setup needs a backend that speaks Base44’s API. Unbase44 is one: it copies the whole app, with its records, users and functions, onto that kind of backend on your Railway account or any Linux server you reach over SSH.
Updated 9 min readBy the Unbase44 team
On this page
- 01What self-hosting a Base44 app has to include
- 02What you can run yourself with Base44’s own tools
- 03The missing piece: a backend that speaks Base44’s API
- 04What a self-hosted app looks like with Unbase44
- 05Vercel and Netlify: why a frontend host alone isn’t enough
- 06AWS, Azure or a VPS
- 07What it costs to run
- 08What you take on when you self-host
- 09Questions and answers
- 10Sources
What self-hosting a Base44 app has to include
“Self-hosting” gets used loosely, so it’s worth being precise. For a Base44 app to run without Base44, every one of these has to exist somewhere you control:
| Piece | What it does |
|---|---|
| Frontend hosting | Serves the built React app to browsers |
| The API | Answers every data, sign-in, function and integration call the app makes |
| Database | Holds every record, in a shape the API understands |
| Sign-in | Accounts, passwords, one-time codes, password resets, Google or Microsoft sign-in |
| Security rules | Row- and field-level rules, enforced on every request |
| Function runtime | Runs your TypeScript functions on Deno, with their secrets |
| Scheduler and triggers | Fires automations and workflows on time and on data changes |
| File storage | Stores uploads and serves them back, public or signed |
| Email, AI and integrations | Sends email, calls language models, generates images |
| Realtime | Pushes live updates to open pages |
| Domain and TLS | Your address, with a certificate |
Hosting the frontend is the easy part. Everything else on that list is what Base44 provides, and it’s what makes a self-hosting plan real or not.
What you can run yourself with Base44’s own tools
Base44 doesn’t offer a self-hosted or on-premises edition, and doesn’t document one. It does give you three tools that are sometimes mistaken for one.
Hosting the frontend elsewhere. Base44 can be used as a backend service behind your own frontend. Its developer tools overview says that when you go live you can either keep hosting the frontend elsewhere or deploy its built files to Base44 hosting. Hosted elsewhere, your pages load from your server while data, sign-in, functions and integrations still run on Base44. It’s a legitimate setup, but it moves the least important piece.
The local development server. base44 dev runs a backend on your machine for development. Functions run locally on Deno, records live in an in-memory database that empties when you stop it, and uploads go to a temporary folder. OAuth sign-in and built-in integrations such as email and AI are forwarded to Base44, and automations don’t run locally (Local development). It’s built for testing changes safely, not for serving users.
Ejecting. base44 eject copies an app into a new, separate Base44 project with its own app ID and an empty database (eject). The copy is still hosted by Base44.
The missing piece: a backend that speaks Base44’s API
Your app’s code was written against the Base44 SDK. The frontend asks the SDK for records, and the SDK sends an HTTP request to a Base44 endpoint for that entity, with the query written in MongoDB’s operator syntax. Functions build a client from the incoming request and call back into the same API, sometimes with a service role that bypasses the security rules. Uploads return URLs on Base44’s storage. Live pages subscribe to changes over a realtime connection.
So there are two ways to self-host for real:
- Rewrite the app for a different backend. Replace every SDK call with calls to Supabase, Firebase or your own API, translate the data model and security rules, and port the functions. It’s a project measured in weeks, and every user resets their password at the end. Our Supabase guide walks through it.
- Run a backend that answers the same API. If something on your server responds to the SDK exactly as Base44 does, the app doesn’t need rewriting. The frontend is rebuilt pointing at your server, and the functions run unchanged.
The second is what Unbase44 migrates you to.
What a self-hosted app looks like with Unbase44
After a migration, your app is a repository in your GitHub account, laid out like this:
your-app/
├─ src/ your original React frontend
├─ base44/ entities, functions, agents, workflows, config
├─ server/ the Base44-compatible backend (Deno + TypeScript)
├─ docs/ architecture, local development, deployment
├─ Dockerfile
├─ docker-compose.yml
├─ README.md, AGENTS.md, CLAUDE.md
The backend is open and documented, and it runs on MongoDB, the same kind of document database Base44 uses, so records move without translation and keep their IDs. It serves the frontend, the API, the sign-in pages and realtime updates from one address.
You choose where it runs:
| Option | What runs there | Good for |
|---|---|---|
| Railway (recommended) | App, MongoDB and file storage in one account | Least to manage; deploys on every push |
| MongoDB Atlas (coming soon) | A managed database, paired with your chosen host | Managed backups and scaling for the data |
| Hetzner (coming soon) | App and database on a server of your own | Low monthly cost; data centres in Europe and the US |
| AWS (coming soon) | App, data and files in your AWS account | Organisations already on AWS; the HIPAA-ready option |
| Any Linux server over SSH | App and database with Docker Compose | Your own hardware or any cloud VM |
On Railway, pushing to main redeploys. For local development, the Docker setup starts the app and its database on your laptop with one command. Users keep their passwords: each person’s first sign-in is checked against Base44 once and then stored as your app’s own hash, which is why you keep the Base44 app published until your active users have signed in.
Vercel and Netlify: why a frontend host alone isn’t enough
“Base44 to Vercel” and “Base44 on Netlify” usually mean one of two things, and the answers differ.
Your frontend on Vercel, with Base44 still as the backend. This works, and Base44 documents it: you can keep hosting your frontend elsewhere and use Base44 as the backend (developer tools). The exported app is a standard Vite build, so either host can serve it. Sign-ins, records, functions and integrations still go to Base44, along with its plan and credits. You’ve moved the part that was never the problem.
The whole app on Vercel or Netlify, with no Base44. Not with those services alone. They’re built to serve a frontend and run short-lived functions, while a Base44 app’s backend needs things that stay put:
- A database and file storage. Neither host is one. You’d add separate services for both.
- A process that stays awake. Automations and workflows have to fire on schedule and on data changes, and live pages hold realtime connections open. Netlify’s function limits are 60 seconds for a normal function, 30 seconds for a scheduled one and 15 minutes for a background one. Vercel functions run for at most 5 minutes on Hobby and 800 seconds on Pro, with 30 minutes in beta (limits).
- Containers that keep running. As of October 2026 Vercel can run a Docker image, but as a stateless function. Vercel’s own comparison with Render says each instance keeps nothing between requests, scales down after five minutes without traffic, and isn’t run as a background worker or cron job. Its WebSocket support is in public beta, and each connection closes when the function reaches its time limit (Vercel).
None of that is a flaw; those platforms are designed for a different job. A Base44 app on infrastructure you own needs a server that runs continuously, which is why Unbase44’s hosting options are Railway and Linux servers rather than frontend hosts. If you rewrite the app for Supabase instead, Vercel or Netlify can serve the rebuilt frontend while Supabase does the backend work.
AWS, Azure or a VPS
“Any Linux server over SSH” covers more than a box under your desk:
- AWS. An EC2 or Lightsail instance running Linux is a server you reach over SSH (AWS: connect with SSH). AWS as a built-in hosting option, including a HIPAA-ready setup, is coming soon.
- Azure. A Linux virtual machine works the same way (Azure: create a Linux VM).
- Any VPS. Hetzner, DigitalOcean, OVH or a local provider: if you can SSH in, the app can run there.
Unbase44 connects over SSH, installs the app and its database with Docker, and sets up HTTPS automatically. On a cloud provider, check the firewall first: AWS calls it a security group and Azure a network security group. It needs to let in SSH and web traffic on ports 80 and 443, or the certificate can’t be issued and visitors can’t reach the app.
A server of your own also means the jobs listed further down (updates, backups, monitoring) are yours. If that’s more than you want, Railway handles the machine for you.
What it costs to run
The monthly Base44 plan goes away. Base44’s pricing runs from $16 a month (Starter) to $160 a month (Elite) billed yearly, or $20 to $200 monthly, and the plan also sets your monthly credits.
Instead, you pay providers for what you use:
- Hosting and database. On Railway, the Hobby plan is $5 a month including $5 of usage (Railway’s pricing, as of October 2026); busier apps cost more, in proportion to their traffic and data. On your own server, it’s whatever the server costs. During setup you see what each option is expected to cost before you choose.
- AI. Calls go to the AI provider account you connect and are billed per use by that provider.
- Email. Sign-in codes and app emails go through your email provider, on its plan.
The migration itself is a one-time price per app, from $99, paid when you get your code. Putting the app online on your own hosting is included.
What you take on when you self-host
Self-hosting shifts some jobs from the platform to you. Be clear-eyed about them:
- Updates. On a managed platform like Railway, the operating system and database engine are handled for you. On your own server they’re yours to patch.
- Backups. Turn on automated database backups (Atlas and Railway both offer them) and test a restore once. On Base44, below the Elite plan, you had no automatic backups at all, so this is often an improvement.
- Monitoring. Set up uptime checks and look at logs when something feels slow.
- Security. Keep secrets in your host’s secret settings, restrict who has access to your accounts, and review your app’s access rules.
- Capacity. If traffic grows, resize the server or database. It’s a setting, not a support ticket.
For most owners the right balance is a managed host: you own the accounts and the code, and the provider handles the machines.
Questions and answers
How do I move my Base44 app to my own server?
Base44 has no self-hosted edition, so the app needs a backend of its own that answers the same calls. Unbase44 moves the whole app, with its records, users and functions, onto a Base44-compatible backend on your Railway account or any Linux server you reach over SSH, run with Docker and with HTTPS set up automatically. Users keep their passwords, and the code goes into your own private GitHub repository. The migration guide sets out the order of the move.
Does Base44 have a self-hosted version?
No. Base44 doesn’t offer or document a self-hosted or on-premises edition. You can host a frontend elsewhere, and Base44’s CLI runs a local server for development, but your live app’s data, sign-in, functions and integrations run on Base44.
Can I host my frontend on Vercel or Netlify and keep Base44 as the backend?
Yes. Base44 supports being used as a backend service for a frontend hosted elsewhere. Your data and logic stay on Base44, along with its plans and limits.
Can I run the whole Base44 app on Vercel or Netlify?
Not on those services alone. They serve frontends and run time-limited functions, but the backend also needs a database, file storage and a process that stays awake for schedules and live updates. Vercel’s Docker support runs images as stateless functions that scale down when idle. Use a host that keeps a server running, such as Railway or your own Linux server.
Can I host a Base44 app on AWS or Azure?
After migrating, yes: an AWS EC2 or Lightsail instance or an Azure Linux virtual machine counts as a Linux server you reach over SSH, which Unbase44 can deploy to with Docker and automatic HTTPS. Open ports 80 and 443 in the provider’s firewall. A built-in AWS option, including a HIPAA-ready setup, is coming soon.
Which host should I choose after migrating?
Railway if you want the least to manage: the app, MongoDB and file storage live in one account. Your own server (a Hetzner machine you rent works) if you want the lowest monthly cost and don’t mind looking after a machine. AWS, once it arrives, if your organisation already runs there or you need the HIPAA-ready setup.
Do I need to know Docker?
No. On Railway the app deploys from your repository automatically. The Docker setup is there for running on your own server, and for starting the whole app on your laptop when you want to.
Sources
Checked on November 10, 2026. Base44 changes quickly; if something here is out of date, tell us.
- Base44 developer tools (backend service, external frontend)
- Local development
- CLI: eject
- Entities overview (MongoDB-compatible database)
- Base44 pricing
- Managing your app data (backups on Elite and Enterprise)
- Vercel Functions limits (duration by plan)
- Vercel: running Docker on Vercel vs Render (stateless containers, scale-down, no workers or cron)
- Vercel: WebSocket support in Vercel Functions (public beta)
- Netlify Functions configuration (execution limits)
- AWS: connect to a Linux instance with SSH
- AWS: security groups
- Azure: create a Linux virtual machine
- Azure: network security groups
- Railway pricing (Hobby plan)