Getting started
Projects
A Project is one isolated RustaBase backend for one application. It has its own database, users, files, runtime, address, and history.
What a Project contains
| Area | What you get |
|---|---|
Database | PostgreSQL tables, relations, indexes, SQL console, row-level security, realtime |
Authentication | Auth tables, email and password, OAuth, one-time codes, MFA, sessions |
Storage | Files attached to records, thumbnails, protected file tokens |
Runtime | Edge functions, scheduled jobs, webhooks, API keys |
Operations | Logs, observability, backups, import and export, security settings |
Project status
| Status | Meaning |
|---|---|
Provisioning | RustaBase is creating the database, runtime, address, and certificate. |
Ready | The API and console passed health and sign-in checks. |
Checking | The console is confirming live status. Nothing is changed. |
Failed | A step did not finish. The reason is in the event log and you can retry. |
Deleting | Managed resources are being removed after your confirmation. |
Addresses
Each Project gets its own address on rustabase.net. That one address serves the REST API, realtime, files, and the Project console. Paid plans can add a custom domain.
RustaBase never shows server addresses, machine names, or database hosts to you or your users. Everything goes through the Project address.
Regions
Regions come from the live capacity RustaBase runs today, for example in Europe, the United States, and Asia Pacific. Each plan lists the regions it can use, and full regions are hidden so new Projects never land on an overloaded server.
Your Project's backend and its database always stay in the same region, which keeps requests fast.
Changing plans
Upgrade your Project's resources to a paid plan at any time from the console. Your Project keeps its address, data, and settings, and stays in the same region.
- Open your workspace billing and choose a paid plan.
- RustaBase upgrades your Project's resources to the paid plan.
- Keep building. Your Project's address and API keys stay the same.
Upgrades are handled for you. There is nothing to reconfigure in your application.
Isolation and access
- Every Project has its own database credentials and encryption keys.
- Credentials are encrypted before they are stored.
- Only members of the workspace with the right role can open or change a Project.
- Your application's users are separate from workspace members and live in the Project's auth tables.
Fix it yourself. The link below opens this file in GitHub's editor and forks the repository for you if you need one, and your change becomes a pull request without leaving the browser.