The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Gctrl listing page.
Ground your data. Command your AI.
GCTRL turns your scattered documents, databases, and code into one governed knowledge graph — then grounds your LLMs and agents on it, with enterprise-grade access control, entirely on your own infrastructure.
Most "AI memory" is a pile of vector chunks: fuzzy recall, no structure, no provenance, no permissions. GCTRL is graph-native — entities, typed relations, dossiers, and hybrid retrieval — and it runs 100% locally, so nothing leaves your building.
The pitch in one line: point GCTRL at your data, get a governed knowledge graph, and let any agent (Claude Code, Cursor, Codex…) read and write it as durable, access-controlled memory.
GCTRL is four modules over one graph, plus an agent layer:
| Module | What it does |
|---|---|
| KEX — Knowledge Extraction | Point it at PDFs, docs, plain text, or a code repo → it extracts entities and typed relations into the graph. Local NER + local relation extraction, zero cloud. Code is parsed via AST into files/classes/functions/imports/calls. |
| FUSE — Knowledge Fusion | Merge many sources and graphs into one canonical graph. Deterministic entity resolution and link discovery reconcile duplicates and contradictions across systems. |
| Manage KGs | Organize knowledge into compilations, schedule incremental or full refreshes, and gate every node, edge, and chunk by clearance level. |
| Talk-to-Graph | GDPR-compliant RAG over your graph. Local inference; sessions stay in browser memory — no server-side conversation storage. |
| Pi + MCP gateway | A built-in agent, plus an MCP server so external agents get governed memory: store, query, get_dossier, search_entities, get_neighbors, shortest_path, ingest_repo, and more. |
One command brings up the whole stack:
When it finishes, open the dashboard at http://localhost:3001 and create your admin account. The installer detects what you already run (graph store, vector store, local LLM), deploys only what's missing, and pulls a local model so you can start immediately.
Full walkthrough — install → connect a model → activate a license → connect an agent → ingest your first PDF: gctrl.tech/docs/quickstart.
Uninstall (keep data) / full reset:
Give any MCP-capable agent durable, access-controlled memory over your graph. Generate a scoped token in Settings → Agent, then drop this into Claude Code, Cursor, Codex, or Claude Desktop:
Your agent now reads and writes a real knowledge graph — scoped to exactly what its token is cleared for. See Agents & MCP.
GCTRL is built for regulated, multi-tenant environments:
Designed ISO 27001-aware, aimed at TISAX Level 3 readiness. See Access Control and Compliance & Sovereignty.
The fusion core (entity resolution / link discovery) is competitive with supervised state-of-the-art — while running unsupervised and fully on-device:
| Task | GCTRL (unsupervised, local) | Supervised SOTA |
|---|---|---|
| Clean structured records (DBLP-ACM) | F1 0.967 – 0.976 | ~0.989 |
| Dirty textual records (Abt-Buy) | F1 0.866 | ~0.891 |
No labels, no cloud, your data never leaves the machine. More in Benchmarks.
A Rust control plane orchestrates Python extraction/fusion workers, a React UI, and local inference — all over Docker Compose.
/v1 endpointFull docs at gctrl.tech/docs:
The bundled compose files ship with well-known placeholder secrets (POSTGRES_PASSWORD, NEO4J_PASSWORD, JWT_SECRET, …) so GCTRL runs out of the box on localhost. Set your own real values (via a local .env, never committed) before exposing GCTRL to a network. A predictable JWT_SECRET lets anyone forge admin tokens; default DB passwords are public knowledge.
GCTRL is dual-licensed:
LICENSE): free to use, modify, and self-host, as long as your own stack stays open under the AGPL.See LICENSING.md for what each option allows and how to obtain a commercial license.
GCTRL stands on excellent open-source work. Full third-party notices and licenses: docs/LICENSES.md.
Neo4j · Qdrant · Ollama · GLiNER · Qwen · PostgreSQL · Redis · React · Rust / Axum · FastAPI · LIMES.