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.
Keys are displayed only once upon creation. They can be regenerated (old invalidated immediately) from the Studio or via Settings › Connection.
8 GA regions · Paris by default
Your project is pinned to its creation region. Data, backups, replicas and CDN caches remain in this region. Changing region involves a migration assisted by our team (contact migrate@aurabase.cloud).
Region codeCityLatency from ParisZone
eu-west-3Bets5msFR
eu-west-1Dublin12msIE
eu-central-1Frankfurt9msDE
us-east-1Virginia85msUS
us-west-2Oregon140msUS
sa-east-1Sao Paulo180msBR
ap-northeast-1Tokyo220msJP
ap-southeast-1Singapore240msSG
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.
RolePermissionsMax
ownerComplete management, invoicing, project deletion1
adminTeam management, policies, deployments — excluding invoicing∞
developerReading/writing tables, functions, migrations∞
viewerRead only on data and logs (no secrets)∞
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.
KeySecurityUsage
anon_keyPUBLISHABLEBundle client, mobile app. RLS applied, claims = anon.
service_role_keySECRETBackend only. RLS bypass. Never board on the customer side.
user_jwtSESSIONGenerated by aura-auth after signin. Expires (15 min), auto rotation.
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