Generated front end, real backend, no surprise bill.
Postgres, auth, and storage behind the client API those tools already write.
AI app builders are fast at the front end and write standard backend client code. Scribase serves that API, with a flat price per project and a backend you can take with you.
What you need
- Keep the generated client code as is
- Know the monthly cost before launch day
- Move the whole backend later without a rewrite
import { createClient } from '@supabase/supabase-js';
export const client = createClient(
process.env.NEXT_PUBLIC_SCRIBASE_URL!, // your Scribase URL
process.env.NEXT_PUBLIC_SCRIBASE_ANON_KEY!,
);How Scribase fits
Drop-in for the generated client
Export the project from Bolt or v0 and set the URL and anon key environment variables to your Scribase environment. Auth, queries, storage uploads, and realtime subscriptions use the same paths.
Caps instead of meters
Plans have hard caps on database size, storage, and egress, and a project cap can also limit rows and function invocations. A signed webhook fires at 80 percent and at the cap, so a viral day does not become an invoice.
Export is a command
scribase export writes schema, data, storage, and policies as a bundle that boots on your own machine or another cloud.
The capabilities behind it
Every claim above maps to a feature Scribase ships. Here are the ones this fit leans on most.
Common questions
Does Bolt or v0 have a Scribase integration?
Not a native one. Because Scribase serves the same client API, you switch by setting environment variables in the exported project rather than through the builder’s integration panel.
What if my generated app has edge functions?
Scribase functions run Deno under the same /functions/v1 path, so most generated functions deploy unchanged with scribase functions deploy.