Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
A

alexeyban/EKOS

EKOS is an AI-native platform that continuously reconstructs, compiles, stores and serves enterprise knowledge

Before you install: no copy-paste command · license MIT · link reachable

First step: nothing runnable here yet - start from the repository: https://github.com/alexeyban/EKOS

View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Star count
28 ★ · alexeyban/EKOS · read from the GitHub search API · (checked 2026-11-13 20:00:50)
Source
read directly from its GitHub page · type: open-source project
Harvest history
first seen 2026-11-06 · last seen 2026-11-14 · seen 9× · listed by 2 sources
Score
score 203 · 28 ★ · 2 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository alexeyban/EKOS;first catalogued 2026-11-06;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.

# EKOS — Enterprise Knowledge Operating System

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

EKOS is the open-source knowledge layer for AI agents: a compiler that turns source code, SQL,
documentation and Git history into evidence-backed knowledge that agents query over MCP. Project
site and documentation: ekos.dev. Install: ekos.dev/docs/getting-started/installation
(a setup wizard in your browser on Linux, Windows 11 and macOS — see Installation).
Unlike traditional enterprise systems that manage data, documents or metadata independently, EKOS treats the entire enterprise as a living knowledge system — a permanently evolving semantic model that can be trusted by both humans and AI.
Text-to-SQL benchmark: on BIRD Mini-Dev (release 1024, 302 hold-out questions over 11 databases), the same model, Claude Haiku 5.5, scores 53.3% execution accuracy on raw DDL, 71.5% on the knowledge EKOS compiles from each database, and 76.2% when it also checks its SQL against the data with EKOS's tools (+22.9 points, significant on paired questions), for about a quarter of a cent per question. Every question, the SQL it produced, tokens, cost and the scorer's parity with BIRD's official evaluator: BIRD Mini-Dev on EKOS.
First benchmark: on a real 2,022-file open-source repo (plausible/analytics), cold ingestion takes 34 seconds, and answering real questions from the compiled ledger costs 67-93% fewer tokens than raw grep-based search over the source — measured with a standard tokenizer (tiktoken), not a hand-rolled estimate, with the one case grep wins included rather than hidden. Full methodology, every command, and every raw output: The First Benchmark Number.
## About
EKOS is a compiler for enterprise knowledge, not a database or document store. It observes an
enterprise's existing systems — source code, Git history, SQL schemas, GitHub issues/PRs,
Confluence, local PDF/DOCX documents — without interpreting them, compiles
those observations through deterministic passes into a Canonical Knowledge Model, and stores the
result in an append-only ledger where every conclusion carries the evidence it was derived from. AI
agents (Claude Code among them) read that ledger through a read-only Model Context Protocol server
(ekos mcp serve, RFC 0013) — they never touch raw enterprise systems directly.
The project follows an RFC-first workflow (docs/rfcs/): every capability is designed in writing
before it's implemented, and the devlogs/devlog.md files are the running record of
what shipped, why, and what was learned building it. It is written in Rust (2024 edition) as a
Cargo workspace, and is licensed under the MIT License.
## The Problem
Modern enterprises contain enormous amounts of valuable knowledge distributed across disconnected systems: source code, databases, data warehouses, documentation, wikis, Git repositories, infrastructure-as-code, APIs, runtime logs, and monitoring systems. Every system contains only a partial description of reality. Documentation becomes outdated. Employees leave. Business logic remains hidden inside production code. AI assistants receive fragmented, inconsistent, and often contradictory information.
Enterprises continuously lose knowledge.
## The Insight
The enterprise already contains its own documentation — embedded inside source code, SQL, infrastructure definitions, APIs, logs, deployment history, schemas, and runtime behaviour. The problem is not missing information. The problem is the absence of a compiler capable of transforming enterprise reality into enterprise knowledge.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/alexeyban-ekos/)
Source
github · https://github.com/alexeyban/EKOS
Browse by field
Open source
Traction
28 ★
Listed by
2 independent sources
added
today

More like this

All 1,671 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index