Explainer · Data

What is Metabase, and is it a business fit for your company?

A plain-English guide to Metabase, the open-source tool that turns questions about your data into dashboards. It covers who can use it, what it really costs and when it fits.

Published Reviewed 9 min read

Monday morning. Someone on your team is rebuilding the same sales spreadsheet for the third week running, pulling numbers from three different sources to get a chart that looks roughly right. You've heard Metabase might be free. So what is Metabase? It's an open-source business intelligence (BI) tool that connects to your existing database and turns questions into interactive dashboards without requiring code for day-to-day work. One boundary: it reads from a database; it doesn't store or clean the data itself.

What Metabase actually is

Metabase is an open-source platform designed for asking questions about your data and building visual answers. You connect it to a tidy source, like a relational database or cloud warehouse, then use its interface to explore what the numbers say. It handles the asking, charting, and sharing, but not the plumbing underneath.

The moving parts

The tool gives you two ways to get answers. A point-and-click query builder lets you select fields, filter rows, and pick visual types without typing code. An SQL editor exists for anyone who wants to write native queries directly against the database. Most non-technical users will live entirely in the first option.

Once questions are answered, you assemble them into interactive dashboards that update as underlying data changes. Share these internally by link, or embed them into other applications if customers need to explore their own slice of data. The flow is connect, ask, build, share.

Where it stops being helpful on its own

Here's the part vendor documentation sometimes buries: Metabase assumes the data it reads from is structured and trustworthy. If your "database" is a tangle of CSV exports, mismatched columns, and numbers that mean different things in each tab, Metabase will faithfully chart that mess. It doesn't reconcile sources or enforce consistent definitions across teams.

That layer, a tidy underlying data store with agreed metrics, is where most projects need help before pointing Metabase at anything useful.

Who can use it without knowing SQL?

This is the question every owner asks. The answer depends on which half of the product you're looking at. The query builder is genuinely click-through: select a table, drag in fields, set filters, choose a chart type. You don't need to know what a join is or how to write WHERE clauses. For day-to-day use, like building a weekly sales dashboard or drilling into regional performance, that's enough.

But someone still has to do the first setup. Connecting Metabase to your database, creating models so non-technical users see clean field names instead of cryptic column IDs, and deciding which questions become standard dashboards require basic technical comfort. They do it once, maybe twice as needs evolve, then the rest of the team clicks through.

The SQL editor sits alongside the query builder for those who want custom queries directly. It's there if you need it, but nobody has to use it just to get a working dashboard up. If your only question is "can my operations manager build a weekly report without writing code," the vendor's feature list says yes, through their GUI tools. We won't tell you how easy that experience feels for every user; that depends on how clean your underlying data models are and whether someone has set them up clearly.

A practical split of responsibility

In a typical setup:

  • One technical person (internal or contracted) handles initial connection, model creation, and any custom SQL queries that can't be built through clicks
  • Non-technical staff use the query builder to create ad-hoc questions and save them as dashboard tiles
  • Everyone with access views shared dashboards and filters by department, date range, or product line

That split works well when one person owns the "how" so others focus on the "what." If you're looking for a tool where everyone does everything from scratch, that's not really how this is designed.

Open source, Cloud, or self-hosted: what's the difference?

Metabase offers several ways to run it, and the naming gets confusing fast. Let's untangle them.

The editions

There's a free open-source edition anyone can download without licence fees. Above that are paid versions, which add single sign-on (SSO), row-level permissions so different users see only allowed data, and additional customisation options. The open-source edition gives you core dashboarding and query tools; paid versions layer on access control, integration, and support.

How you run it

You have three hosting routes: run it as a JAR file on your own servers, deploy it using Docker containers, or subscribe to Metabase Cloud where they host everything for you. The choice matters more than the edition in some ways because self-hosting carries ongoing responsibilities that Cloud removes.

What "free" actually costs when you self-host

This is where the sticker price of zero hides real expenses. If you take the open-source version and run it yourself, Metabase's documentation lists what falls to you: support via their public forum only (paid plans include direct support), manual upgrades whenever a new release comes out, manual backups if you want any safety net, manual monitoring so you know when something breaks, and managing your SSL certificate for secure connections. None of those are trivial. Each is a recurring task that needs a person with the time and skill to do it properly.

Metabase Cloud removes most of that burden: they handle hosting, updates, security patches, and provide direct support. The trade-off is monthly fees per user, which we'll cover next, plus one limitation worth knowing upfront. Metabase Cloud only supports official database drivers they've vetted for quality; if you need a community-built or custom connector, you'll have to self-host.

What does it cost?

All published prices are in US dollars, billed monthly or annually, so flag that before comparing them against any GBP budget. At the time of writing:

PlanBase priceExtra users includedPer additional user/month
Starter$100 / month ($1,080/year)First 5 users$6 per user
Pro$575 / month ($6,210/year)First 10 users$12 per user

One rule that trips people up: everyone who signs in counts as a licensed user, including anyone accessing your embedded dashboards through their own login. Guest embeds, where viewers don't sign in at all, don't count against your seat total. So if you're embedding charts into a customer-facing portal and those customers log in individually, each one is a billable user.

Infrastructure costs for self-hosting

If you go the open-source route on your own servers, there's no licence fee, but you do need to pay for hosting, whether that's a virtual machine at a cloud provider or a physical server in your office. Metabase notes that infrastructure costs are difficult to estimate precisely and publishes ballpark figures as comparable setups across other cloud providers. Those numbers vary widely based on data volume, how many people use it daily, and what performance you need from queries.

The real cost of the free edition

Self-hosting suits teams that enjoy managing Linux servers, taking backups, testing upgrades in a staging environment, and renewing SSL certificates before they expire; for them, the open-source edition is economical. For everyone else, that description reads like a chore you’d rather outsource or avoid entirely, so factor Metabase Cloud fees or an external support retainer into your total cost of ownership. The free version only stays free if setup and upkeep time are worth zero to you.

Is it the right fit for your business?

We'll be straight with you: Metabase shines when you already have a clean, queryable data source and want shared dashboards without paying per-seat enterprise licence fees that scale painfully as your team grows. It's a sensible choice if your main pain is "we have the numbers in our database but nobody outside IT can look at them."

It falls short when your data lives scattered across spreadsheets, disconnected apps, and email exports with nothing centralised for Metabase to connect to. Pointing it at a messy pile of CSVs just creates prettier versions of inconsistent numbers. Before you pick a BI tool, make sure the layer underneath can answer the same question the same way every time. That foundation is what we call the tidy data layer Metabase reads from, and getting it right changes everything about how useful your dashboards become.

In practice · Case study

Building a Data Warehouse

Turning five disconnected platforms into one source of truth.

Read the case study
8+platforms connected into one warehouse
Minutesto generate any cross-platform report

If you’re weighing Metabase against other reporting platforms, know that comparing it with tools like Looker Studio or Power BI is a separate decision we haven’t gathered evidence for on this page. The core question remains: do you have a reliable data source to point at, and do you need shared dashboards more than complex multi-tenant analytics? If yes, Metabase is worth trying.

What should you do next?

Start with five concrete questions your business asks every week about its numbers: "How much did we sell last month by region?" "Which products are losing margin?" "Where are our customers getting stuck in onboarding?" Write them down and note where each answer lives today. If those answers require pulling from three or more systems, you have a data integration problem before you have a dashboarding problem; solving that first will make any BI tool far more useful.

Once you know your data is queryable from one place, try Metabase itself. They offer a free trial of their Cloud version so you can connect to a copy of your data and build a sample dashboard without committing to infrastructure. If you'd rather skip the setup entirely and just have someone connect your sources, agree on metric definitions, and hand over working dashboards with clear access controls, that's exactly what our data team does when connecting data and setting up dashboards. Bring those five questions to a call; we can tell you honestly whether Metabase is the right layer for what you need, or whether there's groundwork to do first.

Does this apply to you?

Probably not yet

With none or one of these, a spreadsheet or your current reporting tool may still be enough.

See how we work

Key terms

business intelligence
Business intelligence, or BI, is the set of tools that turn company data into charts, reports and dashboards for decisions. Metabase is one such tool.
open-source
Software whose code is publicly available, so anyone can download and use it. Metabase's free edition works this way, with paid plans on top.
self-hosting
Running the software on servers you provide and maintain, rather than paying the vendor to host it. You then own the upkeep.
SQL
The standard language for asking questions of a database. Metabase includes an SQL editor for people who want to write queries directly.
single sign-on (SSO)
A setup where people sign in once with one company login and then reach several tools without separate passwords.
dashboard
A single page of charts and figures built from your data, which updates as the underlying data changes.

Frequently asked questions

Is Metabase really free?

The open-source edition is free to download and use. Running it yourself means providing servers and handling upgrades, backups, monitoring and SSL certificates, so the time cost is real. Paid Cloud plans are priced per month in US dollars, starting at $100 for Starter.

What is Metabase used for?

You use it to ask questions of your data and turn the answers into charts, dashboards and links you can share. Teams can also embed charts in their own products, so customers can explore their own figures.

Do I need a developer to set up Metabase?

Usually, yes, for the first connection. Someone technical also builds the models that give fields clear names. After that, most staff can work through the query builder, and Cloud is the quicker route to a working setup.

Can Metabase connect to any database?

Not on Metabase Cloud. Cloud supports only official database drivers that Metabase has vetted for quality. If you need a community or custom driver, you will have to self-host.

How many users can I have?

It depends on the plan. Starter includes 5 users and Pro includes 10, with extra users charged per month in US dollars. Anyone who signs in counts as a user, including people who sign in to embeds, but guest embed viewers do not.

Sources

  1. Metabase documentation, Metabase (accessed 13 Nov 2026)
  2. Metabase plans, Metabase (accessed 13 Nov 2026)
  3. Metabase Cloud versus self-hosting, Metabase (accessed 13 Nov 2026)

Your data

Not sure if Metabase fits your data?

Bring your five weekly questions to a free 20-minute call. We'll tell you honestly whether Metabase is the right layer, or whether there's groundwork to do first.

Book a free 20-min call

No commitment · No sales pressure · Just clarity