One backend, framed for the team using it
The same Postgres backend — auth, storage, realtime, functions, branching, and export — mapped to what each kind of team needs from it.
Scribase for SaaS teams
Multi-tenant Postgres, auth, and storage behind one flat price.
Scribase for SaaS: multi-tenant Postgres with row-level security, preview environments per pull request, and a flat price instead of a metered bill that grows with every signup.
See Scribase for saas teamsScribase for AI apps
CLI and OpenAPI parity, idempotent mutations, and pgvector-ready Postgres.
Scribase for AI apps: real Postgres for embeddings and app data, plus an agent-native control surface where every mutation has a CLI flag, an OpenAPI operation, an idempotency key, and an approval gate.
See Scribase for ai app buildersScribase for mobile apps
Auth, storage, and realtime from one backend and one SDK.
Scribase for mobile: auth, file storage, and realtime on real Postgres, with the client SDK you already know on the device, relational data, and a flat price per project.
See Scribase for mobile teamsScribase for internal tools
A REST API over your schema, auth, and RLS — exportable when a project graduates.
Scribase for internal tools: an instant REST API over your Postgres schema, built-in auth, and row-level security for who-sees-what — plus a full-stack export so an internal tool can graduate to its own stack without a rewrite.
See Scribase for internal tools teamsA backend for Lovable apps
Keep the client code Lovable wrote. Scribase speaks the same API.
Lovable apps are generated against a standard Postgres backend client. Scribase serves the same Auth, REST, Storage, Realtime, and Functions API, so a Lovable app runs on Scribase by changing two environment variables, with flat pricing and a full export.
See Scribase for lovable buildersA backend your coding agent can operate: Scribase for Cursor
MCP over stdio or HTTP, preview branches, and policy tests before merge.
Scribase gives Cursor, Claude Code, and other MCP clients a typed backend surface: create a preview branch, apply a migration, run the Aegis policy test, then merge with approval. Postgres, auth, and storage work with the client SDK your agent already writes.
See Scribase for cursor and claude code usersA backend for Bolt and v0 apps that you can keep
Postgres, auth, and storage behind the client API those tools already write.
Bolt and v0 generate apps that use a standard JavaScript client for data and auth. Scribase serves the same API, so the generated code runs on it with a new URL and key, on a flat plan with hard caps and a full export.
See Scribase for bolt and v0 buildersScribase for Expo and React Native apps
Your client SDK in React Native, Apple and Google sign-in, Postgres underneath.
Scribase for Expo: use the JavaScript client with AsyncStorage or SecureStore for sessions, Apple and Google sign-in through the PKCE OAuth flow, storage for user uploads, and realtime, on Postgres with row-level security and flat pricing.
See Scribase for expo and react native teams