Analytics and monitoring decision
LaDataViz
A small team or experienced developer can reproduce a narrow subset (one extension + Figma exporter) and self-host it, but reproducing the full polished multi-chart product, Tableau-reviewed distribution, and managed hosted billing is larger work and includes nontrivial support and trust benefits.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
What a replacement has to do
- Provide self-hosted Tableau viz extension(s) that render custom charts inside Tableau dashboards and a Figma plugin that exports a Figma frame to a Tableau workbook.
What it still won’t have
- Tableau-reviewed hosted extensions and the official partner trust/visibility
- Hosted updates, packaging, and managed billing via Lemon Squeezy
- The vendor’s polish, docs, and support channels
What remains hard
- Brand trust
Official Tableau Partner
- Brand trust
Our extensions code has been carefully reviewed by Tableau
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 3 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal self-hosted replacement for LaDataViz's core offering: implement one Tableau Viz Extension (Sankey or Network) and a Figma→Tableau exporter. Stack: Node.js + Express backend (TypeScript), React frontend for extension UI, Figma plugin in TypeScript, Docker for deployment, and PostgreSQL for simple usage metrics. In scope: (1) a Tableau Extension using the Tableau Extensions API that renders a custom chart from dashboard data and exposes configuration UI; (2) a Figma plugin that exports selected frame as CSV + layout metadata and produces a downloadable Tableau workbook stub; (3) a backend to serve extension assets, validate a single-seat license token (JWT), and record monthly unique users; (4) Dockerized deployment, TLS instructions, basic admin UI to view usage; (5) CI scripts, error handling, and unit tests for core logic. Out of scope: reimplementing all 21+ chart types, Tableau Exchange packaging/review, merchant-of-record billing, and enterprise on-prem packaged installer. Require input validation, graceful error messages when Tableau APIs are unavailable, and automated tests covering export, extension rendering, and license validation.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 4 cited sources+3
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Evidence score67
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 4
Every page the run actually retrieved.
- official productLaDataViz home
- official pricingLaDataViz store / pricing
- open sourceapache/superset
- open sourcemetabase/metabase
Integrity checks
What held up, and what did not.
