Build your backend. Keep control.

QB Flex gives your application a PGlite database, an authorized REST API, authentication, realtime events and object storage. Studio manages these services; your application connects through a publishable key and its own user sessions.

Start here

1. Follow installation.
2. Create your first project and an ownership policy.
3. Choose the React tutorial or Vanilla JavaScript tutorial.

Three applications, one platform

Studio is the authenticated workspace for project developers. API owns management and application endpoints. Docs is this independently deployable documentation site. A background worker requests scheduled maintenance through an authenticated internal endpoint.

An organization owns projects. Each project owns an isolated primary branch. A branch has a separate PGlite directory and authentication realm. Organization roles and application user identities are different permissions.

What is available

The implementation covers ordinary-table REST CRUD, application policies, password auth with browser passkey/TOTP adapters, row subscriptions, S3-compatible storage and encrypted backup/restore. Read what changed, the expanded-release status and compatibility before deployment. Experimental foundations are not complete delivery/native/WASM services.

GraphQL, vector search, functions, hosted MCP, general branching and replicas are roadmap capabilities. They are not required to use the core backend.

Secure by default

A publishable key identifies a project. It does not grant access to rows. Tables remain private until exposed, and exposed tables still need applicable permissive policies. Platform credentials never become application user sessions.