EvoOntology vs helix-foundry
Renmin University's self-evolving ontology layer for data agents: builds a workload-grounded ontology over tables, files and databases, serves it via MCP, and evolves it from agent trajectories. — versus — HelixDB's ontology builder: connect databases, tools and docs, let an agent draft an ontology, and load it all into HelixDB as one explorable, queryable graph with provenance.
Both build ontologies over data for agents. EvoOntology is a research layer that evolves the ontology from workloads; Foundry is a product with connectors and a UI.
| EvoOntology | helix-foundry | |
|---|---|---|
| Stars | 1.2k | 2.1k |
| Forks | 100 | 302 |
| Language | Python | Go |
| License | MIT | Apache-2.0 |
| Last activity | 28 days ago | yesterday |
| Topics | data, knowledge-graphs | knowledge-graphs, data |
| Curated connections | 5 | 4 |
EvoOntology — the curator's take
The research answer to stale semantic layers: instead of hand-maintained definitions, EvoOntology builds an ontology from your data and real workload, lets agents fetch only the semantics a step needs through MCP, and proposes targeted updates from execution trajectories, publishing a new version only when paired evaluation beats its parent. Claude Code and Codex plugins make it easy to try. It is two-week-old research code from a university lab: treat the evolution loop as an experiment, keep versions reviewable, and give it read-only credentials. If you want definitions humans own and govern, a curated semantic layer (ktx, neocarta) is the conservative choice.
helix-foundry — the curator's take
Use it when your company data is scattered across databases and SaaS tools, and you want one graph that agents and humans can query, with every value traceable to its source. Runs locally with Docker or on Helix Cloud. Skip it if you're not willing to adopt HelixDB as the store, or if a single warehouse plus a semantic layer already answers your questions. The agent drafts the ontology; you still have to review it.