PRODSovereign European BaaS platformOpen Dashboard →
ACCUEIL/PRODUITS/DATABASE
DATABASE · NATIVE POSTGRES

Postgres,
without the chores.

A dedicated Postgres database per project, schema-isolated, with native RLS, versioned migrations, and auto-generated TypeScript types. No proprietary abstractions, zero lock-in.

8ms
P99 READ
16
PG VERSION
12
REGIONS
app/api/devices.tsTYPESCRIPT
import { aura } from '@/lib/aurabase'
export async function GET() {
  const { data, error } = await aura
    .from('devices')
    .select('id, name, temperature, last_seen')
    .eq('tenant_id', tenantId)
    .order('last_seen', { ascending: false })
    .limit(50)
  // Server-enforced RLS — tenantId is in the JWT
  return Response.json({ data })
}
#
Feature set

Everything you get from minute one

Schema-per-project

Strict logical isolation: each project gets a dedicated Postgres schema. No shared row-level tenant, no intermediary proxy.

ISOLATION · O(1)

Versioned migrations

Version-controlled SQL, atomic rollbacks, zero-downtime online DDL. TypeScript types regenerate automatically on every migration.

ZERO DOWNTIME

TypeScript codegen

Comprehensive end-to-end types for your tables, views, functions, and relations. Full inference on joins and filters.

TYPESAFE · STRICT

Row-Level Security

Declarative, testable policies. The SDK injects the tenant claim into every request — impossible to bypass from the client side.

RLS · NATIVE PG

Premium extensions

pgvector, PostGIS, pg_cron, TimescaleDB, PGMQ, and pg_partman enabled in one click. Pinned versions, available security audits.

14 EXTENSIONS · GA

Branch previews (roadmap)

One ephemeral database per pull request, cloned seed data, unique preview URL — roadmap feature, coming soon.

ROADMAP
#
Sample schema

One project, four isolated schemas

Each project receives four Postgres sub-schemas: one for your application tables, three for platform primitives, in a dedicated database on your organization's PostgreSQL cluster. Isolation is enforced by PostgreSQL: each project has its own connection role and schema permissions are granted exclusively to it. On the Enterprise plan, a project can also receive a completely dedicated cluster of its own.

SchemaAccessContainsTables
project_{uuid}userYour business tables∞
project_{uuid}_authsystemusers, sessions, oauth_accounts, mfa_factors, refresh_tokens14
project_{uuid}_storagesystembuckets, objects, rls_policies, upload_sessions6
project_{uuid}_platformsystemfunctions, jobs, cron_jobs, api_keys, webhooks9
#
Performance

Measured in production, under real load

8ms
P99 READ
On a select * limit 100 query, measured from eu-west-3
12
REGIONS
EU, US, APAC · cross-region logical replication
#
Honest comparison

Aurabase · Supabase · Firebase

FeatureAurabaseSupabaseFirebase
Schema-per-projectYes · nativeNo · shared schemaNo · collections
Row-Level SecurityPostgres policiesPostgres policiesFirestore rules
TypeScript codegenOn every migrationManual via CLIPartial (Firestore)
pgvector / PostGISGA · includedGA · includedN/A
BillingPer requestPer compute-hourPer document read
EU regions4 · incl. Paris2 · incl. Frankfurt2 · without Paris
Export to PostgresDirect pg_dumpDirect pg_dumpTotal rewrite
#
FAQ

Frequently asked questions

Is this real Postgres, or a proprietary layer?+
It's vanilla PostgreSQL 16, with no fork or query-rewriting proxy. Your extensions, triggers, and PL/pgSQL functions work as-is. A pg_dump gives you your full database back, extensions included, without lock-in.
How does schema-per-project isolation work?+
Each project receives four sub-schemas: project_ (your tables), ..._auth, ..._storage, ..._platform. The gateway injects the search_path into each connection — queries physically cannot cross another project's boundaries.
Can I use my ORMs (Prisma, Drizzle, Kysely)?+
Yes. Aurabase exposes a standard wire-protocol compatible Postgres endpoint on port 5432. Point your ORM using the provided connection string, and everything works — migrations, transactions, and prepared statements included.
What about performance under heavy production loads?+
Each project can scale vertically up to 96 vCPU / 768 GiB RAM with zero redeployment. Cross-region logical replication is available self-serve on Pro and Enterprise plans. For heavy analytical workloads, enable dedicated read replicas.
How do I migrate from Supabase or Firebase?+
From Supabase: aura import --from supabase imports your schema, RLS policies, and storage buckets. From Firebase: our CLI maps Firestore collections to JSONB Postgres tables and rewrites Security Rules into policies. Expect 1-2 hours for an average project.
What is the data residency policy?+
You choose the region at project creation time. Data, backups, and replicas remain strictly in the chosen region. The Enterprise plan allows pinning at the country level. Paris is available starting from the Free plan.
INSTANT START

Your Postgres database in 90 seconds.

No credit card required. Schema provisioned, connection URL provided, types generated. You code instead of configuring.

No credit card required · 500 MB free · 50,000 MAU