Self-hosted codebase intelligence

Understand the code
before you change it.

Engram connects source code, callers, contracts, tickets and review history so your team and AI assistants can investigate a change with the evidence in view.

Book a 30-minute callSee a real example

Your infrastructure. Your configured models. MCP, CLI and Explore access. Prefer to send a request?

A change to book availabilityFollow a call path into the implementation.
  1. LoanServiceBorrow↓ inferred by unique name · confidence 0.60
  2. BookRepositoryAdjustAvailability↓ resolved in the same file · confidence 0.95
  3. BookRepositoryFindById

Selected path from a captured Engram result, checked against public source. Static relationships; not a runtime trace.

Inspect the result and its limits
In production at House of Travel150+ repositories reportedGit + TFVC in one estateRead the production reference
Three questions. Connected evidence.

Start with the work in front of you.

01 / Change

What could this affect?

Inspect indexed callers, detected contracts and review context before changing a shared component.

Explore change impact
02 / History

Why is it this way?

Bring retained commits, linked tickets, reviews and authored rationale into the investigation. See where evidence is missing.

Inspect decision history
03 / Onboarding

Where should I start?

Get a repository briefing, module map and representative flows with source locations to follow.

Walk through a repository
A shared context layer

Useful to engineers.
Available to their agents.

Search across an indexed estate, trace detected call and contract relationships, and retrieve compiled architecture context through MCP, the first-party CLI or Explore.

Use Engram with MCP-capable clients such as Claude Code, Codex, Cursor and OpenCode. GitHub pull-request annotations are available as an opt-in integration.

Explore the platform and integrations
Know the boundaries

Self-hosted, with
an explicit data flow.

Run Engram’s services and index on your infrastructure with versioned Docker Compose or Helm packaging. Configure repository access and choose where embeddings and optional model reasoning run.

Source text sent for embedding or reasoning goes to the providers you configure. Language coverage, index freshness and enabled features affect the evidence returned.

Read deployment, data flow and coverage

Pricing

Annual self-hosted licensing. Every tier includes the full platform, unlimited repositories, and unlimited agent or MCP queries.

Team

Up to 25 developers

US$15k/year

For engineering teams bringing codebase intelligence into daily AI-assisted development.

Growth

Up to 75 developers

US$36k/year

For larger teams standardising Engram across multiple product areas and shared services.

Enterprise

Unlimited developers

From US$75k/year

For organisation-wide deployments, complex environments, and rollout support.

License prices are in US dollars. Infrastructure and configured model-provider usage are separate costs. Installation scope, support arrangements and any applicable taxes are confirmed in your proposal.

Paid pilot

Run Engram for 60 days against your own codebase for US$3k. The pilot fee is credited if you convert to an annual license.

Scope a pilot

See the pilot evaluation method: agree the repositories, representative tasks and evidence of success before starting.

Product roadmap

Where Engram goes next.

More dependable context, easier adoption and richer pull-request evidence. Explore the direction without dates or delivery promises.

Explore the roadmap
See Engram in context

Bring a real codebase question.

We’ll use a 30-minute scoping call to understand your repositories, tooling and evaluation goals.

Book a scoping call