Deep Semantic Search
Understand intent across languages with vector embeddings. Powered by Azure OpenAI text-embedding-3-large, batched and parallelised at index time.
Engram builds call graphs, traces execution flow, detects cross-repo contracts, and maps blast radius across entire codebases.
Parses 14 languages via tree-sitter AST, links code to work items from 9 providers, and pre-compiles knowledge artifacts for zero-cost retrieval. Self-hosted inside your perimeter, exposed to your AI tools over MCP. Your agents answer "why," not just "where."
Contact us for demoUnderstand intent across languages with vector embeddings. Powered by Azure OpenAI text-embedding-3-large, batched and parallelised at index time.
Connect commits, work items, PR reviews, code reviews, call graphs, import graphs, and type hierarchies into a single, queryable knowledge graph with temporal scoring.
Materialised contract maps surface producers and consumers across every indexed repo. One question, every caller. No per-repo blind spots.
Static call-site extraction with multi-pass name resolution across 14 languages. Trace forward execution from any HTTP route or entry point. Reverse BFS finds all upstream callers with log-scaled risk scoring. Know the blast radius before you touch a line.
34 MCP tools plus a transparent, secure API proxy for your AI assistants. search_code, contract_map, trace_flow, structural_impact, find_impact_graph, detect_communities, and more.
Union-Find clustering over call graph edges automatically discovers architectural modules. Labels by dominant directory, identifies entry points, and generates architecture docs without any LLM cost.
Per-community architecture overviews with entry points, and per-directory API surface bundles with import graphs. Compiled at index time.
Per-symbol bundles with callers, callees, work items, review context, and commits. Plus materialized cross-repo contract topology. Zero LLM cost at query time.
Engram runs against working codebases that change all day. The worker pipeline is designed for that.
Workers heartbeat into the queue. If a pod disappears mid-job, another picks the work up from where it stopped. No silent stalls, no duplicate runs.
Jobs interrupted by a rolling deploy are auto-restarted at the front of the queue. Canary deploys ship with telemetry baselines, dev environments serialise to keep things sane.
Priority-weighted dequeue and dynamic per-job timeouts. A 30-minute mono-repo full reindex won't starve the canary checking a five-file change.
Three modes, pick per repo or per run:
Add your Engram MCP configuration to an AI tool.
{ "mcpServers": { "engram": { "url": "https://..." } } }
A dashboard for the people who run Engram, not just the people who query it.
In-person or remote setup
Contact Mitch at: mitch@pragmaticcoder.com