Product
One secure engine, many form factors
AthenaDB is one engine, built from the ground up — delivered as an embeddable library on your device, a networked server, a clustered service, and a scriptable CLI. Same data, same powerful search, whichever shape you need.
AthenaDB Core
The secure engine everything is built on.
The heart of AthenaDB: an encrypted storage engine with a write-ahead log, B-tree indexes, snapshots, and backup/restore — with its own built-in cryptography. No third-party database or crypto library is bundled inside.
- Encryption at rest (own AEAD: ChaCha20-Poly1305, HMAC, SHA-256)
- WAL, B-tree, snapshots, integrity checks, backup/restore
- C ABI for embedding into applications
AthenaDB Lite
The engine embedded — an encrypted, offline-first local database.
AthenaDB with no server: an encrypted local vault with typed domain stores and the full hybrid-retrieval stack (keyword, vector, HNSW/IVF, timeline, entity). Built for desktop and edge.
- Offline-first encrypted local vault
- Keyword + vector (HNSW/IVF) + timeline + entity retrieval
- On-box embedding generation and re-embedding
AthenaDB Server
Multi-user server runtime with an admin API.
A networked instance serving multiple clients. Listeners, local IPC, and TLS/HTTP/2 transport pieces exist in Early Access; the full multi-user admin surface continues to land.
- TCP default port 1440, TLS, and local IPC paths
- Standalone daemon and service managers in progress
- Admin API — expanding
AthenaDB CSP Edition
Custom edition for cloud service provider infrastructure.
For CSPs who host AthenaDB on their own footprint with complete operational control: offer managed instances, databases, and AthenaDB Data Edge distribution, scaled to your capacity, with geo-residency controls and an extensive API integration service for seamless provider automation. Early Access — inquire on the product page.
- Managed Instance, Managed Database, and AthenaDB Data Edge modes
- Full operational control on your infrastructure
- Geo-residency policies for approved storage locations
- Extensive API integration service for provider control-plane automation
AthenaDB Cluster
Multi-node scale-out with high availability.
DAG execution, replication, sharding, failover, and multi-region placement. Planned — the licensing model already reserves cluster entitlements so editions won't need rework.
- Replication + sharding + failover
- Sentinel high-availability
- Multi-region placement
AthenaDB Sync
Keep working offline. Reconcile when connectivity returns.
AthenaDB Sync is the planned two-way replication model for enrolled Lite and Server replicas. Each replica can continue using its local database offline, then exchange and reconcile changes after reconnecting. Existing object-level oplog and changeset foundations remain in progress; scoped replication and AthenaDB Convergent Record Versioning are Planned / Early Access designs, not GA capabilities.
- Continued local use while offline; two-way reconciliation after reconnect
- Whole or explicitly scoped replication — Planned / Early Access
- Convergent Record Versioning — Planned / Early Access
- Cryptographic identity for every enrolled replica
AthenaDB CLI
A scriptable command line for the whole engine.
The `athenadb` CLI manages instances, ingestion, retrieval, licensing, the Trust Fabric, the SQL surface, and each domain pack — from one binary.
- `athenadb db` — init, status, check, backup, restore, compact, stats, repair
- `athenadb db trust` / `license`, `athenadb sql`, `athenadb import` / `ingest`
- `athenadb legal | medical | research` domain commands
SQLite drop-in compatibility
Migrate existing SQLite apps onto AthenaDB.
A native SQL parser/executor plus a SQLite-compatible C API and an `athenadb-sqlite3` drop-in CLI. Compatibility phases are in the engine; treat this as an Early Access migration path while GA evidence completes — not a certified drop-in for every app yet.
- SQLite-compatible C API + platform-native shim
- `athenadb-sqlite3` compatibility CLI
- A migration path off SQLite, not a rewrite
Programmability
Server-side logic — the way a secure database should do it.
Domain packs provide signed, permissioned server-side logic. Views, pure scalar UDFs, declarative event hooks, and materialized-view markers are in Early Access in the engine; pack-EXECUTE ergonomics and full GA evidence continue.
- Domain packs — signed, permissioned server-side logic
- Saved views and pure reusable functions — Early Access
- Declarative event hooks instead of arbitrary triggers — Early Access
Embedding engine
Pluggable embeddings for vector and hybrid retrieval.
A provider abstraction over external embedding services (Text-Embeddings-Inference / BGE-M3) and native Athena embeddings, with vector indexes, quantization, and re-embedding pipelines — available for Early Access evaluation while platform parity evidence completes.
- Provider abstraction (TEI / Athena-Emb1)
- HNSW + IVF vector indexes, quantization
- Re-embedding pipelines
Native AI runtime
Attach a language model to your database — encrypted, in place.
A planned AI runtime built into AthenaDB rather than bolted on: models load from encrypted, signed packages into protected memory and run inside the database's own security boundary, so your documents and context never leave it. Run it in the database process, on a dedicated model machine you own, or point it at an outside provider when you choose to.
- Encrypted, signed model packages — keys custodied like your data
- Runs in place: prompts and context stay inside your boundary
- Or run the AI tier on its own machine over an encrypted link
Instance Trust Fabric
A secure cognitive trust mesh between database instances.
Instances authenticate each other with cryptographic identity, negotiate scoped roles, and exchange permission-filtered context — never raw remote SQL. Foundations ship in Early Access; full fabric GA evidence remains in progress.
- Cryptographic instance identity (Ed25519)
- Directional, revocable, non-transitive trust policy
- Permission-filtered context packs, mTLS channels, dual-side audit
AthenaDB Secure Data Tunnel
Let the database fetch and exchange data for your app.
A planned application exchange path where AthenaDB securely fetches and moves data on behalf of your app. Short-lived tunnel keys are designed to rotate regularly across Lite, Server, and CSP deployments. This is request-driven app exchange, distinct from AthenaDB Sync's planned ongoing replica reconciliation.
- Planned database-mediated secure fetch, push, and exchange
- Short-lived rotating tunnel keys by design
- Planned across Lite, Server, and CSP deployments
AthenaDB Studio
Multi-engine desktop admin — SSMS-class AthenaDB, plus SQL Server, PostgreSQL, MySQL, and MariaDB.
Cross-platform Qt console built as an SSMS-class (and ultimately SSMS drop-in) replacement: manage AthenaDB in Early Access pilot, and natively administer Microsoft SQL Server, PostgreSQL, MySQL, and MariaDB — with backup, restore, and copy across databases. Full SQL Server drop-in parity is a gated milestone. Product site, Help, downloads, and edition unlocks: athenadbstudio.app (same AthenaDB account).
- Dedicated site: athenadbstudio.app — Help, downloads, account unlocks
- AthenaDB DBA pilot: Object Explorer, query, backup/restore, schema tools
- Multi-engine modules + cross-database copy — registry-gated
SDKs & integration
Native clients for your language.
The Early Access integration surface today is the C ABI and the SQLite-compatible C API. First-party language SDKs (with license-state APIs) are planned. ODBC is tracked in the engine registry but is not a GA claim.
- C ABI (Early Access)
- SQLite-compatible C API (Early Access)
- Language SDKs & ODBC — planned / tracked