← Platform Overview
Feature Pillar
Persistent Codebase Memory
Never lose architectural context or decisions across sessions.
PostgreSQL 16 with strict Row-Level Security, vector embeddings, and knowledge graphs retain ADRs, runbooks, and codebase history indefinitely.
Chapters:
Watch on YouTube (@EngraAI) →
Querying Persistent Memory
BASH
$ engra ask "database indexing policy"
$ engra repo link arenberg-engineering/core
View Full Searchable Transcript
Engra maintains persistent memory across your entire engineering team. Unlike local scratchpads that disappear
between sessions, Engra stores architectural decision records, past debugging traces, and documentation in a
tenant-isolated PostgreSQL 16 store with cryptographic encryption at rest.
Frequently Asked Questions
Is my codebase data used to train AI models?
No. All memory stores enforce train_ok=false by default under contractual zero-data-retention and zero-training agreements.
How is tenant memory isolated?
Every database query enforces PostgreSQL 16 FORCE ROW LEVEL SECURITY with tenant identification digests and Cloud KMS AES-256-GCM encryption.