# OneDroid Engram — Versioned Agent Memory in Your Own Postgres | OneDroid > OneDroid Engram is versioned knowledge and memory for AI agents. Several search engines combined for the best results, git-style history for every document — stored in a Postgres you control. Canonical: https://onedroid.ai/engram OneDroid OneDroid Engram # Portable, persistent context for every AI application. Engram is the memory layer Argus installs. Argus keeps the scenario corpus and the verifier's own track record here, so the evidence behind a verdict has a history rather than just a timestamp — and Engram runs perfectly well on its own. How Argus uses it. Models are interchangeable. Your context is not. OneDroid Engram is where an organisation's durable knowledge lives — versioned, permissioned, searched by several engines at once, and reachable by any MCP client behind any model. Every document, embedding and revision is a row in a Postgres you control. Open Synapse — OneDroid Engram is included Open OneDroid Engram directly One account covers both. Free for individuals and small teams. No credit card. query  →  vector · keyword · graph  →  fused ranking, in your database search log illustrative Why it matters ## When a frontier model is just an API call away, context is the moat. Your competitors buy the same models, on the same terms, with the same API key. The model is a brain in a jar — swappable, and getting cheaper. What it knows about your business is not, and it is the only part nobody else can buy. Which makes it worth keeping. A model session ends and takes everything with it. The next tool starts from nothing, so the same context gets re-pasted, re-explained and re-discovered — by every agent, every time. OneDroid Engram is the layer that stops that: write once, and every application you run can use it. ### Portable Reachable by any MCP client, from any harness, behind any model. Context written by one agent is available to the next — including the one you haven't chosen yet. Changing model doesn't cost you what you knew. ### Persistent and versioned Objects carry revision history, so you can see what an agent knew and when it changed. Knowledge accumulates as an asset instead of evaporating at the end of a session. ### Rich, not just a vector blob Hybrid retrieval — semantic and keyword together — over a typed object graph, so relationships like "supersedes" or "references" are explicit and traversable rather than inferred from similarity. ### Permissioned and yours Scoped by group and namespace, so context is shared deliberately rather than pooled by accident — and all of it in a database you own. Bring your own database ## Your knowledge was never ours to hold. Point OneDroid Engram at your own Postgres and that's where everything lives: documents, chunks, embeddings, history, permissions. Read it with SQL whenever you like. Back it up with the tools you already trust. Leave, and the data simply stays where it always was — with you. The same model serves a single developer's notebook and a Fortune 500's regulated knowledge base. Hybrid search ## Several engines, one answer. ### Vector Semantic similarity over embeddings — finds what you mean, not just what you typed. ### Keyword BM25 full-text ranking — exact terms, names, and identifiers never get lost in the vectors. ### Graph Typed links between objects let search follow relationships — neighbors, references, dependencies. Results are fused into a single ranking, and the vector-versus-keyword weighting is a parameter you control per query — not a black box. Versioned ## Every write is a commit. ### History Each object carries its full revision history — who wrote what, when, with git-style commits underneath. ### Diff Compare any two versions of a document and see exactly what changed between them. ### Restore Roll any object back to a previous version. Agent overwrote something important? It's one call away. ## Your agents' memory, your database. Open Synapse — OneDroid Engram is included Pricing