Tessera DB
PX-01
North Star
Five layers, one binary, one copy of the data.
From the request to the disk: interfaces, a query engine that detects the language, a graph engine, the indexes that make up the five dimensions, and content-addressed, bitemporal storage. Every layer is purpose-built — no wrappers, no adapters.
How it is put together.
Five layers from the request to the disk, all in one binary. Every layer is purpose-built — no wrappers around other databases — and every dimension reads the same record rather than a replica of it.
01
Interface
HTTP/REST · gRPC · PostgreSQL wire · CLI/REPL
Applications, AI agents and BI tools come in over HTTP with an OpenAPI spec compiled into the binary, gRPC, the Postgres wire protocol, JDBC or the REPL.
02
Query
TQL · Cypher → TQL · SQL · GraphRAG
The language is detected at parse time. Cypher is translated to TQL, SQL has its own executor, and EXPLAIN shows the plan and its cost before anything runs.
03
Graph
60+ algorithms · copy-on-write branching · GDS pipeline
Algorithms run against named in-memory projections, and branches are copy-on-write overlays over the same data rather than copies of it.
04
Index
HNSW · BM25 · B-tree · CSR/CSC
Vector, full-text, range and adjacency indexes, built side by side over the same records. The five dimensions are indexes, not copies.
05
Store
Hyperedge · BLAKE3 · bitemporal · LSM-tree · WAL
Each hyperedge is keyed by the BLAKE3 hash of its content and carries valid and transaction time, landing in an LSM-tree behind a write-ahead log, with Arrow IPC and tiered storage.
AutoGuard
Eight defence layers run inside the engine rather than in a gateway in front of it: injection patterns are caught before a query executes, every insert is scored as it arrives, and each security-relevant action is written to a BLAKE3-chained, tamper-evident audit log. Enterprise.
One binary
Written in Rust and shipped as one self-contained executable with no JVM, running on your own hardware with no cloud call-home. The foundational engine is Apache 2.0; Enterprise features unlock on the same binary with a signed licence key.
One hyperedge, five lenses.
Relational
Properties are a typed map on the record (BTreeMap<String, PropertyValue>), which SQL reads as rows and columns.
Graph
Endpoints are the record's list of entity references (Vec<EntityRef>), which Cypher and TQL traverse.
Vector
An embedding is just another property value (PropertyValue::Vector), indexed by HNSW.
Full-text
Text properties (PropertyValue::Text) feed a BM25 inverted index as they are written.
Time-series
Valid-time and transaction-time intervals let any set of facts be read as an ordered series and aggregated in place.
Identity
The record's identity is the BLAKE3 hash of its content, so identical facts collapse into one and lineage has something stable to point at.
The specification.
Data model
Role-typed hyperedges · BLAKE3 content-addressed
Dimensions
Relational · graph · vector · full-text · time-series
Time
Bitemporal · valid time and transaction time
Query
SQL · Cypher (common subset) · TQL, auto-detected
Indexes
HNSW · BM25 · B-tree · CSR/CSC
Transactions
ACID · isolation up to serializable
Storage
LSM-tree · WAL · MVCC · Arrow IPC · tiered
Interfaces
REST/OpenAPI 3.0.3 · gRPC · PostgreSQL wire · JDBC
SDKs
Python · Rust · TypeScript
Security
API keys · RBAC · SSO and AES-256-GCM at rest (Enterprise)
Observability
Prometheus · OpenTelemetry (OTLP)
Topology
Single node · Raft building blocks for multi-node (Enterprise)
Deployment
One self-contained Rust binary · self-hosted · no JVM
Licence
Apache 2.0 core · signed keys for Enterprise tiers