Projects
Creating a project, its id, reference and URL, region, what each project contains, environments, health and deleting a project.
A project is one backend: its own Postgres database, document store, app users, storage buckets, functions, realtime channels, policies and keys. Projects never share data, users or keys with each other.
Create a project
Organization › Projects › New project
Owners and admins can create projects.
Choose the plan
The organization's plan decides how many projects you may have and their compute — see Plan limits.
Choose a region
Only regions with room for your plan and compute size are listed. Pick the one closest to your users; the region can't be changed later.
Name it
The name can be changed any time in Project Settings › General.
Sovaria creates the database, the anon and service role keys and default settings; the project home shows the project as healthy once they are ready.
Identifiers and URL
| Looks like | Used for | |
|---|---|---|
| Project id | a UUID | The CLI (--project), the management API, support. |
Reference (ref) | 12 hex characters | The project URL. |
| Project URL | https://<ref>.sovarias.in | Everything your app calls: auth, SQL, REST, storage, functions, realtime. Shown under Connect. |
| Database host | db.<org-id>.sovarias.in:5432 | Direct Postgres connections (Database: connection, compute, disk and backups). |
The URL already names the project, so apps never send a project id. Older URLs on <ref>.sovaria.in keep working.
sov orgs # your organizations
sov projects # projects in the current organization
sov link # writes sovaria.config.json for this folderWhat a project contains
| Part | Docs |
|---|---|
| Postgres database and the Table / SQL editors | Database |
| Document store (collections) | Documents |
| App users and sign-in | Authentication overview |
| Storage buckets | Storage |
| Functions, triggers and workflows | Functions |
| Realtime channels | Realtime |
| Access policies | How access is decided |
| API keys and secrets | Keys, tokens and credentials |
| Settings | General settings |
Environments
Every project starts with production. You can add staging and versioned environments that get their own URL and their own copy of rules, functions and schema changes, and promote changes to production when they are ready — Environments, staging and deploying to production. The production environment can't be deleted.
Status and health
- The project home shows the database, its region and compute, and request and error counts.
- On plans with idle pause, an unused database pauses and starts again on the next request (the first request can take a few seconds) — Database: connection, compute, disk and backups.
- Errors carry a
trace_idyou can open in Logs & Audit and give to support.