FAQ

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. The answers below are the short version of the product that exists today.

Common questions

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.

Can I require multi-factor authentication?

Yes, per project. Enable MFA and users can enroll an authenticator app with a TOTP secret. Make it required and sign-in returns a challenge until the user presents a valid code, and Data API requests need an MFA-verified session.

How does CubiBase restrict access to data?

The publishable key only identifies the project. The JWT subject is applied for that transaction. If you name a text user column when you create the table, the API role can only access rows where that column matches the subject. Row Level Security is enabled and forced on tables created in CubiBase. The Console uses a separate SQL role so the project developer can manage rows.

Can I use CubiBase for mobile applications?

Yes. A mobile app calls the project host over HTTPS. Send the publishable key and the user’s JWT. There is no CubiBase mobile SDK in this release. Any client that can make an HTTP request can use the Data API.

Can I manage multiple projects?

Yes. Each project has its own slug, database, and API host. A developer account can own more than one project. CubiBase does not currently publish an API for inviting other developers onto a project.

Do I need to know PostgreSQL?

You need enough SQL and schema design to model your application. CubiBase does not hide PostgreSQL. It gives you a real database, a Console for tables and rows, and REST so your app does not need a handwritten controller for each exposed table.

Does the publishable key return rows by itself?

No. A request without an end-user bearer token is rejected, even when the publishable key is valid. The key answers “which project is this?” The token answers “which user is this?”

Are new tables public on the internet?

No. Creating a table does not expose it. Until you allow select, insert, update, or delete, the Data API treats the table as not found for that operation.

Does CubiBase include file storage, realtime, or edge functions?

Not in the current engine. CubiBase stores relational data in PostgreSQL and serves it over REST. It does not provide object storage, realtime subscriptions, or edge functions.

What does CubiBase cost, and is there an uptime SLA?

Plans are published: Free at $0, Pro at $19 per month, and Business at $79 per month, with project, storage, and user quotas on the pricing page. Self-serve checkout is not live yet, so paid plans are arranged by email for now. No uptime SLA is published on any plan.