Quick verdict
Choose Power BI if your organisation runs on Microsoft 365 and Azure, needs a governed semantic model with DAX measures, Excel integration and pixel-perfect paginated reports, and can budget per-user licences or Fabric capacity. Choose Metabase if you want SQL-literate staff and business users answering questions in a browser, with no Windows authoring tool, unlimited users on the free self-hosted edition, and a short path from a SQL query to a shared dashboard. Metabase is lighter on modelling; Power BI is heavier on licensing.
Power BI is Microsoft's business intelligence platform. Reports and semantic models are usually built in Power BI Desktop, a free Windows application (Windows 10 or Windows Server 2016 or later, 64-bit only), then published to the Power BI service, which is now integrated with Microsoft Fabric. Data is shaped with Power Query and modelled with DAX measures, and can be imported into the in-memory engine or queried live with DirectQuery. Sharing needs paid licences: Power BI Pro, Premium Per User (PPU), or a Fabric capacity. On-premises reporting is possible with Power BI Report Server.
Metabase is a browser-based BI tool. Its open source edition is released under the AGPL, while paid editions use the Metabase Commercial Software License. You can self-host it as a Java JAR or Docker container, or use Metabase Cloud. Business users build questions with a graphical query builder, analysts write SQL in the native query editor, and curated models act as reusable starting points. Paid plans (Starter, Pro, Enterprise) add hosting, SSO, row and column permissions and advanced embedding.
Side by side
| Aspect | Power BI | Metabase |
|---|---|---|
| Free option | Power BI Desktop is free; a Free licence covers personal use only, not sharing | Open source edition (AGPL), self-hosted, unlimited users |
| Paid licensing model | Per user (Pro, PPU) or Fabric capacity (F SKUs); viewers on F64 or larger need only a Free licence | Plan fee with included users plus a per-user charge (Starter, Pro); Enterprise by quote |
| Authoring | Power BI Desktop (Windows only); some model and report editing in the web service | Web browser on any OS |
| SQL access | Native database queries in Power Query; DirectQuery sends generated SQL to the source | Native query editor with variables, field filters and snippets; SQL models |
| Semantic layer | Semantic models with DAX measures, relationships and row-level security | Models (curated derived tables) with editable column metadata; lighter than a DAX model |
| Supported databases | Very broad connector library (databases, files, SaaS, Fabric) | 18 official drivers (PostgreSQL, MySQL, SQL Server, Snowflake, BigQuery and others) plus community drivers |
| Self-hosting | Power BI Report Server (on-premises, licensed through SQL Server or Fabric F64+ reservations) | JAR or Docker with a PostgreSQL or MySQL application database |
| Embedding | Power BI Embedded; "app owns data" on F, A or P capacity | Public and guest embeds in all editions; SSO modular embedding and SDK features on Pro and Enterprise |
| Main trade-off | Deep modelling and Microsoft integration, but Windows-only authoring and layered licensing | Quick to adopt and free to self-host, but a lighter semantic layer and key governance features are paid |
Key differences
How SQL users work in each tool
In Metabase, SQL is a first-class path. The native query editor runs a single read query against a connected database, and you add filter widgets with variables such as {{start_date}} or field filters, reuse code through snippets, and reference saved questions or models with tags such as {{#1-customer-model}}. Metabase documents that the editor does not support multi-statement queries, stored procedures or DDL. A SQL result can be saved, put on a dashboard or turned into a model.
-- Metabase native query (PostgreSQL), with an optional variable
SELECT date_trunc('month', created_at) AS month,
count(*) AS orders
FROM orders
WHERE 1 = 1
[[AND created_at >= {{start_date}}]]
GROUP BY 1
ORDER BY 1;In Power BI, SQL usually sits underneath. You can paste a native SQL statement when connecting to a source such as SQL Server, but the main logic lives in Power Query steps and DAX measures in the semantic model. With DirectQuery, Power BI generates SQL against the source for each visual, and Microsoft notes that stored procedures and CTEs cannot be folded in DirectQuery. In our view, analysts who think in SQL find Metabase more direct, while teams that want one governed model reused across many reports benefit from Power BI's DAX layer.
Licensing: per user and capacity versus open source plus plans
Power BI has three per-user licences: Free (content for yourself only), Pro and PPU. To share, authors need Pro or PPU. Viewers also need Pro or PPU unless the content is in a workspace on a Fabric F64 or larger capacity (or a legacy P capacity), where a Free licence with a viewer role is enough. Microsoft states it is retiring Power BI Premium per-capacity (P) SKUs and recommends Fabric F SKUs instead.
Metabase is free with unlimited users when you self-host the open source edition. Paid plans charge a base fee that includes a number of users, then a fee for each additional user; Metabase counts anyone who signs in as a user. The commercial features that most often decide the upgrade are SSO, row and column-level permissions and SSO-based embedding, which are on Pro and Enterprise.
Deployment and platforms
Power BI Desktop runs only on Windows; Mac users need a Windows machine or a supported virtual desktop such as Azure Virtual Desktop or Windows 365. Published content runs in Microsoft's cloud. For on-premises needs, Power BI Report Server hosts Power BI and paginated reports and is licensed through SQL Server core licences or Fabric F64+ reserved instances, according to Microsoft.
Metabase is a single Java application. Metabase recommends Eclipse Temurin JRE 25 for the JAR, or running it in Docker, and advises using PostgreSQL or MySQL as the application database in production rather than the default embedded H2. Metabase Cloud removes the hosting work. Everything is browser-based, so authors can use any OS.
Embedding analytics in your product
Power BI supports "embed for your organisation" and "app owns data" for external customers. For customer-facing embedding, content sits on an F, A (Power BI Embedded) or P capacity and end users do not need Power BI licences; the capacity is the cost.
Metabase offers public links, guest (signed) embeds and full-app embedding on all plans, including open source. Modular embedding with SSO, which unlocks the query builder, drill-through and the collection browser inside your app, plus advanced theming and row-level data segregation, requires Pro or Enterprise.
Pricing and licensing
Power BI. Listed on Microsoft's pricing page in October 2026 (USD): Power BI Pro USD 14.00 per user per month and Premium Per User USD 24.00 per user per month, both paid yearly. Power BI Desktop and the Free licence cost nothing. Fabric capacity (F SKUs) is priced regionally, billed per second through Azure with an optional yearly reservation, and Power BI Embedded is quoted. Check the Azure pricing calculator for capacity.
Metabase. The open source edition is free. Listed on Metabase's pricing page in October 2026 (USD): Starter USD 100 per month (or USD 1,080 per year) with 5 users included and USD 6 per extra user per month; Pro USD 575 per month (or USD 6,210 per year) with 10 users included and USD 12 per extra user per month; Enterprise is custom, from USD 20,000 per year. Starter and Pro have a 14-day free trial. Optional usage-based add-ons (AI tokens, transforms, storage) are billed separately.
Pricing checked on the vendors' official pages on 7 October 2026. Prices change; confirm before buying.
Where each one leads
Power BI strengths
- DAX semantic models with relationships, measures and row-level security reused across reports
- Close integration with Excel, Microsoft 365, Teams and Fabric
- Very broad connector library, with Import, DirectQuery and Direct Lake modes
- Paginated reports for print-ready output
- On-premises option through Power BI Report Server
Metabase strengths
- Free open source edition with unlimited users when self-hosted
- Browser-based authoring on any OS
- Native SQL editor with variables, field filters, snippets and model references
- Quick for business users through the graphical query builder
- Guest embeds available even in the open source edition
Limitations
Power BI limitations
- Power BI Desktop runs on Windows only
- Sharing requires Pro or PPU for every viewer unless content sits on F64 or larger capacity
- DAX and Power Query are extra languages for SQL users to learn
- Licensing is layered (per user, capacity, Embedded, Report Server) and Microsoft is retiring P SKUs
Metabase limitations
- SSO, row and column-level permissions and SSO embedding require Pro or Enterprise
- Lighter modelling layer than a DAX semantic model for complex measures
- The native editor runs single read queries only (no stored procedures, DDL or multiple statements)
- Self-hosting means running a Java service and a production application database yourself
- AGPL licence obligations apply if you modify and distribute or serve the open source code
When to choose each
Choose Power BI if
- Your company already has Power BI licences through Microsoft 365, or Fabric capacity
- You need a central semantic model with DAX measures reused by many report authors
- Excel users need to analyse published models
- You need paginated, print-ready reports or on-premises Report Server
Choose Metabase if
- Your analysts work in SQL and want queries to become dashboards quickly
- You want many internal users without per-seat costs, and can self-host
- Authors use macOS or Linux
- You want to embed simple charts in an internal tool with no licence cost
When neither is right
- You need a governed semantic layer defined in code on Google Cloud: see Power BI vs Looker and Looker vs Looker Studio.
- You want an open source tool with a full SQL IDE and many chart types, and are comfortable running more infrastructure: see Metabase vs Apache Superset.
- Visual exploration by analysts is the priority and Salesforce is your CRM: compare Power BI vs Tableau.
- You only need a few reports from one database: scheduled SQL into a reporting table may be enough; see data warehouse vs database.
Final recommendation
Power BI is the stronger choice for Microsoft-centred organisations that need governed models, Excel integration and enterprise distribution, and that accept Windows-only authoring and per-user or capacity licensing. Metabase is the better fit for SQL-literate teams that want self-service dashboards in a browser quickly and cheaply; the open source edition covers a lot, but plan for Pro if you need SSO, row-level permissions or rich embedding. For the wider open source field, see the best open source BI tools.
Frequently asked questions
Is Metabase free?
The open source edition is free to self-host with unlimited users and is released under the AGPL. Metabase Cloud and the commercial features (SSO, row and column permissions, SSO embedding) are paid plans: Starter, Pro and Enterprise.
Can I write SQL in Power BI?
Yes, in limited ways. You can supply a native SQL statement when connecting to sources such as SQL Server, and DirectQuery generates SQL against the source. Most calculation logic, however, is written in Power Query and DAX rather than SQL.
Does Power BI Desktop run on a Mac?
No. Microsoft lists Windows 10 or Windows Server 2016 or later as the minimum. Mac users typically use a Windows virtual machine or a supported virtual desktop such as Azure Virtual Desktop or Windows 365, or work in the Power BI service in a browser.
Which databases does Metabase support?
Metabase maintains official drivers for Athena, BigQuery, ClickHouse, Databricks, Druid, MongoDB, MariaDB, MySQL, Oracle, PostgreSQL, Presto, Redshift, Snowflake, SparkSQL, SQL Server, SQLite, Starburst and Vertica. Community drivers cover others but are not supported by Metabase.
Do Power BI report viewers need a licence?
Yes, a Pro or PPU licence, unless the report is in a workspace on a Fabric F64 or larger capacity (or a legacy P capacity), where viewers with a Free licence and a viewer role can open it. Customer-facing embedding with "app owns data" does not need end-user licences.
Sources
- Power BI pricing (Microsoft)
- Power BI service features by licence type
- Microsoft Fabric licences and capacity
- Download Power BI Desktop (minimum requirements)
- DirectQuery in Power BI
- What is Power BI Report Server
- Metabase pricing
- Metabase: connecting to databases
- Metabase: SQL editor
- Metabase: embedding overview
- Metabase: running the JAR file
- Metabase on GitHub (licences)
Checked October 2026.
How we research comparisons: our editorial method.