Keep your Lovable app. Give it a backend with a flat bill and an exit.
Keep the client code Lovable wrote. Scribase speaks the same API.
Lovable generates React apps that talk to their backend through a standard JavaScript client. That client only needs a URL and an anon key, and Scribase answers on the same /auth/v1, /rest/v1, /storage/v1, /realtime/v1, and /functions/v1 paths. So the code Lovable wrote keeps working; what changes is the bill, the ability to preview every change on its own branch, and a one-command export when the app outgrows its first home.
What you need
- Run the app Lovable generated without rewriting its data layer
- Stop a prototype from turning into an unpredictable monthly bill
- A safe place to test schema changes before users see them
VITE_SUPABASE_URL=<environment URL from the environment page>
VITE_SUPABASE_ANON_KEY=<anon key from the environment page>How Scribase fits
Same client, new URL
Sync the Lovable project to GitHub, then set the backend URL and anon key variables your project uses to your Scribase environment. This is a code-level switch, not a toggle in Lovable.
Bring the data with you
If the app already has users on a hosted Postgres project, scribase import moves schema, data, RLS policies, storage, and auth users with their password hashes, so nobody resets a password.
Flat price, hard caps
A generated app can be chatty. Scribase has no per-request or per-egress lines: each project has hard caps at a flat price per project, and a signed usage webhook fires at 80 percent of a cap before anything is cut off.
The capabilities behind it
Every claim above maps to a feature Scribase ships. Here are the ones this fit leans on most.
Common questions
Do I have to change code Lovable generated?
Usually no. The client calls stay the same; you change the project URL and anon key. Edge functions Lovable created run on Scribase functions, which use the same Deno runtime and /functions/v1 path.
Can I keep editing in Lovable after switching?
Yes, as long as the environment variables in the synced repository point at Scribase. Lovable’s built-in backend panel will not manage the Scribase project, so run migrations with the Scribase CLI or console instead.