Managing Your AI App After Migration
You moved off Base44 or Lovable onto your own Supabase and Staticbot hosting. Here's how to keep shipping — with a full audit trail and a checked preview before every release.
Ravel works on Staticbot’s migration platform, moving apps built with Lovable and Base44 onto Supabase and hosting their owners control.
The migration is done. Your database, edge functions, storage, and auth now live on a Supabase project you own, and your frontend is deployed to your own infrastructure — Cloudflare Workers for full-stack apps, AWS S3 + CloudFront for static sites. The important part: it's all standard now. No proprietary SDK, no managed entity layer, no vendor console you can't leave. That opens up how you build from here on.
Two ways to keep building
You don't have to pick one and stick with it — many teams do both. The point is that owning the stack gives you options the builder never did.
Keep using the AI builder
Keep ideating and previewing in Lovable or Base44. Continuous Sync applies each change to your Supabase, builds a separate Staticbot preview of the frontend, and health-checks it. Approve the checked preview manually or let it promote automatically once it is healthy. Your users see the promoted version on your main domain.
Edit the repo with Claude Code
Because it's a normal repo against a normal Supabase project now, you can open it in Claude Code (or Cursor, or Codex) and change anything — add a table, write an edge function, refactor the frontend. Push to the branch Continuous Sync watches (the one your builder commits to, usually main), and the change goes through the same preview and promotion as a builder edit. Or deploy on your own terms. No builder credit limits, no black-box backend.
Both paths coexist cleanly
Staticbot deploys production from a dedicated staticbot/live branch. Your AI builder's changes are applied onto it, and if you also edit with Claude Code, those commits land the same way. The builder keeps writing to its own branch, untouched — so you can mix a Lovable session and a Claude Code refactor without either side stepping on the other. Merging staticbot/live back into the builder branch is an explicit, opt-in "cut the cord" move — never automatic.
Continuous Sync is your audit trail
Every push produces a sync run — a recorded, inspectable unit of change. Instead of a builder-managed backend where a change just "happens," you get a granular diff of exactly what moved and a deterministic order in which it was applied to the infrastructure you own.
Recorded diffs
Each sync run captures what changed — new SQL migrations, changed edge functions, frontend, storage, and auth — and records the exact source and target revisions for reproducibility.
Review before publishing
Review the preview and its health check before manual approval, or enable automatic promotion of healthy previews. Destructive SQL still pauses for your explicit approval.
Version pinning
Templates are pinned to Git commit SHAs, so every deploy maps back to an exact commit. You can always see — and re-run — the precise state that shipped.
Changes land in a fixed order
A sync run doesn't fire off changes at random. It applies them in a fixed, dependency-safe sequence:
1. SQL migrations first
New files in supabase/migrations/ apply sequentially to your Supabase project — managed or self-hosted — as soon as the sync runs. Destructive statements pause for your review first.
2. Edge functions next
New or changed functions in supabase/functions/ deploy in parallel to your Supabase project.
3. Frontend last, through a preview
The frontend is rebuilt into a preview and health-checked. It goes live on Cloudflare Workers (full-stack apps) or AWS S3 + CloudFront (static sites) when you approve it, or automatically if you turned that on.
Because the backend changes before the new frontend goes live, the version your users are on must keep working against the new schema. Prefer additive changes: add a column before the code that uses it, and remove old columns in a later change. The result is deployments you can reason about: an ordered, logged, reproducible change set landing on infrastructure you own — the opposite of an opaque managed backend where you can't see, audit, or roll back what happened.
Optional: drive it all from your AI agent
None of the above requires an agent integration — the dashboard does everything, and your infrastructure runs whether or not you ever touch a terminal. In a skill-capable coding agent, install the Staticbot skill collection for focused deployment, migration, and Continuous Sync workflows. Connect the Staticbot MCP server for typed, authenticated tools in Codex, Claude Code, Cursor, Windsurf, and other compatible clients. A direct REST fallback remains available when MCP tools are unavailable.
You're never locked in — including to Staticbot. Your Supabase project and your Cloudflare/AWS deployment are standard and keep running on their own. Pause Continuous Sync, disconnect the builder, or manage everything by hand whenever you want. Ownership is the whole point.
Build there. Own it here.
Keep shipping in your AI builder or in Claude Code — and let every change flow to infrastructure you control, with a full audit trail.
