Graphenium logo
Graphenium
★ 28
vs
engrim logo
engrim
★ 299

Graphenium vs engrim

Graphenium: Graphenium provides a provenance-aware structural memory for AI coding agents, transforming code repositories into persistent, queryable architecture graphs. This allows agents to efficiently navigate large codebases, understand relationships with confidence, and preserve context across sessions, saving tokens and improving reasoning.; engrim: Engrim is a universal, local-first SQLite memory engine specifically engineered for autonomous AI coding agents, designed to solve the '200,000-token context window trap'. It provides high-precision, curated episodic working memory, allowing developers to switch between various models and environments on the same codebase without losing architectural decisions or project state.

01

TL;DR

Graphenium logo
GrapheniumMemory & Context · ★ 28

Efficient navigation of large codebases for AI agents.

engrim logo
engrimMemory & Context · ★ 299

Maintaining Project Context Across Agent Sessions: Developers can use Engrim to prevent LLMs from losing architectural decisions, user constraints, or project state when chat sessions are cleared or models are switched.

02

Side-by-Side Comparison

Field
Graphenium logoGraphenium
engrim logoengrim
Category
Memory & Context
Memory & Context
Stars
★ 28
★ 299
License
MIT
MIT
Install Command
curl -fsSL https://raw.githubusercontent.com/lambda-alpha-labs/Graphenium/main/install.sh | sh
pip install engrim
Updated
3mo ago
3w ago
Open Source
Yes
Yes
Tags
Code Graph, AI Coding Agents, Repository Analysis
Episodic Memory, LLM Context Management, AI Agents
03

Features

Graphenium logoGraphenium
01Persistent, Queryable Repository Graph
02Provenance-Aware Trust Model for Relationships
03Symbol-Level Diff and Blast-Radius Analysis
04Policy-Based Quality Gates for CI/CD
05Agent-First MCP Interface for Structured Queries
engrim logoengrim
01Precision Working Memory: Replaces raw transcript replay with ~4,000 characters of high-precision, curated episodic memory, injected at boot with zero attention dilution.
02Cross-Model/Agent Compatibility: Provides a universal substrate for memory, allowing decisions made in one agent (e.g., Claude Code) to be visible and usable in others (e.g., Antigravity, Cursor).
03Local-First & Private Storage: Stores all memories locally in a SQLite file (~/.engrim/memory.db) with WAL mode and POSIX 0600 permissions, ensuring 100% privacy with no cloud sync or telemetry.
04Self-Healing Diagnostics: The `engrim doctor --fix` command verifies all hooks and installs portable PATH fallbacks, ensuring reliable operation across machines and OSes without silent failures.
05Hybrid Retrieval & Minder: Employs a hybrid lexical (BM25) and vector (model2vec) search for efficient and relevant memory recall in approximately 30ms.
04

Use Cases

Graphenium logoGraphenium
↳Efficient navigation of large codebases for AI agents.
↳Providing architecture maps for AI agent orientation.
↳Performing impact analysis for code changes and refactoring.
↳Enforcing CI trust gates and improving code review efficiency.
↳Persisting repository structural memory across AI agent sessions.
engrim logoengrim
↳Maintaining Project Context Across Agent Sessions: Developers can use Engrim to prevent LLMs from losing architectural decisions, user constraints, or project state when chat sessions are cleared or models are switched.
↳Collaborative Multi-Agent Development: Enabling multiple AI coding agents (e.g., Antigravity, Claude Code, Cursor) to work on the same codebase and share a consistent, evolving memory store.
↳Continue-As-Clear Workflow: Allows users to clear their agent's context window at any time, with Engrim automatically re-injecting the active memory pack for seamless continuation without memory loss.
↳Auditing Agent Provenance: Tracking which agent made specific architectural decisions or added facts to the project's memory, enhancing transparency in multi-agent environments.
FAQ

FAQ

What is the difference between Graphenium and engrim?
Both Graphenium and engrim are in the Memory & Context category. Graphenium has 28 stars, while engrim has 299 stars.
Which is better, Graphenium or engrim?
The best choice depends on your use case. Choose Graphenium if Efficient navigation of large codebases for AI agents., and engrim if Maintaining Project Context Across Agent Sessions: Developers can use Engrim to prevent LLMs from losing architectural decisions, user constraints, or project state when chat sessions are cleared or models are switched..
Is Graphenium free or open source?
Yes, Graphenium is open source on GitHub (MIT).
Is engrim free or open source?
Yes, engrim is open source on GitHub (MIT).
Cloud Infrastructure
Ad

Deploy on DigitalOcean

Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.

Claim $200 Free Credit
→

Related