GSH

Metabase

Self-hostable business intelligence: questions, dashboards, alerts and embeds on the SQL databases you already own.

Business Intelligence

Metabase is a business intelligence application that lets people ask questions and build dashboards on SQL databases by clicking rather than writing SQL, with a SQL editor when they want one, scheduled alerts and subscriptions, and charts or dashboards embedded in another product. It is self-hosted from the official Docker image metabase/metabase or as a standalone JAR on any host with Java installed, and stores its own application data in PostgreSQL, MySQL/MariaDB or the embedded H2 database used for local runs. The Open Source edition is free with unlimited users; outside the top-level enterprise directory its source is licensed under the GNU Affero General Public License v3.0. Paid self-hosted editions start at Pro, listed at 575 USD per month (517.50 USD per month billed yearly) with the first 10 users included and further users at 12 USD per user per month, which adds row and column security, SSO, caching controls and usage analytics. Enterprise is quoted from 20,000 USD per year and adds an air-gapped deployment option, a dedicated success engineer and a 1-day support SLA.

Key features

Open SourceFree self-hosted
LicenceOpen source · AGPL-3.0DeploymentSelf-hosted
Pro575 USD per instance / month
LicenceSource availableDeploymentSelf-hosted
EnterprisePrice on request
LicenceSource availableDeploymentSelf-hosted
Limits, notes & source

Open Source

Limits
Free unlimited users, unlimited questions and dashboards, and 20+ supported data sources. Row and column security, SSO, caching controls and white-labelling are not included.
Notes
Rendered on the pricing page only when the deployment switch is set to Self-hosted. Licence read from the repository: LICENSE.txt states that source outside the top-level enterprise directory is licensed under the GNU Affero General Public License, while that directory falls under the Metabase Commercial License; the binary published at hub.docker.com/metabase/metabase is the AGPL build. GitHub's licence API reports NOASSERTION for the repository as a whole because LICENSE.txt mixes both licences.

Pro

Limits
First 10 users included, further users 12 USD per user per month (130 USD per user per year); row and column level permissions, SSO, caching controls, usage analytics and auditing, multi-tenant embedded analytics, white-label ready.
Notes
Rendered under both Cloud and Self-hosted deployment, so it is recorded as self-hostable: self-hosting Pro or Enterprise means running the enterprise image (hub.docker.com/metabase/metabase-enterprise) with a licence token. Recorded at the monthly-billing price of 575 USD (517.50 USD per month, 6,210 USD per year, billed yearly). The plan price is not per seat: it includes 10 users and seats are added on top, hence the INSTANCE unit.

Enterprise

Limits
All Pro features plus procurement help, a dedicated success engineer, air-gapped deployment (at an additional fee) and a 1-day support SLA.
Notes
The pricing page states "Price starts at $20,000 / year" but the plan itself is custom priced, so no amount is recorded here; the floor is quoted in the notes instead of being presented as a list price.

Pros & cons

Strengths

  • Free Open Source edition with unlimited users. Source
  • Official Docker image metabase/metabase runs on any Docker host. Source
  • Paid Pro and Enterprise editions can be self-hosted, not only run on Metabase Cloud. Source
Show 1 more
  • Self-hosting means you can keep your own fork of the code. Source

Trade-offs

  • Self-hosting leaves upgrades, backups, SSL and SMTP setup to you. Source
  • Production needs a separate application database; the bundled H2 is not for production. Source
  • Single sign-on requires a paid Pro or Enterprise plan. Source
Show 1 more
  • Self-hosted paid plans start at Pro; the cheaper Starter tier is Cloud-only. Source

Metabase replaces

Products this app is built to take over from, with the vendor's own evidence.

Moving your content across: Documented per product: what you do on the side you are leaving, what this app does with the result, and what does not survive the trip. Every step links to the page that documents it.

  • TableauVendor comparison page titled "Why teams switch from Tableau to Metabase".Source
    • CaveatMetabase's Tableau transition guide is a PDF cheat sheet — the page offers only "Download PDF" and documents no importer, so workbooks and dashboards are rebuilt by hand.Source
  • LookerVendor comparison page titled "Why teams switch from Looker to Metabase".Source
    • ImportMetabase connects to the same database and picks up tables and fields by itself: Looker's Explore becomes the query builder, Looks become questions, folders become collections and tiles become cards.Source
    • CaveatThe vendor's guide is a concept map, not a converter: Metabase has no modelling language like LookML, so dimensions, measures and derived tables have to be modelled again by hand.Source
  • Looker StudioVendor page asks what makes Metabase a good choice compared with Looker Studio.Source
    • CaveatMetabase publishes no Looker Studio transition guide at all: its "Transition from other BI tools" index lists only Power BI, Tableau and Looker.Source
  • Power BIVendor comparison page contrasts Metabase with Power BI on licensing and semantic modelling.Source
    • CaveatMetabase's Power BI transition guide is a PDF cheat sheet — the page offers only "Download PDF", and nothing that converts Power BI reports or datasets is documented.Source