Self-hosted Tableau alternative: own your BI with Metabase

Somewhere in your business there is a database that already knows the answer — which plan is churning, which region is growing, what last Tuesday actually looked like. The tools built to ask it questions, Tableau and Looker, have quietly become some of the most expensive software a company buys, priced per viewer so that looking at your own numbers costs more every time you add a person. Metabase is the alternative you run yourself: a real business-intelligence tool that lives on your server, right next to the data it reads.

What Metabase is

Metabase is an open-source business-intelligence platform — the same category as Tableau, Looker, and Power BI, and a genuine competitor to them. You point it at a database and it becomes the front door your whole team uses to explore it: a graphical question builder for people who don't write SQL, a proper SQL editor for people who do, dashboards anyone can read, and scheduled reports that land in an inbox.

This is not a stripped-down demo of a paid product. The open-source edition is the complete tool — connect unlimited databases, add unlimited people, build unlimited dashboards, with no seat count metering what your team is allowed to see. Where the hosted incumbents gate scheduling, embedding, and every extra viewer behind enterprise contracts, the self-hosted version just runs. The only limit is the server you give it.

The features that actually matter

• Ask questions without SQL. The notebook query builder lets anyone filter, join, group, and summarize by clicking through their data, then render the result as a table, line, bar, pivot, map, or trend. Point it at a table and Metabase can X-ray it — auto-generating an exploratory dashboard so you can see what's in a new dataset in seconds.
• A real SQL editor. For the queries the builder can't express, there's a full SQL editor with named variables, parameters, and reusable snippets, so power users are never boxed in by the visual layer.
• Dashboards that filter and drill. Combine questions onto a dashboard, wire up filter widgets, and let readers click a bar to drill straight into the rows behind it — no rebuild required.
• Alerts and subscriptions. Schedule a dashboard or question to email or Slack, or fire an alert when a number crosses a threshold. Per-recipient scheduled delivery is a paid tier on most hosted BI; here it's built in.
• Connects to the database you already have. Postgres, MySQL, SQL Server, BigQuery, Snowflake, Redshift, MongoDB, ClickHouse and more, read directly — no ETL pipeline to stand up first.
• Models. Curate a raw table into a friendly, reusable dataset with sensible column names and types, so the query builder surfaces business terms instead of schema cruft. In Looker, that semantic layer is the whole paid pitch.
• Sharing and embedding. Publish a read-only public link or embed a signed dashboard in your own app, without buying a viewer seat for every person who reads it. A client portal, an internal wiki, a status page — the dashboard goes where the people already are.

Why self-host it instead of the hosted version

Your data never leaves. Metabase reads directly from your production database, so its queries and their results are your most sensitive numbers by definition. Self-hosted, that connection stays inside your own server. Metabase Cloud and the hosted incumbents route it through infrastructure you don't control.

The cost doesn't scale per seat. Hosted BI is priced per viewer, which is exactly the wrong shape — the more useful your dashboards become, the more people want them, and the bill climbs with every one. Self-hosted Metabase is free software on a server you already pay for. The tenth reader and the hundredth cost nothing extra.

You keep control. You decide the version, the upgrade timing, and the domain. Put it behind your own authentication, on your own subdomain, styled to look like it belongs to you — not a rented tab in someone else's product. And when a vendor changes its pricing or sunsets a tier, none of it reaches you, because there's no vendor in the loop to change anything.

Who it's for

• Founders and small teams who want dashboards on their Postgres or MySQL without signing a per-seat BI contract to see their own signups.
• Agencies and consultancies building reporting for clients — a self-hosted Metabase lets you brand it, embed it, and hand over dashboards without reselling anyone else's seats.
• Internal ops and data teams who want genuine self-serve analytics for the whole company without handing production database credentials to a third-party SaaS. Organize questions into collections, set who can see what, and let people answer their own questions instead of queuing for the one person who knows SQL.

The honest setup notes

Running Metabase yourself is real infrastructure, and we'd rather be straight about it. It needs its own application database — the default embedded H2 store is fine for kicking the tires but is explicitly not for production, so you give it a dedicated Postgres for its own metadata. It runs on the JVM, which means it wants real memory; budget a gig or two of RAM rather than the scraps a small PHP app gets by on. You'll want a reverse proxy and a TLS certificate in front so it isn't answering on a bare port, and Metabase won't send a single alert until an SMTP relay is wired in. New versions ship regularly, so someone has to keep it patched and watch that an upgrade didn't break a driver. And the application database — which holds every question, dashboard, and connection you build — needs backing up, because losing it means rebuilding all of that by hand.

None of that is hard. It's just a standing chore that never ends. Or let us run it.

Deploy it in one click

Rolling your own means installing the JVM, standing up a separate application database, putting a reverse proxy and TLS in front, configuring SMTP, and then owning updates and backups forever. It's a perfectly good weekend project and a mediocre use of a Tuesday.

On Caliber Node you deploy Metabase in one click. We provision it with its own managed application database, a sensible amount of memory, TLS on your subdomain, and SMTP already wired for alerts and subscriptions. Updates and backups are handled. You get a running Metabase pointed at a fresh database and a login screen — not a checklist. From there you connect your data and start asking questions, which is the part you actually wanted to be doing.

First run

1. Open your new Metabase URL and create the admin account — name, email, and a password.
2. Add your first database connection: host, port, database name, and read-only credentials. Metabase syncs the schema automatically.
3. Once the sync finishes, X-ray any table to get an instant exploratory dashboard and confirm the connection is live.
4. Click New → Question, pick a table, and use the query builder to filter and summarize — say, signups grouped by week. Save it.
5. Drop that question onto a new dashboard, add a date filter, and set an email subscription so it lands in your inbox every Monday.

The bigger picture

Knowing what your business is actually doing shouldn't be a subscription you re-justify every time the team grows. The database is yours, the questions are yours, and the answers are yours — the software that reads them can be yours too, running on a server you control instead of metering your own curiosity by the seat. Metabase is what that looks like done properly: a serious BI tool, self-hosted, with nothing between you and your numbers. Give the whole team the dashboards, and let the bill stay flat while they do.

Deploy Metabase in a few minutes →

Or browse the full app catalog to see what else you can own instead of rent.

One-click self-hosted apps, managed for you — real logs, SFTP, and your data always exportable. Never a black box.