Sigma vs Tableau: an honest comparison from a consultant who builds both
How Sigma and Tableau differ on warehouse queries, who can build reports, write-back, self-hosting, and pricing, with every claim linked to its source.
Linus TseGreyfield DataFacts last checked Contents 10 sections
The short answer
If your data already lives in Snowflake or Databricks and the people asking questions think in spreadsheets, Sigma is usually the better fit. Pick Tableau if you need the most control over visual design, have to self-host, want a published entry price, or run on Salesforce. We sell Sigma consulting, and we have also shipped Tableau work for clients, including a customer-facing analytics product.
How Tableau and Sigma Computing differ
- 01
Live queries vs extracts
Sigma always queries your warehouse, so there are no extracts to refresh. Tableau lets you choose live or in-memory extracts, which are fast and save warehouse compute but add a refresh job.
- 02
Spreadsheet vs visual shelves
Sigma users work in a formula grid that feels like Excel. Tableau authors drag fields onto shelves, which gives more design control and takes longer to learn.
- 03
Write-back is built in
Sigma input tables save forecasts, approvals, and edits to the warehouse. Tableau needs a paid third-party extension for that.
Pricing at a glance
Tableau
Salesforce (acquired 2019)
Long-established visual analytics platform, sold as Tableau Cloud (SaaS), Tableau Server (self-hosted), Tableau Desktop and the newer Agentforce-based Tableau Next. Built for analysts who author highly customized interactive visualizations, often across many data sources, using live connections or in-memory extracts.
- Pricing model
- Per user, annual contract (also capacity-based viewer blocks on Cloud and 8-core compute licensing on Server)
- Published starting price
- $15/user/month billed annually (Tableau Standard, starting price); Enterprise from $35; Tableau Next from $40/user/month
- Free tier
- Yes: Tableau Desktop Free Edition (local files, cannot publish or share) and Tableau Public; also a free trial
- What drives cost
- Tableau's pricing page shows edition starting prices only: Standard $15, Enterprise $35, Cloud+/Server+/Tableau+ via sales. Third-party licensing advisor Redress Compliance (updated Sept 2026) lists per-role prices of Creator $75 / Explorer $42 / Viewer $15 on Standard and $115 / $70 / $35 on Enterprise, per user per month billed annually. AI (Tableau Agent) on Cloud requires Cloud+ / Tableau+.
Sigma Computing
Sigma Computing, Inc. (private, venture-backed; $80M Series E at a $3B valuation, May 2026)
Cloud BI and data-app platform that runs queries live against a cloud warehouse (Snowflake, Databricks, BigQuery, Redshift and others) through a spreadsheet-style interface, with write-back input tables, Python/SQL and AI agents. Built for companies that already keep their data in a cloud warehouse and want business users to work on it without extracts.
- Pricing model
- Annual subscription: platform tier plus per-user licenses (Creator / Explorer / Viewer, per third-party buyer data)
- Published starting price
- Not published
- Free tier
- No; 7-day free trial with sample data or your own warehouse
- What drives cost
- Sigma's pricing page shows no prices and sends buyers to sales. Vendr buyer data (third-party, directional only) lists Essential, Business and Enterprise tiers, Creator licenses at roughly $1,200-$5,000+ per year depending on tier, and a median contract of about $65K per year (range ~$15.6K-$145K). Warehouse compute is billed separately by your warehouse vendor.
Feature comparison
"Not verified" means we could not confirm it from public docs, not that the feature is missing. Each cell links to the page we checked.
Data and querying
| Feature | Sigma Computing | Tableau |
|---|---|---|
| Queries the warehouse live Reads the cloud warehouse at view time, without an extract or import step. | Yes Workbooks query the connected warehouse directly; no extract engine. source | Yes Live connections to Snowflake, BigQuery, Redshift and others, or in-memory extracts; the author chooses. source |
| Spreadsheet-style editing Business users work in a grid and write formulas instead of a separate modeling language. | Yes Spreadsheet grid with 200+ functions on live warehouse data. source | No Authoring uses visual shelves and calculated fields, not a spreadsheet-style formula grid. source |
| SQL editor Write SQL against the warehouse inside the product. | Yes Custom SQL elements in workbooks and data models. source | Custom SQL source only Custom SQL data sources, limited to a single SELECT statement that Tableau wraps in its own queries. Not a full SQL workspace. source |
| Python Run Python inside the product. | Snowflake & Databricks only Only on Snowflake and Databricks connections; output cannot be materialized; only JWT-signed embeds are supported. source | Via TabPy Python runs through TabPy analytics extensions, which you host yourself, called from table calculations. Supported on Cloud and Server. source |
| Writeback / input tables Users can enter or edit data that is saved back to the warehouse. | Yes Input tables write to a warehouse write schema. Not available on some sources (MySQL, SQL Server, Azure SQL DB, AlloyDB, Starburst, ClickHouse, MotherDuck). source | Third-party extension Not native. Available only through paid third-party extensions on Tableau Exchange, such as Write-Back Cloud. source |
| Governed semantic layer Reusable, governed models and metric definitions. | Yes Data models with reusable metrics, relationships and RLS, also manageable as JSON/YAML via the API. source | Yes Published data sources and virtual connections; Tableau Semantics models in Tableau Next (Semantic Model Builder GA August 2026). source |
Sharing and governance
| Feature | Sigma Computing | Tableau |
|---|---|---|
| Embedded analytics Embed reports in your own app or portal for external users. | Yes JWT-signed secure embeds that pass user attributes and teams for RLS. source | Yes Embedding API v3 and connected apps with JWT; per-user or usage-based embedded pricing via sales (per third-party review). source |
| Scheduled delivery Scheduled email, Slack, or file delivery of reports. | Yes Email, Slack, Teams, SharePoint, Google Sheets/Drive, webhook and cloud storage. source | Yes Email subscriptions with PNG/PDF on a schedule or after extract refresh; Slack app for alerts and sharing. source |
| Row-level security Restrict which rows each user can see. | Yes Based on user, team or user attribute; works in embeds via JWT claims. source | Yes User filters, database RLS on live connections, JWT user attributes for embeds; centralized data policies need the Data Management add-on. source |
| Excel / CSV export Export data to Excel or CSV. | Yes Excel and CSV up to 1M rows; larger exports go to cloud storage. source | Yes Crosstab download to .xlsx or CSV, if the author allows it (described by a third-party guide). source |
| Git version control Content or models can be versioned in git. | Version tags + API Version tags (with protected-tag approvals) and spec APIs; no built-in git sync, so teams build their own pipeline. source | Partly Workbooks have revision history (restore and notes) but no git. The Tableau Semantics DX extension adds git and CI/CD for Tableau Next semantic models only. source |
Platform
| Feature | Sigma Computing | Tableau |
|---|---|---|
| AI assistant Natural-language questions or AI-assisted building, generally available. | Yes Sigma Assistant answers natural-language questions and shows its SQL; requires an AI provider set up for the org. Some AI surfaces, such as homepage chat, are still beta. source | Tableau+ edition on Cloud Tableau Agent is GA in web authoring, but on Cloud it requires the Tableau+ edition. Tableau Agent in Dashboards was still beta in 2026. source |
| Open source / self-host An open-source or self-hosted option exists. | No SaaS only, hosted on AWS, Azure or GCP regions. source | Yes Tableau Server is self-hosted on Windows or Linux; not open source. source |
| Needs a desktop app to author "Yes" means some authoring requires installing a desktop application. | No Authoring is entirely in the browser. source | Partly Web authoring covers most work, but some features (such as actions, Viz in Tooltip setup, clusters and forecasts) need Tableau Desktop. source |
They query your data in different ways
Sigma has no extract engine. Every chart and table runs as a query against your warehouse when someone opens it, so the numbers are as fresh as the warehouse and there is no extract schedule to maintain.
Tableau lets the author choose between a live connection and an in-memory extract. Extracts make busy dashboards fast and keep repeated queries off your warehouse bill. They also add a refresh job that can fail or go stale.
That difference shows up in cost. With Sigma, more usage means more warehouse compute. With Tableau extracts, much of that load moves onto Tableau. If your warehouse spend is already under scrutiny, model both before deciding.
Who can build reports
Sigma looks like a spreadsheet. Finance and operations people can add columns, write formulas, group, and pivot on billions of rows without learning a modeling language. That is the main reason teams move to it.
Tableau authoring uses shelves, marks, and calculated fields. Analysts who learn it can build things Sigma cannot, and the pool of experienced Tableau developers is far larger. Business users who just want to adjust a report often end up exporting to Excel instead.
Write-back and workflows
Sigma input tables let users type or edit data that is stored in the warehouse, which makes forecasts, approvals, and adjustments possible inside the report. Tableau has no native equivalent; teams buy third-party extensions for it.
If your reports end in a spreadsheet where someone types a plan, a comment, or an override, that is the strongest argument for Sigma.
Pricing
Tableau publishes starting prices on its pricing page, and a free Desktop edition works on local files. Its per-role prices are no longer shown there, and AI features on Tableau Cloud need a higher edition.
Sigma does not publish prices. Third-party buyer data puts the median contract in the tens of thousands of dollars a year, which is directional at best. Ask both vendors for a quote built on your actual user mix, and add the warehouse compute Sigma will drive.
If you are already on Tableau
Most of the effort in a move is not rebuilding charts. It is finding which calculations people rely on, how filters behave, and which dashboards nobody uses anymore. Start with one representative workbook before you commit to moving everything. Our Tableau to Sigma migration service and the Tableau calculations cheat sheet cover how we do it.
Where Tableau is better
- Deeper visualization flexibility and polish than Sigma, with many years of chart types, mapping (such as drive-time areas added in 2026) and formatting control
- Self-hosted option (Tableau Server, including container builds on Server+); Sigma is SaaS only
- In-memory extracts let dashboards run fast and avoid warehouse compute costs on repeated queries; Sigma always queries the warehouse
- Published list prices: Standard starts at $15 per user per month, and a free Tableau Desktop edition is available for local files
- Much larger community, training ecosystem and talent pool (Tableau Public, user groups, certifications)
- Native ties to Salesforce, Slack and Agentforce for teams already on Salesforce
- Works with almost any data source, including on-premises databases through Tableau Bridge
Who should pick which
Pick Tableau if
- You need pixel-level control over complex visualizations or maps.
- You must run BI on your own servers or in your own cloud account.
- Your data is spread across sources that are not in a cloud warehouse, and extracts help.
- You are standardized on Salesforce and want analytics tied into Agentforce and Slack.
- You need to hire experienced developers quickly.
Pick Sigma Computing if
- Your data is already in Snowflake, Databricks, or BigQuery and you want no extracts to maintain.
- Finance and operations users live in Excel and want to work on live warehouse data.
- Reports need to collect input: forecasts, approvals, comments, or adjustments saved to the warehouse.
- You want SQL and Python in the same workbook as the spreadsheet view.
Recommendations by team
| If you are | Pick | Why |
|---|---|---|
| Finance team on Snowflake | Sigma Computing | Spreadsheet formulas on live data, plus input tables for forecasts and adjustments. |
| Analytics team building polished executive or public dashboards | Tableau | More visual control, more chart types, and Tableau Public for sharing. |
| Company that must self-host BI | Tableau | Tableau Server runs on your own infrastructure. Sigma is SaaS only. |
| Salesforce-centric company | Tableau | Native ties to Salesforce, Slack, and Agentforce. |
| Operations team that plans in spreadsheets | Sigma Computing | Plans and overrides are typed into the report and saved to the warehouse. |
| Team with data in many non-warehouse sources | Tableau | Extracts and Tableau Bridge handle sources that are not in a cloud warehouse. |
Recent changes to Tableau
- 2025 Tableau Next launched at Tableau Conference 2025: an agentic analytics product built on the Salesforce Agentforce platform.source
- 2026-01 January 2026 release: Tableau Agent added to Tableau Server (needs your own OpenAI API keys), dashboard narratives beta, and AI-generated semantic models.source
- 2026-05 Announced an agentic analytics platform with an AI knowledge layer at Tableau Conference 2026 (San Diego). GA planned for later in 2026, with deeper Salesforce integration in early 2027.source
- 2026-08 August 2026 release: Semantic Model Builder GA in Tableau Next, Semantics DX extension with git/CI-CD, hosted Tableau MCP announced as coming soon, and Tableau Agent in Dashboards beta.source
- 2026 Pricing page restructured around Standard / Enterprise / Cloud+ / Server+ / Tableau+ editions, with Tableau Next listed at $40 per user per month.source
Questions people ask
Does Sigma replace Tableau?
Yes, if your data is in a supported cloud warehouse, you can run BI as SaaS, and most users want to explore and edit reports themselves. No, if you rely on Tableau Server on your own infrastructure, need complex custom visualizations, or have important data outside a warehouse.
Is Sigma cheaper than Tableau?
It depends on your user mix and your warehouse. Tableau publishes starting prices and Sigma does not. Sigma also drives warehouse compute on every query, while Tableau extracts can avoid some of it. Get quotes for the same set of users and estimate warehouse cost before comparing.
Can Sigma replace Tableau Server?
Only if you can move to a hosted service. Sigma runs only as SaaS on AWS, Azure, or Google Cloud regions, and it needs your data in a supported cloud warehouse or database.
Does Sigma use extracts like Tableau?
No. Sigma queries the connected warehouse directly every time. There is no extract engine to schedule or refresh.
How long does a Tableau to Sigma migration take?
It depends mostly on how many shared calculations and data sources the dashboards depend on, not on the number of dashboards. Our migration timeline guide breaks down what drives it.
Sources and corrections
We checked these pages on the dates shown. Products change quickly. If you work at Tableau and something here is wrong or out of date, email linus@greyfielddata.com and we will fix it.
- Tableau pricing (teams and orgs)
- Tableau August 2026 release features
- Tableau January 2026 release features
- Tableau help: Tableau Agent
- Tableau help: Web authoring vs Desktop
- Tableau help: Custom SQL
- Tableau help: Revision history
- Tableau help: RLS options
- Tableau help: Subscriptions
- Tableau help: Tableau app for Slack
- Tableau: TabPy Python integration
- Tableau blog: Extracts vs live connections (2016)
- Tableau Exchange: Write-Back Cloud (third-party extension)
- Redress Compliance: Tableau pricing 2026 (third party)
- Holistics: Tableau embedded analytics (third party)
- Atrium: Tableau Conference 2026 takeaways (third party)
- Pulse.bot: Tableau agentic analytics platform news (third party)
- The Bricks: Export Tableau to Excel (third party)
- Sigma pricing page (no prices listed)
- Sigma spreadsheets product page
- Sigma docs: Region, warehouse and feature support
- Sigma docs: Write and run Python code
- Sigma docs: Input tables overview
- Sigma docs: Sigma Assistant
- Sigma docs: Version tags
- Sigma docs: Manage data models as code
- Sigma docs: RLS in embeds
- Sigma docs: Send or schedule workbook exports
- Sigma docs: Download, export and upload limitations
- Sigma docs: Start your Sigma trial
- Sigma blog: Workflow 2026 recap
- Business Wire: Sigma Series E (May 2026)
- InterWorks: New Sigma features, June 2026 (third party)
- phData: Sigma API to git integration, Sept 2026 (third party)
- Vendr: Sigma buyer pricing data (third party)
- Capterra UK: Sigma reviews (third party)
Related comparisons
Sigma vs Power BI: which fits a company on Snowflake?
Power BI is cheap per seat and everywhere in Microsoft shops. Sigma queries Snowflake live in a spreadsheet. Here is how licensing, modeling, and write-back compare.
Sigma vs Looker: governed models or spreadsheet freedom?
Looker centers on a LookML model the data team owns. Sigma centers on a spreadsheet business users own. Here is how that plays out on Snowflake and BigQuery.
Sigma vs Omni: spreadsheet-first or model-first BI?
Sigma and Omni both query your warehouse live and both have spreadsheet views. The real difference is where the logic lives and who maintains it.