Document engine
NoSQL documents and SQL tables. One authority model.
Schemaless JSON collections under the same identity and policy layer as SQL.
- Point reads, writes and prefix scans
- Secondary indexes and full-text search
- Time-travel reads with Chrono
Atlas Doc stores hierarchical JSON with LSM-tree internals. Atlas Rel runs ACID SQL with MVCC — same Guard policies on both.
Atlas Doc (NoSQL)
Path-based documents, scan queries, Bloom-filter optimized LSM storage.
Atlas Rel (SQL)
Full SQL with cost-based optimizer and row-level security via Guard.
Shared policy surface
SPL rules apply identically to doc paths and SQL tables.
Chrono versioning
Every write produces a version entry — time-travel on both engines.
Each part below is a real component of Atlas Doc + Rel. Point at one to see what it connects to, or trace a request through it.
Axis
Axis resolves sessions into a signed ContextManifest — user, org, project, roles — before any engine runs.
Guard
Sovaria Policy Language compiles to a decision tree at deploy time. Every request gets an explicit ALLOW or DENY.
Chrono
An immutable version graph for snapshots, diffs, and point-in-time restoration.