→
+
Initial migration: from AI Builder
to infrastructure you own
Lovable, Base44, and Bolt.new are great for shipping fast — but they run your backend on infrastructure you don't own. The initial migration moves everything — database, auth, storage, edge functions — to Supabase and your choice of frontend host: AWS (S3 + CloudFront) for static apps, or Cloudflare Workers for SSR apps (TanStack Start, Nuxt SSR, etc.). After that, continuous sync keeps your own infra in lockstep with every change you ship from the builder. You keep building where you are — you own where it runs.
The problem with managed AI builders
You don't own the data
Your database lives inside the AI builder's Supabase organization. If you leave, your data goes with the relationship — not always with you.
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.
Pricing: $15/mo per app, first month free with any migration credit. 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.
Full Postgres dump — tables, indexes, triggers, functions, RLS policies
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 — Staticbot discovers your Base44 project and migrates DB, data, edge functions, storage, and auth. Auto-detects your Supabase project from the deployed app for builders whose secrets live on the platform, not in the repo.
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.