Three BI tools, three completely different starting assumptions about who builds the dashboard and who pays for it. Metabase assumes you want self-service reporting without hiring a data engineer. Looker assumes you have an analytics engineer willing to learn a custom modeling language. Tableau assumes visual precision matters more than anything else and you have the budget to match.
None of them are wrong. The mismatch happens when a team picks based on brand recognition instead of which assumption actually fits their situation.
Metabase: Free, Fast, and Honest About Its Limits
Metabase is open-source and self-hostable at zero cost. Pull the Docker image, connect your database credentials (Postgres, MySQL, BigQuery, Snowflake, and about 20 others), and business users are dragging-and-dropping their own queries within 10 minutes. No SQL required for the question builder, which covers roughly 80% of what non-technical stakeholders actually need. For the remaining 20%, native SQL mode is right there in the same interface.
Cloud-hosted Metabase starts at $85/month for 5 users if you don't want to self-host. Enterprise tier adds SSO, row-level permissions, and audit logs for teams that need access control beyond "everyone with a login sees everything."
The honest limitation: Metabase is a querying tool, not a transformation layer. There's no LookML-style semantic layer where you define a metric once and every report inherits that definition. You're querying raw tables directly, which means dirty source data produces dirty dashboards, and two people can build "revenue" two different ways without the tool catching the discrepancy. r/dataengineering's recurring complaints are slow rendering on complex queries and no caching on the free tier, meaning every dashboard load hits the database fresh.
This is the right tool for teams that want self-service reporting without a dedicated data engineer maintaining a modeling layer. It is the wrong tool for an organization where "sales and finance have different revenue numbers" is already a recurring argument, because Metabase has no mechanism to prevent that.
Looker: The Semantic Layer, at Enterprise Prices
Looker is Google's BI platform, acquired in 2019 for $2.6 billion, built around LookML: a data modeling language that sits between your warehouse and your reports. The idea is straightforward and genuinely solves a real problem. Define "monthly recurring revenue" once in LookML, and every dashboard, every team, every export uses that exact same calculation. The "whose numbers are right" argument goes away because there's only one definition to argue about.
Pricing starts around $3,000-5,000/month minimum for the enterprise platform. Looker Studio (formerly Google Data Studio) is the free, much more limited sibling product, essentially a different tool wearing a related name, not a stripped-down version of full Looker.
The friction point every team hits: LookML is a custom domain-specific language, and someone has to actually learn it well enough to build and maintain the models. That person becomes a load-bearing dependency. Business users self-serve fine once the models exist, but getting there requires real investment. Complex queries against large warehouses (Redshift, BigQuery) can also be slow, since Looker's exploration layer depends entirely on your warehouse's query engine for performance; Looker doesn't do the heavy lifting itself.
Looker is strongest in organizations already running BigQuery or the broader Google Cloud stack, where the integration story is tightest, and where an analytics engineer role already exists or is budgeted for. Without both of those things in place, you're paying enterprise pricing for a semantic layer nobody has the bandwidth to build properly.
Tableau: Visualization Quality as the Product
Tableau has been the BI standard for two decades. Salesforce acquired it in 2019 for $15.7 billion and has been integrating it deeper into the Salesforce ecosystem since. Pricing: Creator (dashboard building) runs $75/user/month, Explorer (exploration without full build access) runs $42/user/month, Viewer (consumption only) runs $15/user/month.
The visualization capability is genuinely best-in-class. Custom visuals and publication-quality formatting that neither Looker nor Power BI matches. Tableau Prep handles data cleaning and transformation before it reaches dashboards, closing some of the gap Metabase leaves open around dirty source data.
The cost is the obvious complaint, and it compounds fast. A 20-person team where everyone needs Creator access is $1,500/month just in licensing, before any data infrastructure. The learning curve is also real: Tableau has its own vocabulary (dimensions vs. measures, LOD expressions, table calculations) that takes meaningful time to internalize even for people comfortable with data generally. Tight Salesforce integration is a plus for Salesforce-centric organizations and unnecessary complexity for everyone else.
Tableau remains the right choice for standalone executive dashboards and printed or presented reports where visual precision is the actual requirement, not just "a chart that's technically correct."
Side-by-Side
| Metabase | Looker | Tableau | |
|---|---|---|---|
| Cost | Free self-hosted, $85/mo cloud (5 users) | $3,000-5,000+/mo | $15-75/user/mo |
| Semantic layer | No | Yes (LookML) | Partial (Prep) |
| Setup time | Under 10 minutes | Weeks (LookML modeling) | Days to weeks |
| Best visualizations | Basic | Good | Best-in-class |
| Requires dedicated owner | No | Yes (analytics engineer) | Recommended |
| Best warehouse fit | Any (20+ connectors) | BigQuery / GCP | Any |
When Free BI Tooling Is Actually Enough
Metabase is enough when your reporting needs are genuinely straightforward: a handful of core metrics, a small number of source tables, and a team that trusts each other's numbers because there aren't yet competing definitions of the same metric floating around. Most companies under 50 people fit this description whether they realize it or not.
The signal that you've outgrown it isn't company size, it's definitional drift: when two departments present different numbers for something that should be one number, that's the moment a semantic layer earns its cost. That's a Looker problem, and it's worth paying for at that point, but not before.
Tableau's cost is justified specifically by the visualization requirement, not by BI needs generally. If nobody in the company needs a dashboard precise enough to hand to a board or print for an investor deck, Tableau's premium is buying capability you aren't using.
The Recommendation
Start with Metabase. It's free, it's fast to stand up, and it covers the reporting needs of most teams under 50 people without requiring anyone to become a full-time BI administrator. Self-host it if you have any infrastructure capacity at all; the setup genuinely takes under 10 minutes.
Move to Looker only when you can name a specific instance of two teams disagreeing about the same metric's definition, and only if you're already on BigQuery or can budget for an analytics engineer to own the LookML models. Without that role filled, Looker's investment sits half-finished.
Reach for Tableau specifically for executive-facing or externally-shared reports where visual polish is the actual deliverable. Using Tableau's $75/user Creator license for internal dashboards a handful of analysts will look at is paying for a printing press to write a memo.
For the parallel question of when free, self-hosted infrastructure tooling makes sense versus paying for a managed platform, the Sentry vs Datadog comparison covers the same tradeoff pattern in the observability space, and the PostHog vs Mixpanel vs Amplitude breakdown covers it again for product analytics specifically.