Lite, Server, Sync, Cluster

One engine, several shapes.

Lite — In progress (Early Access)

Embeddable, offline-first encrypted local vault with hybrid retrieval. No server required. Product: Lite.

Server — In progress

Networked multi-client runtime (default port 1440), local IPC, TLS/HTTP/2 paths. Standalone daemon, service managers, and admin surface continue to land.

Sync — In progress

Device trust, oplog/changeset foundations, and lite-sync paths exist in the engine. An enrolled replica is designed to continue serving its local application while offline, then exchange and reconcile eligible changes in both directions after reconnecting.

The approved design supports replication of the whole eligible database or an explicit scope such as a tenant, workspace, case, project, table, or policy-approved data set. Scoped replication is Planned / Early Access; it is not a GA or implementation claim.

AthenaDB Convergent Record Versioning — Planned / Early Access

The planned reconciliation model:

• merges changes to non-overlapping fields into one converged record;
• chooses the same deterministic winner on every replica when both sides change the same field; and
• preserves recoverable version history so the losing value can be inspected or restored.

Every participating replica must have an enrolled cryptographic identity. Enrollment, replication scope, and revocation ride the Trust Fabric. See the AthenaDB Sync product page for the public overview.

Cluster — Planned

Replication, sharding, failover, Sentinel HA, multi-region — reserved in licensing, not started as a GA product surface.

Related: Architecture · Connectivity