Product

A PostgreSQL backend with auth, a Console, and a Data API.

One project is one database. The Console manages it through the control API; your application calls the project host for users and rows.

Two doors into the same project

Developer

Console

tables · rows · SQL · keys

Control plane

Control API

projects · schema · auth settings

Application

Your app

apikey + user JWT

example-project.api.cubibase.com

Data API + Auth

/rest/v1 · /auth/v1

One project

example_project_db

public · auth · logs

Illustration. The Console manages the project; your app calls the project host.

Console

Accounts, projects, tables, rows, API keys, and one read-only SQL statement. The Console calls the control API. You do not point your mobile app at it.

Project database

example_project_db stands in for the database provisioning creates. Your tables live in public; users and sessions in auth. Developer accounts stay in cubibase_meta.

Project host

https://example-project.api.cubibase.com serves /rest/v1 for exposed tables and /auth/v1 for sign-up, sign-in, and sessions. The publishable key travels with every call.

What you stop rewriting

Handwritten backend compared with CubiBase
JobIn a handwritten backendIn CubiBase
Create a databaseYou provision it and keep the credentials.Creating a project queues a dedicated PostgreSQL database.
Sign up your usersYou build an auth server and a session store.CubiBase Auth serves /auth/v1 with rotating refresh sessions and TOTP MFA.
Expose a tableYou write a controller and a query.You set select, insert, update, and delete. The Data API serves /rest/v1/{table}.
Limit rowsYou add a filter in every handler.A text user column binds the API role to cubibase.current_user_id().

Users

Accounts live where the data lives.

auth.users is a table in your project database. Inspect it from the Console SQL editor, manage it through the control API, and let your app sign people up over HTTPS.

auth.usersexample-project
Fictional end users in the auth schema
emailverifiedmfalast sign-in
[email protected]yestotp2 minutes ago
[email protected]yes—1 hour ago
[email protected]no—Never
Illustration. Users live in your project database, not a shared directory.

What the engine does today

CubiBase stores relational data in PostgreSQL, serves exposed tables over REST, and authenticates your users with email and password, rotating sessions, and TOTP MFA. It also verifies RS256 tokens from an identity provider you configure. End-user confirmation emails, social login, and SAML are not part of the current engine.

Object storage, realtime subscriptions, edge functions, and a mobile SDK are not included, and no uptime SLA is published. Those absences are the scope, not a roadmap promise.

Browse the features or follow the getting started guide.

Create the project first.

The database is provisioned after the project exists, not before.

first request
GET /rest/v1/customersapikey: cb_pub_…Authorization: Bearer <JWT>200 · { "data": [ … ] }