PostgreSQL backend platform
Build your product. Not your backend.
A PostgreSQL database, user authentication, and REST APIs for every project. One host, one Console, no backend to rewrite.
- PostgreSQL per project
- Auth with MFA
- REST for exposed tables
customers
| name | plan | |
|---|---|---|
| Mina Cho | [email protected] | pro |
| Jonah Hale | [email protected] | starter |
| Priya Shah | [email protected] | pro |
| Northwind Supply | [email protected] | team |
GEThttps://example-project.api.cubibase.com/rest/v1/customers
The platform
The backend essentials, already wired together.
You still design the schema. CubiBase handles the parts every app rebuilds.
01
A PostgreSQL database per project
Name a project. CubiBase provisions a database for it alone, with four roles that cannot bypass row security.
example-projectProvisioningDatabaseexample_project_db
Rolesddl · api · sql · auth
Schemaspublic · auth · vault · logs
Illustration of the state change. Creating a project queues the database; it exists when provisioning finishes. 02
Sign-up and sign-in for your users
Call /auth/v1 on the project host. Users, sessions, and TOTP MFA live in your database. The access token is the JWT your data calls need.
Your app
email + password
CubiBase Auth
Argon2id hash
Your database
example_project_db
Illustration. Sign-up returns the JWT your Data API calls use. 03
Exposed tables become REST
A new table is not public. Switch on select, insert, update, or delete, and the Data API serves it. No controller to write.
customers · exposureillustrationServed at
/rest/v1/customersfor the operations you switched on.Illustration. Toggles here do not change any real table.
Authentication
Your users sign in. You skip the auth server.
Email and password, rotating refresh sessions, and TOTP multi-factor, served from your project host. Passwords are Argon2id hashes in your own database.
- Access JWTs that row policies already understand.
- Stolen refresh token reuse revokes the whole family.
- Bring your own IdP with RS256 and a JWKS URL instead.
Email and password return an access JWT and a refresh token.
accessToken · 1 h
A new pair is issued and the old refresh token is retired.
refreshToken · rotates
A retired token presented again revokes the whole family.
family revoked
Logout or a Console revoke fails the session on the next request.
session_revoked
REST
Your tables. Your APIs. Automatically.
Expose customers and the Data API serves https://example-project.api.cubibase.com/rest/v1/customers.
GET https://example-project.api.cubibase.com/rest/v1/customers?plan=eq.pro&order=name.asc&limit=20
apikey: cb_pub_EXAMPLE_ONLY
Authorization: Bearer <USER_JWT>{
"data": [
{
"id": "8c1a0b2e-7d44-4a11-9c31-0b51a6e4d901",
"name": "Mina Cho",
"email": "[email protected]",
"plan": "pro",
"owner_id": "user_mina"
},
{
"id": "44ab91c3-0e55-4d72-b018-6f2c8a91bb70",
"name": "Priya Shah",
"email": "[email protected]",
"plan": "pro",
"owner_id": "user_priya"
}
]
}A call with a valid key and no bearer token fails with missing_end_user_token. See the REST API
{
"error": {
"code": "missing_end_user_token",
"message": "An end-user bearer token is required",
"requestId": "req_example"
}
}Console
See your data. Shape your database.
Tables, rows, filters, and one read-only SQL statement. Try the filter below.
| name | plan | owner_id | |
|---|---|---|---|
| Mina Cho | [email protected] | pro | user_mina |
| Jonah Hale | [email protected] | starter | user_jonah |
| Priya Shah | [email protected] | pro | user_priya |
| Northwind Supply | [email protected] | team | user_northwind |
SELECT name, plan
FROM customers
WHERE plan = 'pro'
ORDER BY nameAuthorization
Four checks on every request.
Each one names a different thing. None of them repairs a user column you forgot to set.
- 1
Separate database
The host is one project. Another slug is another database.
- 2
Publishable key
The apikey header must match an active cb_pub_ key for that project.
- 3
End-user JWT
From CubiBase Auth or your own IdP. The subject becomes the user id, and the session must be live.
- 4
Row policy
The API role has NOBYPASSRLS. A user column policy keeps it to matching rows.
How CubiBase works
- 01
Create your project
Verify your email, pick a slug, and wait for provisioning. The slug is the API host.
- 02
Define tables and users
Add tables in the Console. Sign up a first user through /auth/v1/signup.
- 03
Connect your app
Call
https://{slug}.api.cubibase.com/rest/v1/{table}with the publishable key and the user’s JWT.
Use
One backend platform. Many ways to build.
- MobileA client that speaks HTTP
Sign users in and sync tasks over HTTPS. No mobile SDK required.
- SaaSOne product database
Accounts and the records they own in one project, rows limited by user.
- AgenciesOne project per client app
Each engagement gets its own database and host, under one account.
- Internal toolsA database your team can open
Inspect rows in the Console without shipping an admin panel first.
Developer experience
The request your application sends.
Filter with column=op.value. Sort with name.asc. A list comes back as { "data": [] }.
GET https://example-project.api.cubibase.com/rest/v1/customers/8c1a0b2e-7d44-4a11-9c31-0b51a6e4d901
apikey: cb_pub_EXAMPLE_ONLY
Authorization: Bearer <USER_JWT>{
"data": {
"id": "8c1a0b2e-7d44-4a11-9c31-0b51a6e4d901",
"name": "Mina Cho",
"email": "[email protected]",
"plan": "pro"
}
}Pricing
Start free. Upgrade when the product grows.
Free, Pro, and Business plans are published with project, storage, and user quotas. Every plan includes the database, auth, REST, and the Console.
Questions developers ask first
What is CubiBase?
CubiBase is a PostgreSQL backend platform. You create a project, CubiBase provisions a database for that project, and your application calls the project’s REST API and auth endpoints. The Console is where you manage tables, rows, API keys, and a read-only SQL statement.
How does CubiBase differ from building a REST API manually?
A handwritten API needs a database, controllers, and an authorization check for every table. In CubiBase you create the table, choose which operations to expose, and call https://{slug}.api.cubibase.com/rest/v1/{table}. You still design the schema and decide which column identifies the end user.
Does each project get its own PostgreSQL database?
Yes. Creating a project stores the project and queues provisioning. When provisioning finishes, that project has its own database. Developer accounts live in a separate metadata database, cubibase_meta. Projects do not share a project database.
How are REST APIs generated?
The Data API serves any exposed table at /rest/v1/{table}. A new table is not exposed. You turn on select, insert, update, or delete for that table. The request must send the project’s publishable key and an end-user JWT. List results come back as JSON in a data array.
Can I run SQL queries?
Yes, from the Console. The SQL editor accepts one read-only statement, such as SELECT, and runs it in a read-only transaction on the project’s SQL role. Schema changes go through the table API, not through that editor. Results are capped.
Does CubiBase include authentication for my app’s users?
Yes. Every project has CubiBase Auth on the project host: /auth/v1/signup, sign-in and refresh at /auth/v1/token, logout, and TOTP multi-factor. Users live in the auth schema of your project database, passwords are hashed with Argon2id, and sessions use short-lived access JWTs with rotating refresh tokens. You can also verify RS256 tokens from your own identity provider via a JWKS URL.
How does authentication work?
Two different people authenticate. You sign in to the Console as a developer. Your application’s users either sign up through CubiBase Auth or sign in with your own identity provider. Either way each Data API request carries a JWT: HS256 signed with the project’s secret, or RS256 checked against a JWKS URL you configure. The verified subject becomes the user id for row policies.
Does CubiBase send verification emails to my end users?
Not yet. By default, signup marks the email verified immediately (autoconfirm). If you turn autoconfirm off, new users start unverified and you mark them verified through the control API. Console emails for developer accounts, such as verification and password reset, are a separate flow that does send email.
Your next application starts here.
Spend more time building what makes your product different.
GET /rest/v1/customersapikey: cb_pub_…Authorization: Bearer <JWT>200 · { "data": [ … ] }