live wire
▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸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▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸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
nl2sql.ai
newsPricing

Tableau’s capacity pricing covers AI agents—but authors still need seats

The new Viewer Blocks widen access without per-viewer licenses or overage charges, while Creator and Explorer licensing—and an opaque contact-sales price—remain part of the deployment math.

Named-user seats versus shared capacity for viewers and AI agents
Side by side: what changed
By The News Desk· Sep 30, 2026the quick take — two AI hosts go live when you do

Tableau has changed the licensing boundary for analytics consumed by large audiences and automated systems. Its new Tableau Cloud capacity model lets organizations buy shared Viewer Blocks for employees, partners, customers and AI agents instead of assigning every viewer an individual license. Tableau says the same blocks can cover MCP integrations and headless BI workflows, with no overage charges. Tableau’s announcement and pricing page describe the model.

Consumption moves to capacity; creation does not

The practical distinction is between producing analytics and consuming them. Tableau says customers first determine how many Creator and Explorer licenses they need, then use capacity blocks for broad Viewer access. Creators and Explorers therefore remain licensed per user under the announced Cloud model. Every deployment also requires at least one Creator license, according to Tableau’s pricing page.

That matters for agent deployments because an automated workflow does not erase the human authoring layer. Teams still need licensed people to create workbooks, curate data sources, administer content and build Tableau Knowledge graphs. Capacity changes how widely those assets can be consumed; it does not turn authoring into an unmetered service.

Agent access joins the Viewer pool

Tableau explicitly places AI agents and automated workflows—including MCP and headless BI uses—inside the capacity audience. The blocks are shared across a deployment, and Tableau says customers can add blocks as the audience grows. The model is offered for Tableau Cloud Standard, Enterprise and Cloud+, as well as the Tableau+ Bundle.

For procurement teams, the useful comparison is no longer simply “agent seat versus human seat.” It is the fixed Creator and Explorer base plus the block size required for viewers and machine consumers. Seasonal usage, customer-facing embedded analytics and background agent jobs can now draw from the same capacity construct.

The missing number is still the important one

Tableau has not posted a public price for Viewer Blocks. Its pricing page directs buyers to contact sales for capacity terms. It also lists starting per-user prices of $15 a month for Tableau Standard and $35 a month for Tableau Enterprise, billed annually, but those figures do not reveal the price, unit size or practical throughput of a Viewer Block.

Before treating the change as a predictable agent budget, buyers should request the block definition, measurement window, included machine activity and any throttling or fair-use rules in the contract. “No overage charges” removes one surprise, but it does not by itself show whether a block fits an interactive dashboard audience, a high-frequency agent workload, or both.

The launch is still a meaningful packaging shift: Tableau is acknowledging that analytics consumers now include software agents that do not map cleanly to named-user licensing. The cost case, however, remains impossible to calculate from the public tariff alone.

Filed by The News 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.