Metabase Pricing Teardown 2026
Metabase pricing: Starter at $100/mo, Pro at $575/mo, Enterprise from $20k/year — and the open-source edition still runs free under AGPL with almost everything except embedded analytics.
Get every pricing teardown in your inbox
We tear down open-source pricing — what it really costs, what the license allows, whether it's worth paying for. No spam.
This post is a part of series on commercial open source software pricing. See full list of articles here.
Metabase shows up in almost every seed-stage startup’s tech stack: quick to install, SQL-optional, free to self-host. ~47k GitHub stars puts it past “is this maintained?” and into foundational data tooling. Metabase, Inc. runs a cloud business on top of the AGPL core, in four tiers: Open Source / Starter / Pro / Enterprise.
- Website: metabase.com
- Pricing: metabase.com/pricing
- GitHub: github.com/metabase/metabase
Plans
- Open Source — free, self-hosted: The AGPL-licensed edition. 20+ data sources, unlimited dashboards and questions, SQL editor, models, AI-powered questions, basic permissions. No cloud hosting, no automatic backups. Embedded analytics excluded.
- Starter — $100/month (annual: $1,080/year): Cloud-hosted, 5 users included, +$6/user/month. Adds automatic backups, upgrades, multi-region hosting, 3-day email/chat support. No SSO, no embedded analytics — someone else runs the infrastructure, no commercial features unlocked.
- Pro — $575/month (annual: $6,210/year): Cloud or self-hosted (commercial license). 10 users included, +$12/user/month. Unlocks row/column-level permissions, SSO, multi-tenant embedded analytics, usage analytics, white-label. Self-hosted Pro is the entry point for teams that need data residency plus the commercial features.
- Enterprise — custom, from $20k/year: All Pro features plus air-gap deployment, dedicated success engineer, procurement assistance, 1-day SLA. No published per-seat rate.
The embedded analytics paywall
The most consequential line in the pricing table is a negative: “Embedded Analytics not available” on Open Source and Starter.
If you’re building a product that surfaces data to end users — a customer-facing operations dashboard, white-labeled reports, analytics embedded in your SaaS — the AGPL free tier and the $100/month Starter tier are both dead ends. You land on Pro at $575/month minimum, or Enterprise.
The paywall is well-constructed. Internal BI (your team queries your data) is free or cheap. Customer-facing BI (Metabase as the engine behind someone else’s analytics) is a commercial use case, priced as one. The split is defensible.
Starter is mostly a hosting bill
Starter at $100/month gives you automatic backups, cloud hosting, and support response times. It does not give you SSO, row-level permissions, or embedded analytics — those live behind Pro.
For a team that wants cloud hosting without self-managing infrastructure, Starter is legitimate: you’re paying for operations, not features. But a team eyeing Starter as a stepping stone to SSO hits a wall — there’s no mid-tier between “just hosting” and the full Pro feature set at $575/month.
Per-user rates add up on Pro. A 20-person team pays $575 base + 10 extra users × $12 = $695/month. A 50-person team pays $575 + 40 × $12 = $1,055/month.
Self-hosted Pro is the underrated option
Pro runs cloud or self-hosted. Self-hosted Pro requires a commercial license but unlocks every commercial feature without cloud hosting costs. For teams with existing infrastructure and strict data residency requirements, self-hosted Pro at $6,210/year for 10 users is worth comparing against cloud — the per-user cost is identical, but you skip the hosting bill.
License
Metabase core is AGPL-3.0. For internal use — your team queries your own data — it’s a clean option. AGPL requires open-sourcing modifications if you distribute them, but running a private instance against your warehouse isn’t distribution.
The commercial case is where it gets specific. The repository holds both the AGPL code and the commercial edition source; commercial features are gated by a license key, not separate code. To embed Metabase in a customer-facing product without AGPL’s copyleft obligations, you need a commercial license — Pro or Enterprise.
One nuance: the AGPL restriction applies to distributing a modified Metabase, not to using it via API or embedding dashboards. But Metabase’s embedding terms require a commercial license regardless. The rule: internal use is free; customer-facing use is paid.
Worth paying for?
Self-host the AGPL edition for internal BI if your team can handle the ops. It covers nearly everything except embedded analytics, and the v0.61 line is current as of May 2026 — actively maintained.
Starter is worth $100/month if you want Metabase without managing infrastructure and don’t need SSO or embedded analytics. It’s a hosting convenience, not a path to Pro features.
Pro at $575/month is justified when embedded analytics or SSO is a real requirement. White-label and multi-tenant make it the right tier for teams building a data product on top of Metabase. At that price, compare against Grafana (its own enterprise cliff) and other embedded analytics options.
Enterprise from $20k/year fits scale with compliance needs (air-gap, dedicated SLA) or procurement assistance and named support. At that floor, Metabase is steering larger accounts into custom contracts.
How Metabase pricing scales
Metabase charges a base plus per-user. SSO and embedded analytics sit on Pro, where both the base ($575 vs $100) and the per-user rate ($12 vs $6) roughly double.
This post is a part of series on commercial open source software pricing. See full list of articles here.
I build Beton — open source revenue intelligence for B2B SaaS.