Composable Analytics: Agent-Built Views, Governed Metrics
Composable analytics lets agents assemble HTML dashboards from governed metrics. See how reusable definitions support generated views and fixed reports.
Read the storyField notes, product updates, and practical guides from the team building Datus.
111 stories
Composable analytics lets agents assemble HTML dashboards from governed metrics. See how reusable definitions support generated views and fixed reports.
Read the storyConvert semantic models to Ossie from Cube, dbt, Omni and Power BI. Try ready-made examples, prepare complete source files, and validate the resulting YAML.
Read the storyWhat is an AI dashboard? See how agents turn a question into a visual report, where semantic metrics keep it consistent, and when fixed dashboards still win.
Read the storyLearn how the entity-attribute-value (EAV) model stores flexible fields, where analytics counts go wrong, and how to prepare a reliable semantic model.
Read the storyBusiness glossary vs semantic layer: see how approved terms become tested metrics. Follow one active-customer example from wording to SQL and agent answers.
Read the story
DOSI 0.1.13 adds level of detail calculations for governed metrics, while Datus Agent 0.4.3 brings DOSI into its workflow and adds SQL lineage analysis.
Read the storyUse Apache Ossie converters to export semantic model YAML to dbt, Cube, Snowflake and more. Try examples, inspect output files, and check conversion limits.
Read the storyExplore five approaches to ontology for AI agents, from semantic layers and open standards to knowledge graphs and operational models, with a selection guide.
Read the storySee semantic model examples for revenue, customer regions, and average order value. Download a tested Apache Ossie YAML model and check its answers yourself.
Read the storyHeadless BI separates business metrics from dashboards so apps and AI agents can use them too. Learn when it helps, where it breaks, and how to test it.
Read the story
Conversational BI lets people explore data through follow-up questions. Learn how semantic models preserve metrics, filters, and trust across every turn.
Read the storyDatus's September 2026 update: putting the semantic layer in the agent loop as a deterministic checker, plus Datus Agent 0.4.2 and Dosi 0.1.12 release notes.
Read the storyAgentic analytics uses AI agents to plan and act on data, not just answer questions. See how it differs from conversational BI and needs governed metrics.
Read the storyCompare Cube.dev alternatives by use case: keep Cube for embedded analytics, use dbt for governed metrics, or use Ossie and Dosi for portable agent queries.
Read the storyText-to-SQL breaks on real warehouses because the model guesses what your data means. See why NL2SQL fails and how a semantic layer fixes accuracy.
Read the story
A semantic-layer-based ontology starts from governed metrics and relationships, then builds entity context and concept paths for AI agents on Apache Ossie.
Read the story
AI data agents need more than metrics and more than a glossary. Learn how to build an ontology, an entity plane and typed query functions on a semantic layer.
Read the storySemantic layer vs ontology is the wrong final question. See why AI data agents need both — governed metrics first, then ontology and agent context on top.
Read the story
Why we built Dosi: an AI-native semantic layer is an open spec plus a deterministic planner, compiler and runtime, plus an agent-native tool interface.
Read the story
A 10-minute Apache Ossie + Dosi quick start: install Dosi, query a 191K-row DuckDB dataset from the CLI, connect it to Claude Code over MCP, and ask why revenue dropped.
Read the storyHow Dosi with Cube stacks API-first semantic serving with OSI-native multi-dialect SQL execution — complementary layers for agents and warehouses.
Read the storyCompare Dosi and dbt MetricFlow as execution engines: same OSI interchange can feed dbt graph runtime or OSI-native multi-dialect compile — when to use each.
Read the storyHow agents query governed OSI metrics via Dosi MCP: structured error codes, Claude Code and Codex patterns, and why semantic MCP beats raw SQL.
Read the storyOSI (Apache Ossie) defines portable semantic metadata, not query execution. Learn the interchange-vs-runtime gap and why native OSI engines matter.
Read the story
Read-only data agents answer questions; write agents deliver work. That needs plugins, permission modes, and a sandbox with checkpoint, branch and merge.
Read the storyWhat a native Apache Ossie (incubating) implementation is, how a native Apache Ossie engine differs from OSI converters, and why execution engines like Dosi matter for portable semantics.
Read the storyWhat Anthropic's Data plugin is: Cowork and Claude Code workflows for SQL, charts, and dashboards — plus how it differs from Genie and Cortex Analyst.
Read the storyDosi compiles Apache Ossie (OSI) YAML into SQL across 15+ warehouse dialects — CLI, REST, MCP, and Python — so metrics are defined once and used everywhere.
Read the storyWhat Cortex Analyst is: Snowflake's managed text-to-SQL API grounded in Semantic Views — verified queries, REST integration, and why it is not Cortex Code.
Read the storyWhat Databricks Genie is: domain-scoped agents (formerly Spaces) that answer with SQL and charts under Unity Catalog — and how they differ from Genie Code.
Read the storyVirtual OLAP for Excel, Power BI, and agents — AtScale's SML, DSO pricing, MDX/DAX, and MCP, and when the cube is the wrong unit.
Read the storyWhat Timbr.ai is: a SQL-native ontology over your warehouse — how it differs from Cube and AtScale, and when the extra layer is worth it.
Read the storyThe Datus OSI (Apache Ossie) semantic adapter authors vendor-neutral YAML, validates it, and queries metrics via MetricFlow without leaking backend fields into source models.
Read the storyDatus Knowledge stores schema, semantic models, metrics, reference SQL, templates, and platform docs so a data engineering agent retrieves meaning — not a schema dump.
Read the storyDatus 0.3 ships built-in task subagents. AskMetrics answers KPIs from governed metrics; gen_sql and explore handle SQL and schema — not one universal chat.
Read the storyOntology in data and AI: classes, relationships, and rules — and the three productizations buyers confuse in 2026: OWL/RDF, Palantir, and SQL ontologies.
Read the storyApache Ossie (formerly Open Semantic Interchange, OSI) vs Cube: open standard meets headless semantic layer — format, execution, governance, AI access.
Read the storyApache Ossie (formerly Open Semantic Interchange, OSI) vs RDF/OWL: how formal Semantic Web ontologies differ from lightweight YAML interchange.
Read the storyA year of building Datus: models, frameworks and interfaces change fast, but building and maintaining good context is still the hardest part of a data agent.
Read the storySyntactic interoperability is shared format; semantic interoperability is shared meaning. See the difference, failure modes, and why it matters for AI agents.
Read the storyApache Ossie (formerly Open Semantic Interchange, OSI) vs warehouse-native semantics: Snowflake, Databricks, portability, lock-in, and AI grounding.
Read the storyApache Ossie (formerly Open Semantic Interchange, OSI) vs LookML: lock-in trade-offs, migration paths, and metric portability for AI agents.
Read the storyApache Ossie (formerly Open Semantic Interchange, OSI) vs dbt MetricFlow: definition vs execution, portability, and why both matter for AI agents.
Read the storySnowflake OSI is search shorthand for Snowflake's role in Open Semantic Interchange — now Apache Ossie — plus Semantic View import/export via Ossie YAML.
Read the story"Cursor for data engineering" means an agent that runs your data system — warehouses, metrics, and reference SQL — with evolvable context, not autocomplete.
Read the story
Thirteen months inside a restaurant chain's move from ChatBI to a DataAgent: the paradigm shift, layering by determinism, security hooks, and the pits we hit.
Read the storyCompare 16 semantic layer tools for dbt metrics, embedded BI, warehouse-native views and portable AI agents. See Dosi's Apache Ossie path and each tool's fit.
Read the storyChange data capture (CDC) definition, the three CDC methods — log-based, trigger, query — plus real-time use cases, pitfalls, and CDC to the lakehouse.
Read the storyApache Hudi definition, how copy-on-write and merge-on-read tables, record-level upserts and incremental queries work, Hudi vs Iceberg vs Delta, and agent context.
Read the storyApache Iceberg definition, how its hidden partitioning, snapshots and schema evolution work, Iceberg vs Delta Lake vs Hudi, and why AI agents need table-aware context.
Read the storyMedallion architecture definition: Bronze, Silver, and Gold lakehouse layers, what belongs in each, the anti-patterns, and which layer an AI agent should query.
Read the storyData contract definition: a machine-checked producer–consumer agreement on schema, semantics, quality, and SLAs. Tools, enforcement, and the agent angle.
Read the storyA lakehouse catalog tracks table metadata for query engines. Compare Hive Metastore, AWS Glue, Unity Catalog, Apache Polaris and Snowflake Horizon.
Read the storyApache Ossie (formerly Open Semantic Interchange, OSI) vs MetricFlow: portable semantic standard vs dbt's execution engine, and when to use each.
Read the storyData lake definition, schema-on-read architecture, zones and file formats, the data swamp problem, data lake vs data warehouse, and what AI agents need to query one.
Read the storyData warehouse definition, architecture (ETL, dimensional models, columnar MPP), how it differs from a data lake and lakehouse, and what AI agents need to query one.
Read the storyLakehouse definition, how it differs from data lakes and warehouses, open table formats (Iceberg, Delta, Hudi), and why AI agents need lakehouse-aware context.
Read the storyWhy reliable AI data engineering needs knowledge, planning, review, controlled execution, and reconciliation, not just SQL generation.
Read the storyWhat defines an AI-native data platform, how it differs from platforms with bolted-on AI features, and why data engineering agents are the missing infrastructure layer.
Read the storyBest data engineering agents in 2026 compared by stack fit, context, openness, and enterprise readiness.
Read the storyA detailed comparison of Snowflake Cortex Code, Databricks Genie Code, and Google BigQuery Data Engineering Agent — and the case for open, cross-stack alternatives.
Read the storyGoodData's evolution from cloud BI startup to GoodData.AI — what it reveals about the industry shift toward AI-native analytics and the role of the semantic layer.
Read the storyHow Cube.dev evolved from an open-source semantic layer to the D3 Agentic Analytics platform, and what its trajectory means for data engineering.
Read the storyMetricFlow fits dbt teams that govern metrics in Git. See where it works, when an Apache Ossie runtime such as Dosi helps, and how to choose for AI agents.
Read the storyA complete guide to Open Semantic Interchange (OSI) — now Apache Ossie (incubating): what it standardizes, who's behind it, and why portable semantics matter.
Read the storyWhat an ontology is, what a semantic layer is, where the two overlap, and the signals that tell you when a data team actually needs a formal ontology.
Read the storyData agent definition, types, capabilities, and how a data engineering agent fits as the specialized subclass that builds and evolves data context.
Read the storyData mesh definition, four principles, comparison to data fabric, and how subject trees and subagents align with domain ownership.
Read the storyMetric layer definition, MetricFlow examples, semantic layer vs metric layer differences, and why AI agents need standardized metrics.
Read the storySemantic model definition, key components, how it fits into a semantic layer, and how it differs from warehouse-native semantic views.
Read the storyRAG definition for data engineering: retrieving schema, metrics, and SQL history to ground NL2SQL and data engineering agents.
Read the storyData catalog definition, popular tools, and why data engineering agents need context engines beyond discovery metadata.
Read the storySchema linking definition for text-to-SQL, common failure modes, and how dual-dimension context improves column resolution.
Read the storyText-to-SQL definition, NL2SQL pipeline stages, accuracy limits, and how data engineering agents improve with persistent context.
Read the storyData engineering agent vs SQL copilot: persistence, feedback, team context, and when each tool fits.
Read the storyHow a one-person data team uses a data engineering agent to reduce SQL translation work and ship self-service analytics.
Read the storySubagents explained: domain-specific data agents built from scoped context, feedback, and governed access.
Read the storyBuild a first data engineering agent with Datus: install, ask questions, generate context, and create a subagent.
Read the storyData engineering agent vs Claude Code: when persistent data context matters and when a coding agent is enough.
Read the storyEnterprise data engineering agent requirements: shared context, RBAC, auditability, reliability, and governance.
Read the storyBest data engineering agents in 2026 compared by stack fit, context, openness, and enterprise readiness.
Read the storyMCP for data engineering: how agents connect to databases, orchestrators, quality tools, and context services.
Read the storyCompare open-source data engineering agents and learn what a private deployment must check: model endpoint, data flow, credentials, and access controls.
Read the storyHow a context engine improves data engineering agent accuracy with schemas, validated SQL, and feedback loops.
Read the storyContextual data engineering explained: schemas, semantics, and feedback loops for durable data agents.
Read the storyFour products now ship as a data engineering agent — but they are not the same thing. Working definition, side-by-side comparison, and where persistent context separates agents from chat windows.
Read the storySemantic layer defined: the business translation layer between raw tables and analysts, what it includes (metrics, dimensions, entities), how it differs from metric layers and catalogs, and why static models break under AI agents.
Read the story
Why the one-person data team is coming, the three skills a full-stack data engineer needs, and why validation — not SQL generation — is now the real bottleneck.
Read the storyLearn how MCP and Skills connect Datus to your data catalog, metric layer, scripts, and quality workflows across the full data toolchain.
Read the storySee how Ask User, session management, Explore, and action display make Datus data agents easier to trust, control, and use every day.
Read the storyPluggable storage adapters that separate relational and vector storage from the agent core for enterprise flexibility.
Read the storyThe General Chat Agent goes beyond SQL generation to support exploration, investigation, and knowledge-building.
Read the story
Datus 0.2.6 adds a more general chat agent, stronger planning flows, deeper data exploration, and broader support across the data stack.
Read the story
Compare agentic and traditional data engineering across workflows, tooling, team structure, and reliability in production.
Read the story
See how agentic ETL adds context-aware planning, validation, workflow-state reasoning, and human review beyond traditional ETL.
Read the story
Learn where AI data pipeline automation works, how to design the architecture, and which tradeoffs matter before scaling it.
Read the story
Learn how MCP improves data workflow automation with structured tool access, safer execution paths, and tighter system integration.
Read the story
Learn how structured context improves AI agent output by grounding reasoning in metrics, semantics, and workflow state.
Read the story
Learn how semantic modeling improves agentic analytics by grounding AI agents in shared metric definitions and governed business context.
Read the story
Learn how an agentic data team operates with clear roles, review loops, guardrails, and human-in-the-loop control across planning, execution, and governance.
Read the story
Learn how MCP extensions give data engineering agents controlled tool access, safer execution paths, and more reliable automation.
Read the story
See what autonomous data engineering looks like in practice with structured context, bounded agent actions, human review, and workflow automation.
Read the story
Learn why semantic context helps AI agents reason reliably across data systems by grounding definitions, relationships, and constraints.
Read the story
Learn why data engineering needs agents, not just copilots, and how agentic workflows improve execution, reliability, and control.
Read the story
Learn why reliable data agents need structured context, workflow state, metrics, semantic models, and guardrails beyond good prompts.
Read the story
Learn why the Agentic Data Stack goes beyond AI SQL tools by combining context, semantics, workflows, and governed execution.
Read the storyA practical architecture blueprint for data engineering agents, with Datus patterns for context, subagents, and governed execution.
Read the storyExplore practical data engineering agent use cases and how Datus helps teams improve speed, quality, and governance.
Read the storyLearn what a data engineering agent is, why context matters, and how Datus turns AI into reliable, production-ready data workflows.
Read the story
Learn why SQL agents fail without governed context and how Datus uses contextual engineering and subagents for reliable workflows.
Read the storyIntroducing the Datus blog with insights on AI-native data engineering, context engineering, and reliable data workflows.
Read the story