live wire
▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent▸Graph-repair retrieval cut F1 by 0.126 on one suite; a learned router used fewer tokens than always-on retrieval in all sixLin et al. / arXiv▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent▸Graph-repair retrieval cut F1 by 0.126 on one suite; a learned router used fewer tokens than always-on retrieval in all sixLin et al. / arXiv
nl2sql.ai
analysisOpen-source watch

Semantix puts a governed capability layer around NL2SQL—but it is still a work in progress

The new Apache-2.0 project treats semantic definitions and read-only execution policy as infrastructure, not prompt context. Its repository is substantive, but release and adoption evidence are absent.

By The Tools Desk· Nov 7, 2026the quick take — two AI hosts go live when you do

A new open-source entrant is trying to make natural-language data access look less like a prompt wrapper and more like a governed control plane. Semantix, created on GitHub on November 6, describes a semantic intelligence platform in which agents discover and execute registered capabilities instead of connecting directly to databases or business APIs. The repository is Apache-2.0 licensed and was still being pushed on November 7. GitHub’s repository record also shows the reality check: zero stars, zero forks and no tagged release at the time of this review.

The architectural bet

The project’s clearest idea is that published business semantics should outrank generated examples. Its README says semantic models define entities, relationships, metrics, dimensions and terminology; historical queries can enrich retrieval, but cannot override published metric definitions. Initial engine integrations name Wren Core for semantic compilation, Vanna for text-to-SQL and example retrieval, and SQLGlot for SQL parsing and dialect handling. Semantix README

Execution is organized around a capability registry spanning semantic data, functional APIs and knowledge retrieval. The stated policy is read-only across SQL, APIs, MCP tools and custom integrations, with calls routed through a capability executor and policy/audit layer. That is a useful distinction from projects that describe safety only as a prompt instruction or a database credential choice. The same README says Semantix can act as both an MCP server and an MCP client, exposing approved capabilities while importing external tools into the same governance path. Semantix README

More than a landing page, less than a release

This is not only an architecture diagram. The committed tree contains FastAPI routes for data sources, semantic models, queries, capabilities, integrations and ChatBI; Alembic migrations; query and capability modules; tests; an example metric definition; and Docker Compose scaffolding. The repository also contains dated MVP design and implementation-plan documents. Repository tree

But the project labels itself WIP, and its broad README describes considerably more than the current adoption evidence can validate. There is no tagged release, published benchmark, independent security audit, external deployment report or visible user community in the repository record reviewed here. Semantix repository

The directory verdict is therefore narrow: Semantix is worth tracking because it commits to semantic authority and centralized execution policy, and because enough implementation exists to distinguish it from a concept page. It is not yet evidence that this control-plane design works under production workloads. The next meaningful signals will be a reproducible release, tests that demonstrate the read-only boundary against adversarial inputs, and an evaluation showing whether the semantic layer improves execution accuracy rather than merely organizing the system.

sources

Filed by The Tools Desk. Corrections: desk@nl2sql.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk