Tableau's per-user math
doesn't survive ISV embedding.
Tableau is the enterprise analytics standard — and Salesforce-owned since 2019. For ISVs, the structural problem is the licensing model: per-user. Even Viewer at $15/user/month becomes roughly $180,000/year for 1,000 customer end-users. The dedicated Embedded Analytics license is a separate, custom-priced Cloud-only product. Yurbi publishes annual pricing from $10,000/year with a $30,000/year ceiling at the Unlimited tier — no per-user fee.
- 100 viewers $18,000/yr $18,000/yr
- 500 viewers $90,000/yr $24,000/yr
- 1,000 viewers $180,000/yr $30,000/yr
- 5,000 viewers $900,000/yr $30,000/yr
Four things ISVs need to know before embedding Tableau
These aren't reasons to automatically rule it out. They're the questions worth asking with clear answers before committing to a customer-facing embed.
Per-user pricing makes your cost a function of your customers' size
Tableau's published rates are per user, billed monthly. For an ISV embedding Tableau in a customer-facing product, your "user count" is the sum of every end-user across every customer. At 1,000 end-users on Viewer Standard ($15/user/month), list-rate licensing is around $180,000/year. At 5,000 end-users it is roughly $900,000. The cost scales with your customers' adoption — not your revenue per customer. That structurally compresses gross margin as you grow.
The Embedded Analytics license is custom-priced and Cloud-only
Tableau offers a dedicated Embedded Analytics license — a limited-use Tableau Cloud license billed in analytical impressions (one impression per dashboard load, worksheet load, export, subscription, or Pulse insight). Pricing is custom-quoted; there is no published number. The license cannot coexist with full-use licenses in the same environment, and it requires Tableau Cloud — not Server. ISVs needing self-hosted, on-premise, or air-gapped deployment cannot use this license.
Salesforce-owned roadmap targets a different customer profile
Salesforce acquired Tableau in 2019 for $15.7 billion. Since then, Tableau's roadmap and integrations have aligned with Salesforce's broader strategy — bundling with Salesforce editions, integration with Einstein AI, deeper Data Cloud connections, the Tableau+ AI bundle, and the new Tableau Next "agentic analytics" tier. For ISVs whose product is unrelated to the Salesforce ecosystem, this means roadmap priorities and feature investment increasingly target enterprise CRM customers, not embedded analytics partners.
Designed for internal BI, then extended to embedding
Tableau's foundation is internal enterprise BI — analysts authoring dashboards for their own organization. Embedded Analytics extends that engine to external customers, but the architecture, pricing, and licensing all reflect the internal-BI origin: Creator-led authoring workflows, per-user accounting, and Cloud-first delivery. Yurbi was built from day one for ISVs embedding analytics in a product they sell — multi-tenant isolation, dynamic per-tenant data source routing, and per-tenant white-label branding are platform features, not configuration patterns.
Tableau Embedded vs Yurbi — for ISVs embedding analytics
Tableau pricing sourced from tableau.com/pricing as of publication. Embedded Analytics license is custom-priced — verify with Tableau before budgeting. Yurbi pricing is published here.
Which one is actually right for your product?
We're not going to claim Yurbi wins every use case. Here is a direct read on when each platform is genuinely the better fit.
Choose Tableau if:
- Your product lives in the Salesforce ecosystem — your customers already use Tableau or CRM Analytics, and Salesforce is part of the integration story
- Your customer end-user count is small and well-bounded — embedded analytics is for a few power users per customer, not the entire customer base
- Tableau's visualization breadth, AI features (Pulse, Einstein, Tableau Next), and analyst community are genuine product requirements — not nice-to-haves
- Your budget is enterprise-level and your customers do not require self-hosted, on-premise, or air-gapped deployment
Choose Yurbi if:
- Your customer end-user count is large or growing — and you need analytics cost to be decoupled from that count
- You want a published, predictable annual price you can model into your unit economics — without a sales call
- Your customers require self-hosted deployment — their data stays in their infrastructure, full stop
- You need multi-tenant isolation, dynamic per-tenant data source routing, and unlimited per-tenant branding without per-tenant licensing
- You'd rather evaluate before committing — download the trial, connect your database, and have a working embed in days
Tableau Embedded vs Yurbi — questions answered directly
Tableau publishes per-user pricing for Tableau Cloud — Viewer at $15/user/month, Explorer at $42/user/month, and Creator at $75/user/month on the Standard tier (Enterprise tier rates are higher: $35, $70, and $115 respectively). Every deployment requires at least one Creator license. The dedicated Tableau Embedded Analytics license is a separate Cloud-only product billed in analytical impressions, and pricing is custom-quoted — no published number.
For an ISV with 1,000 customer end-users on Viewer Standard, list-rate licensing reaches roughly $180,000/year before counting the required Creator seat, infrastructure, the Embedded Analytics license itself, or implementation. Yurbi publishes annual pricing from $10,000/year with a $30,000/year ceiling at the Unlimited tier — no per-user fee.
Tableau Embedded Analytics is a limited-use license for Tableau Cloud — designed specifically for delivering Tableau content to users outside your organization. It uses usage-based licensing measured in analytical impressions: each dashboard load, worksheet load, export (image, PDF, PowerPoint, workbook), subscription, or Pulse insight request counts as one impression.
Two practical constraints follow. First, the Embedded Analytics license cannot coexist with full-use licenses in the same Tableau environment — an organization that uses Tableau internally and wants to embed externally must run two separate environments. Second, the license is Cloud-only: it does not apply to Tableau Server. ISVs whose customers require self-hosted deployment cannot use this license.
The Tableau Embedded Analytics license is exclusive to Tableau Cloud — Salesforce's hosted environment. Tableau Server can run self-hosted on Windows or Linux with role-based or core-based licensing, but the dedicated Embedded Analytics usage-based license is not available on Server. Building a Server deployment for embedded use means purchasing per-user role-based licenses for every end-user, which is the same per-user math that drives the cost issue.
For ISVs whose customers require data residency, on-premise deployment, or air-gapped infrastructure — common in regulated industries, government, and large-enterprise procurement — Tableau Embedded Analytics on Cloud cannot meet those requirements. Yurbi is self-hosted by design: Windows Server, Linux, or Docker on your own infrastructure, with no required outbound connections.
Salesforce acquired Tableau in 2019 for $15.7 billion. Since then, Tableau's roadmap, pricing, and integrations have aligned with Salesforce's broader strategy. Tableau is increasingly bundled with Salesforce editions, integrated with Einstein AI and Data Cloud, and positioned through CRM Analytics. The Tableau+ AI bundle and the new Tableau Next agentic-analytics tier reinforce the direction toward Salesforce ecosystem customers.
For ISVs whose product is unrelated to Salesforce, this means roadmap priorities and feature investment increasingly target enterprise CRM customers rather than embedded analytics partners. That isn't a problem if you're embedding for Salesforce-adjacent customers; it's worth understanding if you're not. Yurbi is independent — bootstrapped, no parent vendor, no platform alignment that may shift with corporate strategy.
Per-user pricing was designed for internal BI — a known internal employee count. For ISVs embedding analytics in a customer-facing product, the user count is the sum of every end-user across every customer, and it grows as your product grows.
At 1,000 customer end-users on Viewer Standard pricing ($15/user/month), the annual Tableau license bill is around $180,000. At 5,000 end-users it is roughly $900,000. The cost grows with your customers' adoption, not with your revenue per customer. That structurally compresses gross margin as you scale — and it's a cost line you cannot pass through cleanly without restructuring your own pricing.
Yurbi's pricing tiers by named user count up to a $30,000/year ceiling at the Unlimited tier — every user role (viewer, builder, architect, admin) consumes a named user license. The structural difference: Tableau has no upper bound on per-user cost as you scale; Yurbi caps at $30,000/year regardless of whether you have 500 end-users or 50,000.
Tableau has a deeper visualization library, native Salesforce ecosystem integration, AI features through Pulse and Einstein, the new Tableau Next agentic tier, and a far larger community of analysts and consultants. Those are real differentiators if your use case requires them.
Yurbi is purpose-built for embedded analytics in ISV products: 20+ chart types, multi-tenant security at the platform level, dynamic data source routing per tenant, unlimited per-tenant branding policies, and FastCache for performance. Yurbi has no AI or natural-language analytics features yet (on roadmap, deliberately built on the semantic layer for safe multi-tenant query generation). Embedding is iframe and API only — no JS SDK. SSO uses session tokens via the DoLogin API rather than SAML or OIDC. Dashboard interactivity is parameter-driven rather than associative click-through.
If those gaps are blockers, Tableau is the better fit and we'll tell you in a demo.
Download the Yurbi trial today. Connect to your database. Configure tenant structure. You can have a working embedded dashboard inside your product within days. Full production deployment — your branding, your SSO configuration, your customer data — is typically 2 to 6 weeks depending on data architecture.
The Tableau Embedded Analytics path begins with a sales conversation to scope the Embedded Analytics license, pricing, and impression volume. Implementation engagement is typically required for embedding patterns and SSO. If you are starting fresh on Tableau Cloud rather than migrating from an existing Tableau Server deployment, you also build the report library from scratch in Tableau before you can embed it. Starting with "download trial" versus "contact sales" is a measurable difference in time to a working analytics feature.