→
+
Your app already matters.
Own where it runs. Choose how you build.
Your users, data, and daily workflows make this more than a hosting change. Start with a test migration to a separate Supabase project and a working preview. Once it passes, plan a maintenance window, take the final copy, verify the result, and reopen on your existing domain. Staticbot handles the supported migration and preview; our live-move guides cover the manual coordination around it. Afterward, keep building in Lovable or Base44: Continuous Sync creates a preview for each change, health-checks it, and promotes after manual approval or automatically once it is healthy. You can also work in the repository with Claude Code, Codex, or Cursor.
FOR APPS PEOPLE ALREADY RELY ON
Start by testing the move
Your app has users, important data, or a place in your daily workflow. Start with a test migration and a working preview. Once you know it works, schedule a short maintenance window and move the live app. Your users keep using the same domain.
0 · Try a test migration
Migrate to a separate target and test the preview while your live app keeps running.
1 · Make the live move
Announce maintenance, stop source writes, take a fresh copy, and verify before switching traffic.
2 · Keep building
Keep using Lovable or Base44 and review updates in Staticbot before they go live. Or work in the repository with Claude Code, Codex, or Cursor.
Staticbot handles the migration and gives you a preview. The guides explain the rest: telling your users, stopping changes to the old database, checking the result, and switching your domain.
The problem with managed AI builders
People depend on your app
Moving means preserving accounts, records, files, and the workflows people use every day. You need a tested plan for all of them.
Pricing scales against you
Managed platforms charge per project, per seat, or per usage tier. As you grow, you pay a premium for infrastructure that could run on your own AWS account at a fraction of the cost.
No infrastructure transparency
You can't audit your database configuration, tune performance, or comply with data residency requirements when the infrastructure is abstracted away.
The production stack
Supabase as your backend, your choice of frontend host (AWS or Cloudflare Workers depending on whether your app is static or SSR), and Staticbot tying it together.
Supabase — your backend
A Supabase project in your own organization gives you a Postgres database, Auth, Storage, and Edge Functions — all fully managed by Supabase, but under your account. Your data stays in a region you choose. You hold the service role key. You control the schema.
AWS S3 + CloudFront — your frontend
For static appsYour compiled frontend (HTML, CSS, JS) is served from S3 and distributed globally via CloudFront. No Node.js servers, no containers, no idle costs. Sub-100ms response times globally, and a bill that scales from nearly zero. Best fit for vanilla Vite / Lovable's classic React-Vite output / static Astro / Bolt SPAs.
Cloudflare Workers — your SSR frontend
For SSR appsModern AI builders are increasingly producing server-rendered apps — Lovable defaulted new projects to TanStack Start SSR in May 2026, and Nuxt, Astro-SSR, and Hono apps need a real runtime, not just static files. Staticbot deploys these to Cloudflare's global edge network via Workers for Platforms. Custom domains via two DNS records, automatic SSL, no Node servers to manage. Read the deployment overview or the technical deep dive.
Current pricing: migrations are free; hosting is $5/mo for two sites or apps, or $15/mo for up to ten, with the first month free for any app you migrate. Bring-your-own Cloudflare account is on the roadmap; today we host SSR apps in a shared Workers for Platforms pool in our Cloudflare account.
Staticbot — the orchestration layer
Staticbot connects your GitHub repo to AWS and orchestrates the migration of your Supabase backend. It handles the infrastructure as code (Terraform), build pipeline, environment variable injection, and the step-by-step migration workflow — all through a dashboard, not a CLI.
What moves, and where it goes
Everything that lives inside your AI builder's managed backend has a destination in the new stack.
Tables, indexes, triggers, functions and RLS policies — restored from the builder's official database export where one exists, otherwise replayed from your repo's SQL migrations
OAuth providers, redirect URLs, JWT settings, email templates
Bucket configuration and file contents transferred to your project
Server-side logic deployed to your project's edge runtime
Static Vite / classic Lovable React / Bolt SPAs — built from your GitHub repo and served from a global CDN
TanStack Start (Lovable's new default), Nuxt SSR, Astro-SSR, Hono — deployed to Cloudflare's edge runtime
Why migrate to owned infrastructure
Full data ownership
Your Postgres database lives in your Supabase organization. You can export, audit, or move it at any time — no dependencies on your builder's account.
Predictable infrastructure costs
AWS + Supabase free tiers cover most early-stage apps. As you scale, you pay directly for what you use — no builder markup on top.
Security and compliance control
Choose your data region, configure RLS policies directly, manage service role keys, and comply with GDPR or other requirements on your own terms.
No lock-in
Staticbot provides the Terraform code that manages your infrastructure. You can inspect it, modify it, or run it yourself — you're never dependent on Staticbot being online.
Supported AI builders
Migration guides available now, with automated tooling being added progressively.
Fully automated migration — Staticbot discovers your source project and migrates DB, edge functions, storage, and auth in a single guided workflow.
Fully automated migration for the most locked-in builder. Native Base44 apps get their entity schemas turned into Postgres tables on a fresh Supabase project, users migrated by email with passwordless sign-in, and the Base44-hosted login page rebuilt in your app. Apps already wired to their own Supabase are auto-detected from the deployed bundle — no copy-paste of platform secrets. Either way: DB, data, edge functions, storage, and auth, moved to infra you own.
Fully automated migration — Staticbot discovers your Bolt project and migrates DB, data, edge functions, storage, and auth in a single guided workflow.
Ready to own your infrastructure?
Connect your GitHub repo, point Staticbot at your source Supabase project, and walk through the migration in a guided dashboard — no devops expertise required.