One Platform.
Many Workloads.
Transactions, columnar analytics and, on the roadmap, time series, vectors and search, all behind one plan language and one verifier. Every table is scoped to a tenant by its key range, never by a filter someone remembered to write.
A query plan, as the verifier sees it
- n1SCAN contacts
- n2TENANT_ISOLATE your workspaceTenant isolated
- n3ACL_FILTER team = 'sales'Access policy applied
- n4FIELD_MASK emailEmail hidden
- n5FILTER status = 'active'
- n6TOPK 20 by created_at desc, id
- n7PROJECT id, name
- n8RESULTEvery rule met
AcceptedEvery row this plan returns belongs to your tenant and passed your access policy.
This is the CRM example from the IR specification and its real verdict from the test suite.
Engines behind one verifier
Each engine is proven by a public benchmark against a named leader before it ships. Built engines today: row and columnar.
Transactional (row)
Snapshot isolation, first-committer-wins, idempotent writes with client keys, a durable GC horizon. SQL INSERT rejects duplicate keys with 23505.
BuiltColumnar collections
Append-only row groups (≤4 096 rows) with a header zone map, dictionary and bit-packed chunks, created with WITH (storage = columnar).
BuiltAnalytics
Vectorised executor with typed columns and batch aggregation; five TPC-H queries equal DuckDB's answers at SF 0.1.
BuiltTime series
Columnar collections carry telemetry today; a dedicated engine measured on TSBS is planned.
PlannedVector and search
Filtered vector search, text search and graph traversal are specified as plan operators with per-tenant index partitions.
PlannedManaged service
Hosted databases open to early-access teams after multi-node replication, backups and point-in-time restore.
PlannedIsolation that is checked, not configured
The verifier accepts a plan only if every collection it reads is isolated to the requester's tenant, filtered by policy, and masked above the requester's clearance. The optimizer, cache and gateway are untrusted plan authors.
Verified per query
Every data node checks every plan before executing a single operator, whoever produced it.
Identity from the token
RS256 tokens verified at the gateway and again at the node; tenant and clearance come only from verified claims.
Hidden tenant column
SQL tables carry a tenant key you can neither read nor write; primary keys are unique per tenant.
994,405 checks
Paired databases that differ only in hidden rows must give identical answers. No failures in the 10⁷ campaign.
What this does not yet cover: row-level policies (tenant isolation is the boundary today), index probes, and timing or resource side channels, which are listed in a declared-leakage register. Details in the security model.
PostgreSQL on the outside
psql and PostgreSQL drivers connect today with a token as the password, over the simple protocol or prepared statements. A first SQL subset runs; everything else fails fast with SQLSTATE 0A000 and names the missing feature.
Works today
CREATE TABLE, INSERT, UPDATE and DELETE, SELECT with WHERE, inner and left joins, GROUP BY, count/sum/avg/min/max, ORDER BY, LIMIT, OFFSET. Simple protocol and prepared statements with $1 parameters; key lookups seek.
BuiltNext
Transactions, RETURNING, ON CONFLICT, subqueries and DISTINCT, the pg_catalog tables ORMs read, parallel reads at a snapshot.
In progressTypes
smallint, int, bigint, real, double precision, numeric(p,s), text, boolean, uuid, date, timestamp, bytea. No silent lossy conversion.
BuiltSee exactly what runs today.
The status page lists each phase, its gate, and the measurement behind it.