StackMap
Subscribe

auto-ontology vs neocarta

NVIDIA's ontology framework for agentic analytics: generate ontologies from metadata, ground agents in governed business meaning, validate generated SQL, and serve context via MCP, CLI and API. — versus — Neo4j Labs' semantic layer for data agents: ingest warehouse schema, business glossary, metrics and query history into one graph, then serve it over MCP so agents route queries and write grounded SQL.

The curated verdict

Both are semantic layers for data agents built from warehouse schema and business definitions; Neocarta stores it in Neo4j, Auto Ontology centres on governed ontology and SQL validation.

auto-ontologyneocarta
Stars14k156
Forks1.2k29
LanguagePythonPython
LicenseApache-2.0Apache-2.0
Last activitytoday1 months ago
Topicsknowledge-graphs, dataknowledge-graphs, data
Curated connections49

auto-ontology — the curator's take

Reach for it when agents answer business questions across many sources with conflicting definitions — the ontology pins metric meaning, validates queries and returns the SQL with every answer, and certified corrections flow back in. Its own README says it: one clean source and a fixed question set don't need this; direct SQL or a semantic layer is enough.

neocarta — the curator's take

The honest fix for Text2SQL: the model is not bad at SQL, it is blind to your data landscape. Neocarta pulls schema metadata, foreign keys, sample values, glossary terms, governed metric definitions and real query history into a Neo4j graph — only metadata crosses over, data stays in the source — then serves it to agents over MCP with full-text, vector and hybrid search that returns columns, types, example values and the FK references needed to build a join. Embeddings are optional; catalog search works from schema alone. It ships a runnable LangGraph + BigQuery agent so you can see the routing loop end to end. Read the label though: Neo4j Labs, explicitly experimental, not a supported product, 98 stars, and it assumes you are willing to stand up and maintain a Neo4j instance next to your warehouse.