“There’s a free, open-source tool we can install on our own server.” In many small businesses, that’s how Metabase enters the conversation, often through a developer or technical lead who has used it elsewhere. Facing it, Power BI arrives with all the obviousness of Microsoft 365. But a close reading on October 2, 2026 of Metabase’s pricing page and documentation shows that the real difference is not “free versus paid.” Metabase’s free tier stops at specific points: the connection to your Microsoft directory, data partitioning by person, and the way accounts are counted. Those three boundaries decide the real cost.
This article compares Metabase (open-source edition, Starter and Pro plans) and Microsoft Power BI from the standpoint of a company with 10 to 250 employees that wants dashboards on its sales, margin or production. Sources: the metabase.com pricing page, its documentation (billing, SAML, OIDC and Microsoft Entra ID authentication, row and column security, Cloud limits, region selection, upgrades, application database), Metabase’s licensing page, the Power BI pricing page (microsoft.com, French and US editions) and Microsoft Learn. This is the fourth head-to-head in our series on dashboard and reporting tools, after Power BI vs Looker Studio, Power BI vs Tableau and Excel vs Power BI.
A note on method: we subscribed to nothing and took no price from a third-party comparison. Metabase publishes its prices in US dollars, excluding taxes; Microsoft’s US page lists Power BI Pro at $14 per user per month, paid yearly (both as of November 2026). The French edition of this article converted Metabase’s dollar prices at the European Central Bank reference rate of October 1, 2026 (€1 = $1.1298), rounded to the euro, against Power BI at €12.10 per user per month excl. VAT; those France figures (€) are kept in the chart and table below, with the US dollar figures alongside.
Two philosophies: a tool on your database, a tool inside your suite
Both tools build dashboards, but they don’t start from the same place. Power BI starts from your files and your applications. Its authoring tool, Power BI Desktop, is a free Windows application that can read an Excel workbook, a SharePoint list, an ERP export or a database, clean them up with Power Query and link them in a model. The report is then published to the Power BI service, where every viewer needs a license.
Metabase starts from a database. It’s a web application you connect to PostgreSQL, MySQL, SQL Server, BigQuery, Snowflake and some twenty other sources (“20+ supported data sources,” says the pricing page). You ask questions by clicking or in SQL, assemble them into dashboards, and everything happens in the browser. There’s no software to install on employees’ computers. On the other hand, if your numbers live in scattered Excel files, Metabase won’t read them directly: you’ll need to load them into a database or use CSV upload (storage of uploaded rows is billed beyond one million rows on the Cloud, starting at $2 per million).
That’s the first question to ask, even before price: is your data already in a SQL database? If your ERP, e-commerce platform or line-of-business app runs on PostgreSQL or SQL Server and someone on the team can write a query, Metabase is at home. If your reporting relies on exports and spreadsheets, Power BI and its Power Query do the preparation work that Metabase assumes is already done. Our guide on ERP data integration explains how to build that shared layer.
What the vendors publish, line by line
The table below shows only what appears on the official pages. The Metabase columns separate the free edition from the Pro plan, because it’s between the two that you find most of the features a small business takes for granted in Power BI.
| Criterion | Metabase Open Source / Starter | Metabase Pro | Power BI Pro |
|---|---|---|---|
| Published price | Open Source: free, unlimited accounts. Starter (Cloud): $100/month or $1,080/year, 5 accounts included, then $6/month or $65/year per account. | $575/month or $6,210/year, 10 accounts included, then $12/month or $130/year per account. Enterprise: “starting at $20,000 per year.” | $14 per user per month, paid yearly (US list price, as of November 2026). Premium Per User: $24. |
| Hosting | Open Source: on your own infrastructure (Java JAR file or Docker). Starter: Metabase Cloud only. | Cloud or self-hosted, same price. | Microsoft cloud service. A data gateway must be installed for on-premises sources. |
| Cloud region | Two regions to choose from in the account: US West (Oregon) or Europe (Frankfurt). Switching takes under 30 minutes of downtime, according to the documentation. | Storage region tied to the company’s Microsoft 365 tenant. | |
| Microsoft Entra ID sign-in | No: SAML and OIDC are reserved for Pro and Enterprise. Available: Google sign-in on a single domain, basic LDAP. | Yes, SAML or OIDC, with a dedicated Entra ID guide in the documentation. | Native: it’s each employee’s Microsoft 365 account. |
| Row-level permissions (each sales rep sees only their own customers) | No: row and column security is “only available on Pro and Enterprise plans.” | Yes, on Cloud and self-hosted alike. | Yes (RLS), but it doesn’t apply to the workspace Admin, Member and Contributor roles. |
| Authoring tool | Web browser, visual or SQL editor. No software on employees’ computers. | Power BI Desktop, free, Windows only; partial web editing in the service. | |
| AI features | SQL generation and natural-language questions. Your own AI provider’s API key, or Metabase’s managed service on the Cloud (1 million tokens included to start, then $3.75 per million tokens). | Copilot in Power BI, depending on capacity and licenses; see our Excel vs Power BI comparison. | |
First boundary: the Microsoft front door
Many small businesses manage their accounts in Microsoft 365. Employees sign in everywhere with the same identity, and when someone leaves, you disable a single account. That’s single sign-on (SSO), and it’s often taken for granted.
At Metabase, that front door costs extra. The documentation is explicit, page after page: SAML authentication is “only available on Pro and Enterprise plans,” so is OIDC, and the “SAML with Microsoft Entra ID” guide carries the same notice. The free edition offers two alternatives: Google sign-in, limited to a single email domain (multiple domains require Pro), and an LDAP connection whose advanced features (group membership filter, attribute sync) are also reserved for Pro.
In practice: a company on Microsoft 365 that wants employees to sign in to Metabase with their usual account has to move to Pro, at $575 per month, before any discussion of features. Without it, you manage separate Metabase passwords and must remember to deactivate the account of everyone who leaves. That’s not a deal-breaker for a team of five analysts; it becomes one when the dashboard has to be opened to thirty branch managers.
Power BI has no such step: identity is the Microsoft 365 account. Offboarding is handled by the same procedure as email.
Second boundary: who sees what
The most common need in sales reporting isn’t a sophisticated chart. It’s that each sales rep or branch manager sees only their own scope in the same dashboard. Without that partitioning, you end up duplicating the dashboard per person and fall back into the bad habits of Excel files sent by email.
At Metabase, this partitioning is called “row and column security.” The documentation is unambiguous: it is “only available on Pro and Enterprise plans (both self-hosted and on Cloud).” The free edition and Starter let you grant or remove access to a whole database, schema or table, by group — not filter rows based on who is signed in.
In Power BI, row-level security (RLS) is included in Pro. It does have its own limit, which we covered in the Excel vs Power BI comparison: according to Microsoft Learn, it doesn’t apply to users with an Admin, Member or Contributor role in the workspace. Viewers must therefore stay viewers.
In other words, feature for feature, you have to compare Power BI Pro with Metabase Pro, not with the free edition. And the comparison flips.
Third boundary: a “user” is an account, not a person
Both vendors bill per user, and both count viewers: at Metabase, the pricing page states that the team creating analyses and the people viewing embedded dashboards “count as users.” The difference lies in how counting works, which Metabase details on its “How billing works” page.
Every day, Metabase records the maximum number of accounts present in the instance over the previous 36 hours, and adds up that maximum across all instances using the same license key. The documentation gives the example of the same email address present in two instances: it is counted twice, since the calculation works like a “COUNT” and not a “COUNT DISTINCT.” An account stops being billed only once it’s deactivated. And on paid plans, if the number of accounts drops, there’s no refund; extra accounts are billed only above the maximum already paid for.
Two traps follow. First, SSO creates accounts on its own: the SAML documentation points out that a new sign-in through the directory automatically creates a Metabase account, and that paid plans bill every additional account. Opening Metabase to the whole domain lets any curious employee add a line to the invoice. Second, a small business that sets up a test instance next to production with the same license pays for its users twice.
With Power BI, cost follows the licenses assigned in the Microsoft 365 admin center: more rigid, but also easier to read. In both cases, the management rule is the same: a quarterly account review, deactivating inactive users and leavers.
Three costed scenarios, with comparable features
The amounts below are annual license costs, excluding taxes, on an annual commitment. Each row label gives the US list prices in dollars (as of November 2026); the euro figures in bold are the France list prices from the French edition of this article (Metabase converted at the ECB rate of October 1, 2026), with Metabase’s original dollar price in parentheses. They exclude setup time and, for the free edition, the server and administration time: we come back to that just below. Every account is counted, viewers included.
| Scenario | Power BI Pro | Metabase Starter (Cloud) | Metabase Pro |
|---|---|---|---|
| 8 accounts (3 analysts, 5 executives) — US: Power BI $1,344 · Starter $1,275 · Pro $6,210 | €1,162 (8 × €145.20) | €1,129 ($1,275) | €5,497 ($6,210, 10 accounts included) |
| 25 accounts (leadership + managers) — US: Power BI $4,200 · Starter $2,380 · Pro $8,160 | €3,630 | €2,107 ($2,380) | €7,223 ($8,160) |
| 60 accounts (branch network) — US: Power BI $10,080 · Starter $4,655 · Pro $12,710 | €8,712 | €4,120 ($4,655) | €11,250 ($12,710) |
| Entra ID sign-in and row-level permissions? | Yes | No | Yes |
The takeaway is clear. Metabase Starter is cheaper than Power BI Pro from 8 accounts, and the gap widens with the number of viewers, since an extra account costs $65 a year versus $168 at Microsoft ($14 × 12, US list price). But Starter has neither Entra ID sign-in nor row-level permissions. As soon as either one is needed, Metabase Pro is the plan to compare, and Pro only becomes cheaper than Power BI Pro from about 130 accounts at US list prices as of November 2026 (about 145 accounts at the French euro prices and exchange rate).
One more factor for a business that is already equipped: if the company is on Microsoft 365 E5, Power BI Pro is included in the license (Microsoft lists it in Microsoft 365 E5 and Office 365 E5, not in the Business plans, as we noted in the comparison with Looker Studio). In that case, the marginal cost of Power BI is zero and the question almost answers itself.
The real price of self-hosting
The open-source edition is free, with unlimited accounts. That’s its decisive argument for a small business that already has a small technical team. But it isn’t cost-free, and Metabase’s own documentation says where the cost lies.
1. A proper application database. Metabase stores its questions, dashboards, accounts and settings in a so-called “application” database, separate from your data. By default, that’s an embedded H2 database, which the documentation describes as a solution for local demos, to “avoid in production.” It recommends PostgreSQL (MySQL or MariaDB also work). So you need a database to administer, back up and monitor.
2. Regular upgrades, with backups. The official procedure starts with “back up your application database.” A major upgrade changes that database’s structure; to roll back, you must restore the backup or migrate manually, otherwise Metabase may refuse to start. The pace is brisk: on October 2, 2026, the documentation’s version selector showed v0.64 as current and already marked v0.62 and earlier as “unsupported,” except v0.58, flagged “LTS.” Staying current is recurring work.
3. A runtime platform. The JAR file requires a Java environment; the Docker image is the other documented route. You also need an HTTPS certificate, a domain name and a backup policy, as for any exposed application. Our method for a data backup plan applies as is.
4. A license to read if you embed dashboards in a product. The open-source edition is licensed under the AGPL. Metabase’s licensing page states that to embed dashboards in your own application, you must either comply with the AGPL or obtain a commercial license. For internal use, the question doesn’t arise; for a software vendor that wants to offer analytics to its customers, it’s central.
Altogether, this takes a few hours a month for someone who knows Linux and PostgreSQL. If that person already exists in the company, open source is unbeatable. If not, you have to put a value on their time, and the comparison with Starter or Power BI becomes much tighter. One important point: self-hosting doesn’t lower the price of the paid features. Pro shows $575 per month in the Cloud tab and in the self-hosted tab alike. You then pay for the license and the operations.
Where does the data live?
For a business that cares about data location, Metabase offers a rare option: full self-hosting, on a server in your own country or on your premises, with no data ever leaving your infrastructure. That’s a real argument for a manufacturer, a clinic or a firm that wants no dependency on a third-party cloud (for European companies, a US cloud in particular). Our comparisons OVHcloud vs AWS and CRM SaaS vs open source cover the trade-offs of this kind of choice.
On Metabase Cloud, the documentation offers two regions: US West (Oregon) and Europe (Frankfurt). The vendor itself lists an address in California; choosing the European region settles where the data sits, not the provider’s nationality. The Cloud also has documented limits: only officially supported databases (no community drivers, no SQLite), no access to the application database, no customizing the sender address for emailed reports, and queries cut off after 20 minutes.
Power BI stores data in the region of your Microsoft 365 tenant, and Microsoft has local subsidiaries, including in France. But there’s no “everything on your premises” equivalent to Metabase’s open-source edition for sharing: the published report lives in the Microsoft service, and on-premises data flows up to it through the gateway.
Which tool for which kind of small business?
Choose Metabase Open Source if your data is already in a SQL database (business application, e-commerce, ERP on PostgreSQL or SQL Server), if someone on the team can run a server, if all viewers can see the same numbers and if Google sign-in or local accounts are enough. That’s typically a digital business, a software vendor or a company with a technical department. The license cost is zero, whatever the number of viewers.
Choose Metabase Starter if the profile is the same but nobody wants to manage a server. It’s cheaper than Power BI Pro from 8 accounts. Just check that you won’t need Microsoft sign-in or row-level permissions within the year: moving to Pro multiplies the bill.
Choose Power BI if your reporting starts from Excel files, ERP exports and SharePoint lists, if the company lives in Microsoft 365, if each manager must see only their own scope, or if you have fewer than about 130 viewers (US prices) and need those features. That’s the most common profile in manufacturing, wholesale and service businesses. Our article on optimizing cash flow with data shows this kind of dashboard.
Consider Metabase Pro if you have a large number of viewers (beyond roughly 130 accounts at US prices), if you embed dashboards in a product sold to your customers, or if self-hosting with row-level partitioning is a requirement. It’s a rarer case for small businesses, but a real one among SaaS vendors.
Finally, the two aren’t mutually exclusive. It’s common for the technical team to use Metabase to explore the production database while leadership reads consolidated Power BI reports. The danger then is having two different revenue figures: you have to decide which one is authoritative.
Method: decide in one week
1. Locate the data. List the metrics to publish and, for each one, its source: SQL database, file, online application. If more than half come from files, Power BI starts with a head start.
2. Count accounts, not people. How many authors, how many viewers, how many instances (production, test)? At Metabase, every account in every instance counts.
3. Ask the two knockout questions. Do people need to sign in with Microsoft Entra ID? Must each person see only their own scope? A single “yes” rules out Metabase’s free edition and Starter.
4. Put a value on operations. For self-hosting, estimate the monthly hours of upgrades, backups and monitoring, and multiply by a fully loaded hourly cost. Add them to the Open Source column.
5. Prototype the same dashboard in both. Metabase Open Source installs in minutes with Docker, Starter and Pro offer a 14-day trial, and Power BI Desktop is free. Rebuild your most-read metric and show it to its viewers.
If you’d like an outside view on this choice, it’s the kind of assessment we carry out in our ERP reporting and data engagements, or as part of a fractional CIO engagement.
Frequently asked questions
Is Metabase really free?
The open-source edition is free, under the AGPL license, with unlimited accounts, provided you host it yourself. You then need a server, a PostgreSQL database for the application database and time for backups and upgrades. Metabase Cloud starts at $100 per month (Starter plan, 5 accounts included).
Can you sign in to Metabase with a Microsoft 365 account?
Yes, but only on the Pro and Enterprise plans: Metabase’s documentation reserves SAML and OIDC authentication, including with Microsoft Entra ID, for those plans. The free edition offers Google sign-in on a single domain and a basic LDAP connection.
Is Metabase cheaper than Power BI?
Metabase Starter becomes cheaper than Power BI Pro from about 8 accounts, but it has neither Entra ID sign-in nor row-level permissions. With comparable features, Metabase Pro only becomes cheaper than Power BI Pro from about 130 accounts at US list prices as of November 2026 (about 145 accounts at French euro prices and the October 1, 2026 exchange rate).
Where is data hosted on Metabase Cloud?
The documentation offers two regions: US West (Oregon) and Europe (Frankfurt), selectable in the account. To keep all data on your premises or in a specific country, you need the self-hosted edition.
Can Metabase read Excel files?
Not directly, as Power BI does. Metabase connects to databases; it accepts CSV file uploads, stored free up to one million rows on the Cloud. If your reporting relies on Excel workbooks, Power BI and Power Query are a better fit.
In short
Metabase and Power BI aren’t opposed as free versus paid. They differ on where the bill starts. With Metabase, the software is free, but Microsoft 365 sign-in and per-person partitioning are reserved for Pro, at $575 per month, at the same price whether you self-host or not. With Power BI, everything is included from the first license, but every viewer pays for one.
For a small business on Microsoft 365 that reports from files and needs per-person permissions, Power BI remains the rational choice up to well over a hundred viewers. For a technical business whose data is already in a database and whose viewers all see the same numbers, Metabase Open Source or Starter is unbeatable. Last episode in the series: Qlik vs Power BI, where we discover a tool that no longer bills viewers but gigabytes. Finally, our overview of digital transformation tools for small businesses places reporting within the whole software stack, and if you’re still undecided, let’s talk.