Project management
Everything surrounding an Aurabase project: creation, regions, team, roles, API keys, monitoring, invoicing. A project = a dedicated Postgres database on your organization's cluster + a complete namespace.
One project, one complete namespace#
An Aurabase project provisions: a dedicated PostgreSQL database with four sub-schemas (hosted on your organization's CNPG cluster, or on a cluster entirely dedicated to the project on the enterprise offer), a pair of API keys (anon + service_role), a UUID identifier which serves as a prefix to all its routes (/v1/<service>/{project_id} — there is no domain per project), a default storage bucket, a scope for edge functions and a budget.
Billing is per consumption on the Pro plan, flat rate on Enterprise. A project can be paused (resources remain allocated, not billed) or deleted (data deleted within 30 days).
Create a project#
From the console (console.aurabase.cloud): a name and a database engine. The region is the one your deployment declares for its database cluster — the only one available, shown in the form — and the plan is your organization's. Provisioning takes 45 seconds to 1.5 minutes (measured: about 45 s when the organization's cluster is created, about 90 s with the CLI, which waits for the project to be active) — base created on your organization's PostgreSQL cluster (or dedicated cluster provisioned on the fly on the enterprise offer), schemas initialized, keys generated, TypeScript types pre-generated. When you delete the last project of an organization, its cluster is deleted immediately; the next project creates a new one.
# CLI alternative (non-interactive)
aura projects create my-saas --org <org-slug>
# API keys of the project (linked in aurabase.toml, or --project-id)
aura projects api-keys --project-id <project-uuid>
Keys are displayed only once upon creation. They can be regenerated (old invalidated immediately) from the Studio or via Settings › Connection.
EU regions · Paris by default#
Your project is pinned to its creation region. Data, backups and replicas remain in this region, inside the European Union. Changing region involves a migration assisted by our team (contact migrate@aurabase.cloud).
fr-par— Paris · Scaleway (FR)de-fsn— Falkenstein and Nuremberg · Hetzner (DE)fi-hel— Helsinki · Hetzner (FI)
Enterprise only: pinning at country level, contractual commitment. No third-party certification (SecNumCloud FR, C5 DE) is yet committed — public roadmap on our Trust Center.
Four default roles, custom RBAC available#
Each project has a unique owner (the default creator, transferable). Beyond that, you invite members with a predefined role or a custom role defined via policy.
| Role | Permissions | Max per project |
|---|---|---|
owner | Full management, invoicing, project deletion | 1 |
admin | Team management, policies, deployments; no invoicing | Unlimited |
developer | Read and write tables, functions and migrations | Unlimited |
viewer | Read-only access to data and logs; no secrets | Unlimited |
A viewer never sees the secrets or values of service_role_key. Audit logs record each access to sensitive resources for 30 days (2 years on Enterprise).
Anon, service_role, JWT custom#
Three types of keys. Use the right one for the right surface.
| Key | Visibility | Use |
|---|---|---|
anon_key | Public | Client bundles and mobile apps. RLS applies and the claims are anon. |
service_role_key | Secret | Backend only. Bypasses RLS. Never ship it in client code. |
user_jwt | Session | Issued by aura-auth after sign-in. Expires after 15 minutes and rotates automatically. |
Live metrics + quotas#
The Studio exposes real-time metrics on each service: requests/sec, p50/p99 latency, active connections, error rate, storage usage/egress. Export to Datadog, Grafana Cloud, Honeycomb via webhook or Prometheus endpoint.
- DB REQ/S: 1 240 (average 5 min)
- P99 READ: 8ms (select last 100)
- STORAGE: 4.2 GB (100 GB · Pro plan)
- EDGE INV: 48k (this month · 5M quota)