Skip to main content
← Back to Unimatrix

Security & Technical Architecture

We treat memory as infrastructure. Here is the verified technical architecture governing data encryption, processing boundaries, and operational access controls.

AES-256-GCM at Rest
HTTPS in Transit
HKDF + PBKDF2 Key Derivation
Audit rows for memory tools
PostgreSQL RLS Isolation
Docker Self-Host Parity
No Training on Your Data

System Architecture & Data Pipeline

Unimatrix processes memory through distinct capture, intelligence, storage, governance, and delivery layers.

1. AI CLIENTS & SURFACESClaude Desktop • Cursor • Windsurf • ChatGPT • Gemini • Copilot • Custom Agents • Mobile App • REST/API2. CAPTURE LAYER/api/mcp Streamable HTTP | Manifest V3 Extension | REST Tool Calls | Mobile/API ClientsExplicit tool invocation, guided save flows, and authenticated API writes3. UNIMATRIX LIBRARIAN / INTELLIGENCE ENGINEIntelligence Pipeline (Memory Formation)Normalization → Decomposition → Extraction → Contradiction Checks → PersistenceLocal ONNX embeddings (BGE-small) • semantic triples • supersession/provenance hooks4. MEMORY SUBSTRATE & STORAGECanonical Hierarchy: Spaces → Locations → MemoriesHybrid recall: pgvector semantic candidates • PostgreSQL tsvector full-text • lineage/audit contextAES-256-GCM encrypted at rest after processing • active / superseded / archived memory states5. ENTERPRISE GOVERNANCERole-Based Access Control (RBAC) • PostgreSQL Row-Level Security (RLS) • Audit LogsHuman-in-the-Loop approval patterns • Audited privileged access • Self-host infrastructure control6. DELIVERY LAYERMCP tools • REST API • extension save flows • dashboard and mobile clients
Deployment: PostgreSQL with pgvector. The current development and production target is PostgreSQL 16. Licensed self-hosting is described on the deployment page. There is no public clone URL.
Deployment →

Ingestion Boundaries & Encryption Architecture

DASHBOARD COMPOSER PATH

Browser-Encrypted Ingestion

Memories created directly within the web dashboard memory composer can be encrypted in your browser before transmission using your key derivation password. The server receives and stores ciphertext directly.

AI INTEGRATION & MCP PATH

Server-Processed Ingestion

Memories captured through AI integrations, MCP servers, browser extensions, and APIs are processed server-side so Unimatrix can perform entity extraction, classification, local HuggingFace ONNX vector embedding (BGE-small), full-text index creation, and contradiction detection. Once processed, content is encrypted with AES-256-GCM before database write.

Encryption & Key Management

In Transit

Public client-to-API traffic uses HTTPS. The negotiated TLS version depends on the client and the deployment. Internal transport security is deployment-dependent and is governed by the managed infrastructure or the organization's self-hosted network and database configuration.

At Rest

Application-layer AES-256-GCM. Memory content is stored as ciphertext encrypted within a three-level key hierarchy (root key → tenant Data Encryption Key → per-record AES-256-GCM key derived via HKDF-SHA256 from a fresh 16-byte per-record nonce used as the salt). Dashboard memories that enable passphrase encryption use PBKDF2 in the browser.

Storage Layout: [Ver][KeyVer][WrapIV 12B][WrapTag 16B][WrappedDEK 32B][Nonce 16B][IV 12B][Tag 16B][Ciphertext]

Processing and storage boundaries: Stored memory content uses AES-256-GCM before it is written to the content column. The service decrypts that content to classify it, embed it, and search it. Summaries, hints, the full-text index, and embedding vectors are stored so search can run. They are sensitive. They are not homomorphic ciphertext. Optional browser encryption for memories typed in the dashboard is separate and, when used, is not the path MCP writes take.

Access Controls & Privileged Access Model

Your memories are protected by application-layer encryption, authenticated access controls, PostgreSQL Row-Level Security (RLS), and audited privileged operations.

  • MCP tokens: A new token from Settings → MCP Tokens is displayed exactly once. Unimatrix stores a bcrypt hash for later authentication, along with a short non-secret prefix for identification.
  • Tenant Isolation: PostgreSQL RLS policies restrict database rows to the authenticated user or organization context.
  • Privileged operational access: Administrative access that decrypts content uses the server-held master key. Some account actions are written to an audit log in the same database. That log is not a digital signature and it is not published to an external ledger.
  • Model Training: We never sell your data, nor do we submit memory content to third parties to train commercial AI models.

Audit records and provenance

Audit records

Memory tools write an audit row for the action, the memory id when there is one, and a hash of the request payload. Those rows are ordinary database records. A separate hash chain exists for a smaller set of account and compliance actions and is stored in the same database. It is not a digital signature, and it is not published to an external log. Do not treat it as proof that history cannot be changed by someone who can write to the database.

Veritas Lineage Graph

Supersession and contradiction history can be tracked through Veritas provenance. The unimatrix_audit_memory_provenance tool supports auditing why a belief is held without requiring direct database access.

Data Retention & Hard Deletion

Memories, spaces, locations, and vector index entries are retained until explicitly deleted via dashboard, API, or full account deletion.

Upon account or memory deletion, primary database records and vector index entries are purged immediately. Backup snapshots purge following the standard database retention window.

Self-Hosting Security

A licensed customer can run Docker and PostgreSQL with pgvector on machines they control. The current development and production target is PostgreSQL 16. PostgreSQL 15 was not part of the verification for this page. Source access is part of an agreement. There is no public clone URL.

In a self-hosted instance, you manage the MASTER_ENCRYPTION_KEY and database infrastructure within your own private network boundary.

Read how licensed self-hosting is delivered →

Vulnerability Disclosure

Please report security issues by emailing security@deployunimatrix.com.