| Category | AI-native analytics engine with an integrated data stack | Visual analytics suite, repositioned around Tableau Next and Agentforce |
|---|
| Who it is built for | AI product and analytics teams, plus anyone who works with data — spreadsheet users through ML engineers | Analysts and business users who work visually |
|---|
| Primary interface | The agent you already use, over MCP — plus Workspaces, notebooks, reports and data apps for the people who want a UI. All of them consume the same model rather than being the place it lives | Its own UI — drag-and-drop visual authoring, with Pulse and Agentforce agents alongside |
|---|
| Modeling language | Malloy — a modeling and query language with imports, inheritance, and public and private members | Calculated fields and Tableau Semantics, purpose-built for Tableau |
|---|
| What is open | Open core. Malloy is open source, and we build and maintain Malloy Publisher, the open-source server for Malloy models. Your model is code in your repository, and Credible is in the Apache Ossie ecosystem for semantic interchange | Vendor-owned, with a stated intent to open the Tableau Next semantic layer |
|---|
| How the model gets built | A coding agent with open-source MCP tools and agent skills, capturing context from where it already lives | Hand-built data sources and calculations; Tableau Semantics adds a shared layer |
|---|
| Governance | Governance as code. Access rules are annotations in the model itself — versioned, reviewed and composable like any other code | Row-level security and permissions in the tool, plus Salesforce identity |
|---|
| Materialization and caching | One annotation on the source, in the same file as the logic it materializes — no derived-table block, no rollup definitions, no refresh triggers, no orchestration run to schedule. Optional per source: query your own warehouse directly, or hold a source hot in Credible’s in-memory serving layer, which is how a team on Postgres gets fast serving without buying a warehouse to get it | Hyper extracts, refreshed on a schedule, or live connections. Mature |
|---|
| How an agent finds the right data | Search. Typed targets — source, dimension, measure, view, even a dimensional value — are matched against an index of the model and come back ranked, so an agent asks for what it needs instead of picking a model and touring it | List and describe the published data sources, then query them; the MCP server is hosted on Tableau Cloud |
|---|
| Where the model can be used | One model served to every surface — agents over MCP, plus APIs, an SDK, embedded dashboards, notebooks and HTML data apps. Results carry an interactive UI resource (MCP Apps, the official extension), so a client that supports it renders a real chart or table instead of the model re-narrating rows | The Tableau UI, embeds, VizQL Data Service and an MCP server hosted on Tableau Cloud; Tableau Next agents run on the Salesforce platform |
|---|
| Scale and portability | Built for globally distributed, high-availability workloads. Warehouse-agnostic on open-source Malloy — BigQuery, Snowflake, Postgres, MySQL, Trino, Presto and DuckDB, which also reads Parquet straight out of object storage including Azure Data Lake — so the model travels | Scales with Tableau Cloud or Server; Tableau Next is tied to the Salesforce platform |
|---|
| What you pay for | Usage, not seats — unlimited users on every plan, so adding people never changes the bill. Metered per organization on tokens, bytes processed, bytes served and hot storage, starting free. Your own agent’s tokens are never billed, and a query that runs on your own warehouse is not metered for the scan — only for the result it hands back | Per-seat by role, with Creator, Explorer and Viewer priced differently |
|---|