Records — rows, with a columnar projection of the same records — search, vectors, graphs, queues, topics, files, geometry and sealed secrets: eleven engines over one transactional store, in one Rust binary, on its own storage engine.
tessaridb.com · docs · kv.tessaridb.com · s3.tessaridb.com · am.tessaridb.com · oauth.tessaridb.com · vault.tessaridb.com
An AI product usually ends up running a database, a search engine, a vector index, a cache, a queue, an event log and somewhere for files, with no transaction across any of them. TessariDB is one store that does all of those jobs on the same records, under one snapshot, in one language. A table keeps its records as rows and may project the same records into a columnar layout for the scans that read many at once — one authority, two layouts, no copy to reconcile. Not the fastest at any single job; enough at all of them, and nothing to keep in step.
The database. Eleven engines, one transaction, a cluster declared in the catalog itself — realms and what a loss must survive, sharding that rebalances a growing table by itself, failover, replication between clusters — on its own engine, TessariKV. The relational wire protocol serves its tables to the psql, psycopg and BI-tool clients a stack already runs.
Repository · Site ·
Docs · 0.49.1
The heart of TessariDB: an embedded key-value storage engine in pure Rust, lock-free first, with a stable file format. TessariDB runs on it from 0.36.0.
Repository · Site ·
Docs · 0.2.0
S3-compatible object storage in Rust. Metadata in TessariDB, bytes erasure-coded across nodes. Its console signs in through TessariDB OAuth, and the settings its nodes share are kept in TessariDB.
Repository · Site ·
Docs · 0.8.1
Sign-in for your own applications: an OAuth 2.1 authorization server and OpenID provider in Rust, with every piece of its state in TessariDB. Passkeys, passwords with an authenticator app, consent, and an account page where users see and end their sessions and grants, in one binary with its admin panel.
Repository · Site ·
Docs · 0.3.3: existing SSO sessions resume at authorization
Goals, plans, tasks and what each agent remembers, as queryable records. CLI, REST and MCP.
Site · Docs · 0.6.5: Cloud entitlement and secure reproducible images
A password manager for companies. Records are encrypted in the browser and shared by person, team, department or company; the server and TessariDB hold only ciphertext, and every piece of state is in TessariDB.
Repository · Site ·
Docs · 0.0.4: owners linked to OpenID Connect at provisioning
Apache-2.0, all checked against one protocol and conformance corpus:
- Rust:
tessaridb-client0.14.0 - Python:
tessaridb-client0.14.0 - TypeScript:
@tessaridb/client0.14.0 - Go:
github.com/tessaridb/tessaridb-sdk-go0.14.0 - Kotlin:
com.tessaridb:tessaridb-client0.14.0 - S3 SDK and CLI:
tessaridb-s3-client0.2.1, for S3-compatible storage - OAuth client:
tessaridb-oauth-client0.1.0, to check TessariDB OAuth access tokens and sign users in - Agent plugins: for Claude Code and Codex
docker run -d --name tessaridb \
-p 9080:9080 -p 8000:8000 \
-v tessaridb-data:/var/lib/tessaridb \
-e TESSARIDB_INITIAL_USER=owner \
-e TESSARIDB_INITIAL_PASSWORD='choose-a-real-one' \
tessaridb/tessaridbThe console is at http://localhost:8000. Next: the docs.
Production use is free, commercial included (BUSL-1.1, each release converts to Apache-2.0 after four years). Clients, protocol and TessariKV are Apache-2.0. hello@tessaridb.com
© 2026 @boogvar