Tableau Embedded Pricing 2026: Cloud+, Next + Alternatives

By Vishnupriya B, Data Analyst at Databrain. Data Analyst specializing in data visualization, SQL, Python, and data modeling.

Published August 15, 2025 · Updated May 20, 2026 (post-TC 2026 + 4-edition Cloud restructure + Tableau Next published-pricing refresh) · For: SaaS PMs, engineers, and CTOs evaluating Tableau Embedded / Tableau Next pricing.

2026-05-20 refresh - material pricing-structure changes since the prior version of this page. Per the live Tableau pricing page verified 2026-05-20, Tableau has restructured Tableau Cloud into four editions (Standard, Enterprise, Cloud+, Tableau+ Bundle) - Enterprise + Cloud+ are new tier names since our last refresh. Tableau Next now has published per-user pricing at $40/user/month (Creator), explicitly moved from consumption-based Flex credits to role-based per-seat licensing. Tableau Agent is GA in the new Cloud+ Edition. The Tableau+ Bundle (Cloud+ + Tableau Next combined) includes 250K Data Cloud Credits. All of this is layered on top of the broader Agentic Analytics Platform reframe Tableau announced at Tableau Conference 2026 on May 6, 2026. The page below is rewritten against the live-verified pricing structure.

At a Glance

Tableau Embedded prices through three paths in 2026: (1) the new 4-edition Tableau Cloud structure - Standard ($15/$42/$75), Enterprise ($35/$70/$115), Cloud+ (contact sales - Tableau Agent included), and the Tableau+ Bundle (Cloud+ + Tableau Next combined); (2) Tableau Next standalone at a newly published $40/user/month Creator tier - role-based, no more Flex credits; (3) a custom-quoted legacy Embedded Analytics OEM SKU for SaaS teams embedding Tableau inside their own product.

What Tableau Costs (the public posture, 2026 edition)

Tableau's official Tableau Cloud pricing page now publishes prices across four editions and a separate Tableau Next standalone line. The structure verified 2026-05-20:

Tableau Cloud - 4 editions

All Cloud editions require at least one Creator license. Pricing is billed annually. Source: <https://www.tableau.com/pricing/teams-orgs>.

The newest tier in this lineup is Cloud+ Edition - explicitly the agentic-enabled tier. This is the SKU that gates Tableau Agent for Cloud customers in 2026. Standard and Enterprise editions don't include Tableau Agent for Cloud users (Tableau Agent in Tableau Server is a separate gate that requires customers to provide their own LLM, currently OpenAI-only).

Tableau Next - standalone, now with published per-user pricing

This is the biggest pricing-structure change since 2025:

Per the Tableau Next pricing FAQ verified 2026-05-20: "Tableau Next pricing is now Role-based, eliminating consumption-based pricing (like Flex credits) for data queries, data transforms, and agentic analytics. Data storage in Data 360 and other costs may still apply."

Tableau Next standalone now publishes its Creator rate ($40/user/month). For SaaS teams that previously couldn't get a Tableau Next quote without committing to the full Salesforce stack, this is a meaningful procurement-velocity change.

Tableau Server - the same 2-edition structure (Standard + Enterprise) for self-hosted

For teams that need self-hosted deployment (regulated industries, sovereign-cloud, air-gapped), Tableau Server publishes the same per-seat list as Standard / Enterprise Cloud editions (Viewer $15/$35, Explorer $42/$70, Creator $75/$115) plus a core-based licensing option (contact sales). Cloud+ and Tableau+ Bundle are not available for self-hosted Server deployments per the live pricing page.

What's still not on the public price list - Tableau OEM Embedded

Tableau OEM Embedded Analytics - the SKU you actually need if you're embedding Tableau inside your own SaaS product (as opposed to standing up Tableau Cloud for your internal team) - remains custom-quoted off the public price list. Tableau OEM Embedded deals are typically structured as one of three models:

1. Per-end-user pricing - a heavily discounted per-seat rate for the customers of the SaaS that's embedding Tableau. Discounts off public Viewer pricing of 50–80% are typical, scaling with volume.
2. Capacity-based pricing - a flat annual fee tied to a usage envelope (concurrent users, data volume, query throughput). More common for high-volume embedded deployments.
3. Revenue-share - Tableau takes a percentage of the SaaS's revenue from the analytics-enabled tier. Less common, used in specific partnership structures.

The OEM embedded deal floor in 2026, for SaaS teams reading this guide, sits between $60K and $150K in year-one fees - not including services, not including infrastructure, not including any Data 360 / Salesforce-prerequisite licensing if Tableau Next or Tableau Semantics is in the conversation. This is the SKU that unlocks the Tableau Embedding API v3 <tableau-viz> web component + Connected Apps JWT auth.

The Agentic Analytics Platform - What's Included, What's Extra in 2026

At Tableau Conference 2026 (TC 2026) on May 6, 2026, Salesforce reframed the entire Tableau portfolio as the Agentic Analytics Platform - a single umbrella spanning Tableau Cloud, Tableau Next, Data 360, and a new set of agentic primitives. The TC 2026 keynote introduced four net-new components on top of Tableau Agent: MCP Voice (voice-driven analytics queries via Model Context Protocol), the Agentic Analytics Command Center (operator console for agent observability), Agent Actions (write-back actions agents can take in source systems), and a refresh of the Auto Knowledge Graph + Tableau Semantics on Data 360.

For pricing, the post-TC-2026 Agentic Analytics Platform has four implications worth budgeting against.

1. Tableau Agent for Cloud users requires Cloud+ Edition

The single sharpest cost-of-ownership shift in 2026: Tableau Agent is no longer a Pilot capability. It is GA in the new Cloud+ Edition for Tableau Cloud customers (in Desktop, Web Authoring, Catalog, Prep, and Pulse). Standard and Enterprise editions do not include it. For Tableau Server customers, Tableau Agent runs against a customer-provided LLM (currently OpenAI-only, per the live pricing FAQ) - the customer manages the LLM's security.

If your roadmap includes "every analyst gets a Tableau Agent surface," budget for the Cloud+ jump - and treat Premier Success + 50-site capacity as bundled features of that tier, not separate negotiations.

2. Tableau Next standalone is now Role-based, not consumption-based

The largest 2026 pricing-structure change: Tableau Next moved off Flex credits. Per the live FAQ, "Tableau Next pricing is now Role-based, eliminating consumption-based pricing (like Flex credits) for data queries, data transforms, and agentic analytics." Creator is $40/user/month standalone, billed annually. Consumer is contact-sales.

For SaaS teams previously locked out of Tableau Next quotes because the Flex credit math was opaque, this is a meaningful procurement-velocity change. The trade-off: Data 360 storage costs and other line items can still apply on top - Role-based pricing eliminates query/transform/agentic credits, not the underlying Data 360 storage SKU.

3. The Tableau+ Bundle (Cloud+ + Tableau Next) includes 250K Data Cloud Credits

Per the live pricing page, the new Tableau+ Bundle combines Cloud+ Edition with Tableau Next and ships with 250K Data Cloud Credits as a starter. For most SaaS teams reading this guide, 250K credits is sufficient for proof-of-concept and early-tenant deployments; production-scale SaaS deployments at 1,000+ customer tenants typically hit the credit ceiling and re-quote. The credit usage is trackable in Digital Wallet.

4. The OEM Embedded SKU is still the right answer for "embed Tableau inside our SaaS product UI"

Tableau Next is built around Salesforce-hosted experiences (Agentforce skills, Slack, Tableau Next surfaces). For SaaS teams embedding Tableau dashboards inside their own product UI (not a Salesforce-hosted surface), the legacy OEM Embedded SKU with Embedding API v3 + Connected Apps JWT remains the right SKU - custom-quoted, ~$60K–$150K year-1 floor. Tableau Next's standalone $40/user/month rate is published, but it's priced per Salesforce user and assumes Salesforce-hosted consumption surfaces, not white-labelled SaaS embed.

The Hidden Costs

Five hidden costs land hardest in the first 12 months of a Tableau Embedded deployment.

1. Implementation services

Tableau Embedded deployments almost always include an implementation services package - either from Tableau directly or from a tier-1 partner (Slalom, Aimpoint Digital, InterWorks, or Salesforce's professional services arm). Typical scope: $40K–$120K for a first deployment, depending on data complexity, embedded surface count, and any Data 360 / Tableau Semantics integration.

2. Tableau Server infrastructure (if self-hosted)

If your embedded use case requires self-hosted Tableau Server (typical for regulated industries or air-gapped deployments), the infrastructure footprint is non-trivial - typically 2–4 sized EC2 instances or equivalent, plus VizQL Server scaling, plus the Tableau Server license itself. Note that Cloud+ and Tableau+ Bundle editions are Cloud-only per the live pricing page - Server deployments are capped at Standard + Enterprise editions, so the agentic Cloud+ feature set isn't available on self-hosted Server in 2026.

3. Data 360 storage + Tableau Semantics (if Tableau Next or Tableau Semantics is in scope)

The post-2026 reframe matters here: Tableau Next's role-based per-user pricing eliminated Flex credits for queries / transforms / agentic analytics, but Data 360 storage still applies. For SaaS teams provisioning Tableau Semantics on Data 360 (Auto Knowledge Graph + Semantic Modeling with AI), the Data 360 storage SKU is the line item that surprises buyers - it's metered separately from the $40/user/month Tableau Next license. Track consumption in Digital Wallet from day one to avoid mid-year re-quotes.

4. Embedded SDK customization

Tableau's Embedding API v3 (the <tableau-viz> web component) and the underlying JavaScript API for embedding dashboards work, but they have constraints. Typical customizations - custom auth flow, deep linking, programmatic dashboard interactions, white-label theming beyond logo + color - require engineering effort. Most embedded deployments include 100–300 hours of custom development on top of the SDK. Note also that Tableau Next has its own non-interchangeable SDK (@salesforce/analytics-embedding-sdk) on a separate auth model - embedding Tableau Next dashboards in a SaaS product is a different developer-experience surface from embedding Tableau Cloud dashboards.

5. Annual uplift

Tableau renewals typically include a 7–12% annual uplift, negotiable depending on deal structure and multi-year commitment. Multi-year deals lock the uplift but lock the seat count too - adding mid-term capacity often involves a re-quote, particularly across the new Cloud+ / Tableau+ Bundle boundary if your team graduates into agentic capabilities mid-contract.

TCO at 10 / 100 / 1,000 Users (Year 1, Year 3) - reframed for the 4-edition structure

Three caveats. First, OEM Tableau Embedded for SaaS deployments is custom-quoted - figures below are directional benchmarks reconstructed from public reports and customer conversations during 2025–2026, not a price book. Second, "users" in an embedded SaaS context means the customers of the SaaS - not internal employees. Third, the rows below now distinguish Cloud edition (Standard / Enterprise / Cloud+) from Tableau Next add-on explicitly, because the 2026 pricing-structure restructure made these two separately purchaseable.

Assumptions: US-only deployment, mid-range data volumes, single staging + production, no air-gapped/regulated requirements. Multi-region or sovereign-cloud deployments add 20–40%. The 10,000-end-user row is where most Series-B SaaS reading this guide will land.

The post-2026 framing change worth flagging: a SaaS team that previously needed to commit to the full Salesforce data + agent stack to access any Tableau Next capability can now buy Tableau Next standalone at $40/user/month Creator. For 10–50 internal analysts, this is a $20K–$50K Year-1 line item - not the $300K+ Salesforce-bundle minimum the prior version of this page assumed. The Data 360 storage cost is still real but is metered separately, and the 250K Data Cloud Credits in the Tableau+ Bundle absorbs early-deployment usage.

The column to compare against developer-first embedded analytics platforms with transparent per-tenant or per-deployment pricing: typically 30–50% of the Tableau OEM Embedded year-1 TCO for the equivalent footprint, with white-label, multi-tenant, and MCP capability included by default rather than gated to Cloud+ / Tableau+ Bundle.

5 Best Tableau Embedded Alternatives in 2026

1. DataBrain - developer-first embedded analytics with published pricing

DataBrain is purpose-built for SaaS teams embedding analytics in their own product. The default footprint includes multi-tenant data isolation, row-level security, white-label theming, an SDK for React / Angular / Vue / vanilla JS, and published pricing.

• Best for: SaaS teams whose customers consume analytics inside the SaaS product, especially when buyers want predictable pricing without a procurement cycle that starts with Salesforce Data Cloud.
• Tableau-vs-DataBrain on the axes that matter: white-label is included not customized; multi-tenant is the default not an enterprise tier; pricing is published; the SDK posture is component-first not iframe-first.
• Where Tableau still wins: if your buyers want the Tableau brand in their own brand stack, or if you're already deep in the Salesforce ecosystem and Tableau Next is part of your AI roadmap.

2. Sisense Compose SDK - developer-track BI

Sisense's Compose SDK is the developer-facing track of the Sisense platform. Closer to what most SaaS PMs need than Sisense Fusion, but the pricing posture is still custom-quote - see Sisense pricing for the breakdown.

• Best for: teams that want a developer toolkit but also want enterprise BI capabilities for their internal analyst team in the same vendor.
• Where it wins vs Tableau: developer-first surface; component-based embedding.
• Where it falls short: custom-quote pricing introduces the same procurement friction Tableau has.

3. Power BI Embedded - Microsoft-bundle predictability

If your SaaS already lives in the Microsoft cloud (Azure, Fabric, Synapse), Power BI Embedded gives you bundle economics on Azure capacity and Microsoft-published pricing. Per the Azure-published per-capacity model, the SKUs are predictable and scale linearly.

• Best for: teams whose data already lives in Microsoft cloud and whose buyers want Microsoft procurement.
• Where it wins vs Tableau: published per-capacity pricing; tighter Microsoft-cloud bundle economics.
• Where it falls short: iframe-centric embedding model; component-level customization is harder than DataBrain or Embeddable.

4. Embeddable - component-driven embedded

Embeddable focuses on developer-friendly embedding with React / Vue components and transparent pricing. Built for the embedded use case from the ground up, no internal-BI platform legacy.

• Best for: product teams that want to assemble custom dashboard layouts component-by-component inside their own UI shell.
• Where Tableau still wins: mature governance, role-based admin tooling for buyers who want a finished platform with deep visual customization and an analyst-facing authoring experience.

5. ThoughtSpot Embedded - search-first analytics with conversational AI

ThoughtSpot Embedded leans into conversational analytics - search-driven exploration, Spotter and Sage agentic capabilities, and SearchIQ as the primary user interface. Different center of gravity than Tableau's chart-first approach.

• Best for: SaaS products whose end-users are non-technical and prefer asking questions over building dashboards.
• Where Tableau still wins: the Tableau community, breadth of visualization types, and analyst tooling are deeper.

Who Tableau Embedded Is For - and Who It's Not For

Tableau Embedded is a strong fit if

• Your SaaS sells into the Salesforce ecosystem and your buyers expect Tableau in the analytics layer.
• You have meaningful budget ($150K+/year for the embedded use case) and the procurement maturity to negotiate OEM terms.
• Tableau Next + Agentforce + Data Cloud is part of your 12–24 month AI roadmap.
• Your end-users are analyst-shaped - they want rich visual customization, calculated fields, and the analyst-grade authoring experience.

Tableau Embedded is the wrong tool if

• You're a Series A SaaS team that needs to embed analytics in 6–12 weeks. The OEM negotiation cycle alone often eats the timeline.
• Multi-tenant + white-label are non-negotiables and you don't want to scope them as customizations.
• Pricing transparency matters to your team's procurement model.
• Your buyer is a PM/engineer at a non-Salesforce SaaS - the Salesforce-bundle gravity is real and gets stronger every quarter.

How Tableau Compares on 2026 AI Capability

Tableau's 2026 AI story has five pillars: Tableau Pulse (proactive insights and metric monitoring), Tableau Agent (GA in Cloud+ Edition since TC 2026, including the agentic skills Concierge / Data Pro / Inspector), Tableau Next (agentic analytics platform with native Slack integration), Tableau Semantics (Auto Knowledge Graph + Semantic Modeling with AI on Data 360), and the open-source @tableau/mcp-server for MCP-client integration.

How that compares to peers in the embedded-analytics MCP race as of May 2026:

• GoodData (now GoodData.AI after the April 30, 2026 rebrand) ships the MCP Server (27 tools, including 3 Knowledge Tools) plus the Agent Builder multi-agent platform with five config surfaces and A2A protocol support. The most aggressive MCP+agentic positioning in the embedded-analytics category as of mid-2026. If MCP-protocol-native agentic workflows are a hard evaluation requirement, GoodData.AI is the most mature.
• DataBrain ships an MCP-compatible server (/api/mcp in the same Express app as the embedded analytics product) that lets analytics queries flow through Claude, ChatGPT, and custom agentic workflows without requiring a Data 360 prerequisite or a separate process per operator. Same auth, same RLS, same semantic layer as the embedded dashboards.
• Sisense launched @sisense/mcp-server (v0.4.1, April 30, 2026) - among the early MCP Apps protocol implementations alongside the Compose AI tier and the Notebook agent.
• Power BI has the Microsoft Fabric Copilot stack plus remote + local Power BI MCP server previews - bundled with the Microsoft AI tier.
• Looker is now anchored on Conversational Analytics + Gemini-in-Looker integrated through Vertex AI, with the Google Cloud agentic stack.
• ThoughtSpot has Spotter + Sage as its agentic positioning - search-first conversational UX, different shape from Tableau's chart-first agentic surface.

The Tableau-specific differentiation in 2026 is the Tableau Semantics + Auto Knowledge Graph pairing on Data 360 - that's the architectural bet that Tableau Next's agentic skills will be more trustworthy than competitor agents because the semantic layer is auto-generated against the underlying data. Whether this proves out depends on Auto Knowledge Graph maturity in production deployments.

For a deeper evaluation across the AI dimension, best AI-first embedded analytics 2026 compares all the AI-first vendors on agentic, MCP, semantic-layer, and CLI axes.

What You're Actually Buying at the API Level

Tableau pricing tiers map onto specific developer surfaces. Knowing which API contract each SKU unlocks - and which prerequisites the agentic Tableau Next path inherits from Salesforce - is the difference between a $60K Embedded subscription and a multi-six-figure Data 360 + Agentforce procurement.

Legacy Tableau Embedded SKU → Embedding API v3 + Connected Apps

The OEM Embedded SKU (per-end-user / capacity / revenue-share) unlocks the Tableau Embedding API v3 - a web-component-first JavaScript library shipped as tableau.embedding.3.n.n.min.js or installed via the @tableau/embedding-api npm package. The host app drops a <tableau-viz> custom element that mounts an iframe internally:

<!-- from https://help.tableau.com/current/api/embedding_api/en-us/index.html -->
<script type="module"
  src="https://public.tableau.com/javascripts/api/tableau.embedding.3.latest.min.js"></script>

<tableau-viz id="tableauViz"
  src="https://my-server/views/my-workbook/my-view"
  device="phone" toolbar="bottom" hide-tabs>
</tableau-viz>

React, Angular, and Vue hosts use thin wrappers over the same custom element - there is no first-party framework-native SDK shipped by Tableau. Tableau Next's @salesforce/analytics-embedding-sdk is a separate, non-interchangeable package on a separate auth model.

Connected Apps JWT auth → a freshly minted token on every view load

Every Embedding API v3 call requires a JWT signed with a Connected App secret created in Tableau. Per the Tableau auth doc, the JWT carries registered claims (iss, exp, jti, aud="tableau", sub, and a scp like tableau:views:embed), is signed HS256 with the connected-app secret, and is passed as the token attribute on the embedded viz:

<!-- from https://help.tableau.com/current/api/embedding_api/en-us/docs/embedding_api_auth.html -->
<tableau-viz id="tableauViz"
  src="https://your-tableau-server/views/my-workbook/my-view"
  token="JWT generated from connected app secrets">
</tableau-viz>

The same doc states explicitly: "you must generate a JWT dynamically for each enabled user. Never embed the credentials for one user in your connected app and then use that as authorization for others." So the embedding tier price also obligates you to build, deploy, and rotate secrets for a per-user-per-load JWT-issuance microservice. Browsers must also allow third-party cookies for the iframe session, and sign-out requires an extra POST /api/{version}/auth/signout REST call plus an iframe reload to clear the HttpOnly Tableau cookie.

Tableau Pulse vs interactive viz - the runtime theming gap

The Embedded SKU does not ship a runtime CSS theming primitive for interactive dashboards. Per the Tableau Pulse theme doc, only <tableau-pulse> supports <theme-parameter> children for fonts, backgrounds, foregrounds, and per-chart-element colors:

<!-- from https://help.tableau.com/current/api/embedding_api/en-us/docs/embedding_api_pulse_theme.html -->
<tableau-pulse id="tableauPulse"
    src="<Your_Tableau_Pulse_URL>"
    layout="default">
    <theme-parameter name="fontCssUrl"
      value="https://fonts.googleapis.com/css2?family=Bebas+Neue&display=swap"></theme-parameter>
    <theme-parameter name="backgroundColor" value="#fef"></theme-parameter>
    <theme-parameter name="foregroundColor" value="#808"></theme-parameter>
    <theme-parameter type="chart" name="bar" value="#808"></theme-parameter>
</tableau-pulse>

Interactive <tableau-viz> dashboards rely on workbook-baked styling - per-customer brand colors require either duplicating workbooks via the Document API or accepting a single brand across all tenants. For a multi-tenant SaaS embedding a Tableau dashboard with per-customer logos and palettes, this is a structural constraint, not a configuration option.

Tableau Next + Salesforce Data 360 - the agentic prerequisite stack

The Tableau Next "Analytics and Visualization Agent" - Salesforce's flagship agentic-analytics component - is gated on a multi-product Salesforce stack. Per the Salesforce SDK doc for the agent component, shipping it requires a Salesforce External Client App for OAuth, Data 360 (formerly Data Cloud) provisioned, Einstein Generative AI enabled, Agentforce enabled, and at least one Agentforce agent configured, on top of a Tableau+ or Tableau Next Creator license:

// from https://developer.salesforce.com/docs/analytics/sdk/guide/sdk-integration-embed-agent.html
// (Embed the Analytics and Visualization Agent - Pilot)
// Requires: Tableau+ or Tableau Next Creator license, Tableau Next enabled,
//           Data 360 (formerly Data Cloud) provisioned, Einstein Generative AI on,
//           Agentforce enabled, at least one Agentforce agent configured.
import { initializeAnalyticsSdk, AnalyticsDashboard } from '@salesforce/analytics-embedding-sdk.js';
await initializeAnalyticsSdk({
  authCredential: 'AUTH_CREDENTIAL',
  orgUrl: 'https://my-domain.lightning.force.com',
});

None of those prerequisites is a Tableau-only line item - every one is a Salesforce SKU with its own minimums, and every end viewer must exist as a Salesforce user with the right permission sets. The "Tableau Next pricing" conversation is really a "Salesforce Customer 360 pricing" conversation.

Tableau MCP - open source, local-only, PAT-authenticated (and seeing real adoption post-TC 2026)

The single Tableau-published MCP server, @tableau/mcp-server (v2.2.4, Apache-2.0 TypeScript, May 2026), runs locally against a Tableau site URL + Personal Access Token. It wraps the VizQL Data Service, Metadata API, and REST API for MCP clients such as Claude Desktop, Cursor, and VS Code:

# from https://github.com/tableau/tableau-mcp
# Run via npm (Node 22.7.5+ required); configured via env vars pointing at
# a Tableau Server / Cloud site URL, site name, and a PAT.
npx @tableau/mcp-server

It is not a hosted MCP control plane and does not ship with the Embedded SKU - every operator runs their own server with their own PAT, and the agent on the other end consumes whatever scope the PAT happens to carry. However, adoption since TC 2026 has been real: per the GitHub repo and npm registry as of 2026-05-18, the package is at ~9.7K weekly downloads, ~271 GitHub stars, and grew roughly +73% in 12 days following the May 6, 2026 TC keynote - a sharper adoption curve than most embedded-analytics-vendor MCP servers in 2026. The pricing implication: MCP capability arrives at zero incremental cost for buyers who already have a Tableau Cloud or Server license + a PAT. The downside is the operator-per-deployment model and the PAT scope inheritance - neither is a hosted-control-plane equivalent of what DataBrain or GoodData ship.

What DataBrain ships at the same architectural seams

Where Tableau gates each capability behind a separate SKU, a separate auth model, or a Salesforce prerequisite, DataBrain ships them as defaults of one product:

• One embed surface for every framework. The same React component is wrapped into a Shadow-DOM Web Component (<dbn-dashboard>) via @r2wc/react-to-web-component, so React, Angular, Vue, vanilla JS, Webflow, and server-rendered hosts use the same auth and same props - no <tableau-viz>-vs-@salesforce/analytics-embedding-sdk decision and no React-wrapper-over-web-component indirection.

frontend-mono/packages/@databrainhq/plugin/src/webcomponents.ts (lines 22–60)

const DbnDashboard = r2wc(Dashboard, {
  props: {
    token: 'string',
    dashboardId: 'string',
    options: 'json',
    theme: 'json',
    isHideChartSettings: 'boolean',
    isHideTablePreview: 'boolean',
    isStickyDashboardFilters: 'boolean',
    enableDownloadCsv: 'boolean',
    enableEmailCsv: 'boolean',
    disableDownloadPng: 'boolean',
    enableDownloadAllMetrics: 'boolean',
    enableDownloadAllPdf: 'boolean',
    enableMultiMetricFilters: 'boolean',
    disableFullscreen: 'boolean',
    enableTitleClickFullscreen: 'boolean',
    // ... more props ...
    chartClickFunction: 'function',
  },
  shadow: 'open',
});

• One auth model, no per-load JWT signing. The host calls POST /api/v1/guest-token/create (or v2) once per session; the server validates the tenant against the actual data source before minting an opaque, revocable token - no per-user-per-load JWT issuance microservice to deploy and rotate secrets for, no third-party-cookie sign-out dance.

backend/serverless/express/src/externalApis/guestToken.ts (lines 67–207)

const isClientExists = async (
  workspaceId: string,
  clientId: string,
  datasourceId?: string,
) => {
  try {
    // ... resolves the data source + tenant column ...
    const query = `select ${getConvertedColumn(...)} from ${tableNameString} WHERE ${getConvertedColumn(...)} = '${clientId}' LIMIT 1`;
    const { data } = await executeSqlQuery({ id: ..., query, workspaceId, databaseName: '' });
    if (data?.length === 0) return false;
    return true;
  } catch (error) {
    return false;
  }
};

• Theming is a runtime JSON prop on every dashboard. Per-tenant white-label switches with a single prop change - no Pulse-only <theme-parameter> API and no Document-API-cloned workbooks per brand for interactive viz.

frontend-mono/packages/@databrainhq/plugin/src/utils/theme.ts (lines 134–159)

export const applyTheme = (theme: ThemeType): void => {
  const root = document.documentElement;
  // ... walks the theme JSON and sets CSS custom properties on :root ...
  if (theme?.button)
    Object.entries(theme.button).forEach(([key, value]) => {
      if (key && value) root.style.setProperty(`--dbn-btn-${key}`, `${value}`);
    });
};

• MCP is a control plane in the same Express app. The MCP router shares the same service-token, rate-limiter, and RBAC plumbing as the rest of the product - no Salesforce-prerequisite agent stack and no separate-process local MCP server that has to be hand-deployed per operator.

backend/serverless/express/src/index.ts (lines 147–155)

app.use(
  '/api/mcp',
  isPrivateApp([]),
  MCPRateLimiter,
  resolveOperatorEmail,
  MCPRouter,
);

• Pricing is published. Per-tenant + per-deployment rates on the pricing page - no three-OEM-model custom-quote conversation, no separate Salesforce Data 360 minimums for the agentic path.

Where to go next

If you want to see what a published-price, embed-first alternative looks like end-to-end, DataBrain vs Tableau is the head-to-head on multi-tenancy, white-label, AI, and pricing. The Tableau alternatives shortlist compares the full set of 7 alternatives for SaaS. If your decision is between Tableau Embedded and Power BI Embedded specifically, Tableau Embedded vs Power BI Embedded is the head-to-head between the two BI-classic embedded SKUs.

Comparing pricing across the broader category? GoodData.AI pricing is the companion 2026 breakdown for the agentic AI-native peer (Sisense pricing is covered above for the developer-SDK peer).

For a strategic AI-first look at the embedded analytics market in 2026, the 2026 AI-first vendor buyer's guide is the companion to this pricing-focused page.

Builder reader (SaaS PM / engineer)

If your job is to ship customer-facing analytics inside your SaaS product in the next quarter, the procurement reality with Tableau Embedded is typically a 6–12 week negotiation cycle followed by a multi-month implementation. That timeline often disqualifies Tableau before the technical evaluation begins.

→ See how DataBrain embeds analytics in your product - multi-tenant, white-label, MCP-ready, with published pricing and 2–6 week deployment.

Analyst reader (BI / data team buyer)

If you're shortlisting analytics platforms for a mixed internal-BI-plus-embedded use case and you have the procurement runway, Tableau Cloud + Tableau Embedded is a credible candidate. The hidden-cost playbook in this article - services, infrastructure, Data Cloud prerequisites, customization, uplift - is the punch list for your sales conversations.

→ Explore live sample dashboards to see what a published-price embedded experience looks like before your next vendor call.