Overview
Self-hosted business intelligence and analytics with dashboards and SQL queries.
Metabase is an open-source business intelligence and analytics platform that connects to databases so teams can ask questions, build charts and dashboards, and share data insights from infrastructure they control.
Why people choose Metabase
Its visual query builder makes common analysis approachable while the SQL editor supports direct database work. Dashboards, filters, models, metrics, alerts, subscriptions, and permissions let teams move from one-off questions to repeatable reporting.
What is included
Official Metabase documentation covers questions and charts, SQL queries, dashboards, models, metrics, data visualization, alerts, exports, permissions, embedding, and an AI layer guided by the semantic model. Supported data sources span relational databases, warehouses, and services documented by Metabase.
What to know before deployment
The open-source edition is not the same as Metabase Cloud or the commercial editions. Self-hosting means managing the application runtime, application database, upgrades, backups, database credentials, network access, and permissions. The official docs show a quick Docker start, but production deployments should use a supported external application database rather than treating the default H2 setup as a backup strategy.
Best fit
Choose Metabase for self-hosted dashboards and analytics when you want a friendly interface over your own databases. Consider a lighter dashboard tool for a single static status page, or a more specialized warehouse/BI stack for advanced enterprise governance and large-scale transformation work.
Interface previews
Screenshots of the Metabase interface.
Feature support
| Feature | Support |
|---|---|
| Visual query builderMetabase lets users create questions and charts through a visual query builder without writing SQL for every report. | Supported |
| SQL editor and parametersOfficial documentation covers native SQL queries, SQL parameters, field filters, snippets, and reusable query patterns. | Supported |
| Dashboards and filtersDashboards combine saved questions and visualizations with filters, interactivity, text cards, and linked filters. | Supported |
| Models, metrics, and semantic definitionsMetabase supports models, metrics, metadata editing, semantic types, segments, and a semantic layer for consistent business definitions. | Supported |
| Alerts, subscriptions, and exportsThe docs cover alerts, dashboard subscriptions, and exporting query results for recurring reporting workflows. | Supported |
| Permissions and sharingMetabase includes permissions and sharing controls; the exact depth depends on the edition and deployment configuration. | Supported |
| Embedding and APIsMetabase documents embedding and APIs for integrating analytics into applications, with edition-specific capabilities. | Supported |
| AI-assisted analyticsCurrent official pages describe AI features and Metabot, but availability, configuration, data access, and licensing vary by edition and should be checked before deployment. | Partial support |
Questions
What is Metabase used for?
Metabase is used to connect to databases, ask questions, create charts and dashboards, share reports, and help teams explore business data.
Is Metabase a self-hosted Tableau or Power BI alternative?
Metabase can be a self-hosted alternative for teams that need approachable dashboards and SQL-backed analytics, but feature depth, governance, and licensing differ from Tableau and Power BI.
Is Metabase open source?
Metabase has an open-source edition and a public repository, alongside commercial editions and features. Check the current edition and license terms for the capability you plan to deploy.
Can Metabase run with Docker?
Yes. The official site documents a Docker quick start using the Metabase image. Production deployments should also configure a durable supported application database, persistent storage, backups, and secure credentials.
What database does Metabase need?
Metabase connects to the databases you want to analyze and also stores its own application metadata. The official installation documentation distinguishes the quick-start setup from production use, where a supported external application database is recommended.
What is the main tradeoff with self-hosted Metabase?
You gain control over analytics data and deployment, but you must operate the application, database, upgrades, backups, permissions, network security, and edition-specific features yourself.
support // the lab
Found this write-up useful?
If it saved you time or a rebuild, you can support more practical homelab guides.