Every request checked. Every change rehearsed.

Postgres, sign-in, storage, functions and realtime behind one API. Nothing reaches your data until it is identified and allowed, and every change runs on a copy first.

  • TypeScript
  • Python
  • React
  • Next.js
  • Node.js
  • Flutter
  • Swift
  • Kotlin
  • REST
  • CLI

SDKS AND A CLI FOR THE STACK YOU ALREADY USE

Write a row. Watch it arrive. Watch a rule say no.

An order inserted with the SDK reaches every phone that is listening. The same insert from a visitor is refused by the table’s row rule, with Postgres’s own error.

How row rules work Sample data from the recorded Keel Supply build.
orders.ts
201 Created
[{ "number": "SO-1049", "total_cents": 79200, "status": "submitted" }]
403 Forbidden
{ "code": "42501",
  "message": "new row violates row-level security policy for table \"sales_orders\"" }
Row rule · sales_orders
create policy "customer orders" on sales_orders for insert
  with check (customer_email = auth.verified_email()
              and status = 'submitted');
OrdersKeel Supply
  • SO-1048Fernbrook Store$264.00
  • SO-1047North Market$156.00confirmed
  • SO-1046Marrow Kitchen$126.00confirmed
  • SO-1045The Linen House$1,152.00shipped

A visitor’s order was refused by your rules. Nothing changed.

Realtime · INSERT sales_orders

Write a row. Watch it arrive. Watch a rule say no.

An order inserted with the SDK reaches every phone that is listening. The same insert from a visitor is refused by the table’s row rule, with Postgres’s own error.

How row rules work Sample data from the recorded Keel Supply build.
orders.ts
// signed in as ops@junipercafes.com
const { data } = await sovaria
  .from('sales_orders')
  .insert({
    number: 'SO-1049',
    customer_email: 'ops@junipercafes.com',
    lines: [{ product_id: 'KL-101', qty: 3 }],
    total_cents: 79200,
    status: 'submitted',
  })
  .select('number, total_cents, status')
201 Created
[{ "number": "SO-1049", "total_cents": 79200, "status": "submitted" }]
// a visitor with the public anon key
await anon.from('sales_orders').insert({ number: 'SO-1050', … })
403 Forbidden
{ "code": "42501",
  "message": "new row violates row-level security policy for table \"sales_orders\"" }
Row rule · sales_orders
create policy "customer orders" on sales_orders for insert
  with check (customer_email = auth.verified_email()
              and status = 'submitted');
OrdersKeel Supply
  • SO-1049Juniper Cafés$792.00
  • SO-1048Fernbrook Store$264.00
  • SO-1047North Market$156.00confirmed
  • SO-1046Marrow Kitchen$126.00confirmed
  • SO-1045The Linen House$1,152.00shipped

A visitor’s order was refused by your rules. Nothing changed.

Realtime · INSERT sales_orders

Every request is checked before it runs

Ten layers stand between a request and your data, in this order. This is the console’s own view of them, with each layer’s live setting.

  1. 01TLS and HSTSEncrypted, plain HTTP refused
  2. 02FirewallBots, injection and path tricks stopped
  3. 03Allowed originsOnly the websites you list
  4. 04Rate limitsPer IP, per user and per resource
  5. 05App attestationCalls from your real app, not a copy
  6. 06Token checkWho is calling, and is it still valid
  7. 07Access rulesMay this caller do this, here
  8. 08Row-level securityOnly the rows they may see
  9. 09Plan limitsQuotas and spend cap
  10. 10Audit logWritten to a tamper-evident log
See request security in the console
Simulation›Request security
The Request security page: every layer a request to read rows passes, with its setting and status

Every request is checked before it runs

Ten layers stand between a request and your data, in this order. This is the console’s own view of them, with each layer’s live setting.

  1. 01TLS and HSTSEncrypted, plain HTTP refused
  2. 02FirewallBots, injection and path tricks stopped
  3. 03Allowed originsOnly the websites you list
  4. 04Rate limitsPer IP, per user and per resource
  5. 05App attestationCalls from your real app, not a copy
  6. 06Token checkWho is calling, and is it still valid
  7. 07Access rulesMay this caller do this, here
  8. 08Row-level securityOnly the rows they may see
  9. 09Plan limitsQuotas and spend cap
  10. 10Audit logWritten to a tamper-evident log
See request security in the console
Simulation›Request security
The Request security page: every layer a request to read rows passes, with its setting and status

The latest pieces, each shown on the console screen it lives on.

See the changelog

Echo checks a policy or SQL change on a copy, so you see who gains or loses access before it ships. Chrono keeps every version of your schema, rules and functions, and table history lets you query a table as it was at any moment.

See how simulation works
  1. 01Read every change in the plan
  2. 02Apply it once it is reviewed
  3. 03Read the table as it was
EchoReview and apply a plan
Plan deploy-checkoutSimulated · nothing written
  • -ALLOW IF ctx.resource.name == "orders"
    +ALLOW IF ctx.resource.name == "orders"
    + AND ctx.actor.user_id == ctx.resource.owner_id
ChronoRead the table as it was
mainHEAD
SELECT * FROM sov_as_of(NULL::orders, '2026-10-09 15:30');
idtotalstatus
ord_1$48.00paid
ord_2$22.50refunded
ord_4$87.25paid
ord_5$64.00paid
ord_6$129.00pending

5 rows · 3 columns · read-only snapshot of add two orders

EchoReview and apply a plan
Plan deploy-checkoutSimulated · nothing written
  • -ALLOW IF ctx.resource.name == "orders"
    +ALLOW IF ctx.resource.name == "orders"
    + AND ctx.actor.user_id == ctx.resource.owner_id
ChronoRead the table as it was
mainHEAD
SELECT * FROM sov_as_of(NULL::orders, '2026-10-09 15:30');
idtotalstatus
ord_1$48.00paid
ord_2$22.50refunded
ord_4$87.25paid
ord_5$64.00paid
ord_6$129.00pending

5 rows · 3 columns · read-only snapshot of add two orders

Branch the whole backend, not just the database

01Branch the whole system

A branch is a copy of your schema and migrations, functions, policies and settings, with a checkpoint of the data if you want it. Personal columns arrive masked.

productionPriya Murphypriya.murphy@fastmail.com4111 •••• 1042
branchInes Calderuser_7f3a91@masked.example4000 •••• 0000

Same row, same shape, joins still work. The real name, email and card never leave production.

02Every change is a commit you can read

Tables, rules, functions and settings changed on the branch are recorded one by one, with a diff for each, and any of them can be undone.

03Deploy when it is right, rewind if it isn’t

Deploy to staging, then production; every change is checked on a copy first. Snapshots keep a point you can go back to, with the database too.

How branches work
The Branches page
Version history of a branch
Snapshots of a branch

Branch the whole backend, not just the database

01Branch the whole system

A branch is a copy of your schema and migrations, functions, policies and settings, with a checkpoint of the data if you want it. Personal columns arrive masked.

productionPriya Murphypriya.murphy@fastmail.com4111 •••• 1042
branchInes Calderuser_7f3a91@masked.example4000 •••• 0000

Same row, same shape, joins still work. The real name, email and card never leave production.

The Branches page

02Every change is a commit you can read

Tables, rules, functions and settings changed on the branch are recorded one by one, with a diff for each, and any of them can be undone.

Version history of a branch

03Deploy when it is right, rewind if it isn’t

Deploy to staging, then production; every change is checked on a copy first. Snapshots keep a point you can go back to, with the database too.

Snapshots of a branch

Everything a backend needs, already in the project.

33
Products in every project
5
SDKs, plus the sov CLI
12
Engines behind one gateway

Each engine does one job and is reached only through the gateway. Hover an engine to light up everything it connects to.

Read the engine reference
GATEWAYIDENTITYPOLICYDATA & COMPUTEREALTIME · TIME · USAGECONSENSUSGatewayAxisGuardAtlas DocAtlas RelForgeVaultPulseChronoLedgerQuorumEchoNexus
  1. Gateway
  2. Identity
  3. Policy
  4. Data & compute
  5. Realtime · time · usage
  6. Consensus
  7. Alongside

Guard

Policy & authorization

Evaluates SPL policies with default-deny semantics. Nothing executes without an explicit ALLOW.

  • Sovaria Policy Language (SPL)
  • Per-user and per-IP rate limits
  • Storage, API and bandwidth quotas
  • Policy versions and rollback

The sov CLI and five SDKs (TypeScript, Python, Dart, Swift and Kotlin) follow the same rules as the console. Every command and line of output here is real sov CLI output, beside real SDK code.

See the SDKs and the CLI
Terminalsov 0.2.7
$
app.tsnpm install @sovaria/sdk
$ npm install -g @sovaria/cli$ npm install @sovaria/sdk$ pip install sovaria-sdk

What changes when identity, policy, data and simulation live in one place.

SovariaFragmented stack
Identity and policy on every requestOne gateway path: Axis then Guard, default denyAuth service plus per-route middleware you maintain
Preview a change before it shipsEcho: who gains or loses access, checked on a copyStaging environment and hope
Documents and SQL togetherAtlas Doc and Atlas Rel under one policy modelTwo databases, two permission systems
Read data as it wasTable history (sov_as_of) and point-in-time recoveryRestore a backup into a scratch database
Branch your dataTimelines you can spawn, review and convergeCopy tables by hand
Know what happenedAudit trail with hash-chain verificationLogs spread across services
One client for everythingOne SDK, one CLI, one gateway URLA client library per service

Security is part of the request path, not an add-on. These behaviors come from how the gateway, Guard and the SDKs are built.

How Sovaria keeps data safe

Default deny

Guard evaluates every request against compiled SPL policy and denies anything not explicitly allowed.

Verifiable audit trail

Audit entries are append-only and hash-chained. sov audit verify checks the integrity of the chain.

Tenant isolation

Every call carries org, project and environment scope. Tenant allowlists are enforced in Guard.

Short-lived realtime tickets

WebSocket connections use a short-lived ticket, so JWTs are never placed in WebSocket URLs.

Cookie-based browser sessions

The console uses an HttpOnly refresh cookie. SDKs and the CLI use a JSON refresh flow. The two modes are not mixed.

Client-side encryption

Optional zero-knowledge documents: the SDK derives a key with Argon2 and encrypts before data leaves your app.

What teams ask before building on Sovaria

Straight answers about how the platform works, how it keeps data safe and what it costs. For anything else, the docs go deeper.

Browse the docs Compare with Supabase, Firebase, Convex and Neon

Sovaria is a backend platform for web and mobile apps: every project gets a Postgres database, user sign-in, file storage, server functions, realtime, a JSON document store and vector search behind one API, plus Sovariq, an AI engineer that builds and runs the backend with you.

Build on a backend
you can reason about