Links checked 2026-10-14
Self-hosting Metabase
The self-hosted route instead of Hosted BI tools.
Starting the container is easy. The work is on the database side: credentials, an application database you back up, and queries your warehouse can actually serve.
What it is
A business intelligence tool that connects to the database you already have and puts a question builder, SQL editor and dashboards on top of it. It runs as a single Java application or container, and it keeps its own application database for the questions and dashboards you save.
What you actually need
This is the reader's own hardware and configuration, not a price. We describe what a job needs; we do not put a figure on what self-hosting costs, because that depends on the provider, the term and the disk you choose.
- The server
- A VPS with enough memory for the Java application. Query work happens on the database you connect it to, not on this machine.
- How it installs
- The published container image, or the application JAR run directly. The project's Docker page is the documented path.
- Data store
- Metabase keeps an application database of its own for saved questions, dashboards and users. The project's Docker page states that it ships with an embedded file-based database and that a production install should use a production-ready database such as PostgreSQL instead.
- What grows
- The application database plus whatever your data warehouse already holds. Metabase reads your data where it lives.
Before it is safe to expose
- Read-only credentials for the databases you connect it to
- A reverse proxy and TLS, since dashboards are often shared
- A backup of the Metabase application database, which is the part people forget
The trade-offs, specifically for Metabase
- Metabase's documentation includes activating a commercial licence, so some features sit behind one. Check which you need before you plan around the install.
- The application database is a real dependency: lose it and every saved question and dashboard is gone, even though your underlying data is untouched.
- Dashboard performance is your database's performance. Metabase hands the query over and waits.
- Upgrades migrate the application database, and the project's documentation tells you to take a backup first for that reason.
And the six things you own from now on
These are true of every tool in this section, including Metabase. They are also the reason to decide against self-hosting, which is a legitimate decision.
- You own the updates. Security releases have to be applied by you, on your schedule, and a project that stops publishing releases becomes your problem to notice.
- You own the backups, and a backup is not a backup until you have restored from it once.
- You own the uptime. There is no status page to watch and no support line to call when it stops answering.
- You own the security patches, the TLS certificate, the reverse proxy and the firewall in front of it.
- You are the on-call rota. The failure mode nobody plans for is being the only person who knows how the thing was set up.
- The hardware has a running cost and a lifetime. Disks fail, and the replacement is on you.
What you give up
- A managed BI service's hosting, upgrades and support
- The features reserved for the commercial edition
What you gain
- Dashboards over data that never leaves your infrastructure
- No per-user subscription for the open-source edition
Elsewhere in the index
The box it runs on
A VPS with enough memory for the Java application. Query work happens on the database you connect it to, not on this machine. That machine is the purchase this page is really about, and it is the one number we will not invent for you: the right size depends on the provider, the term and the disk, so check it on the provider's own page.
Hostinger
Hostinger's VPS product is the closest fit to a self-hosted application: its own page advertises root access, Docker and NVMe storage, with data centres in several regions.
See Hostinger's plansRead Hostinger's published pricing ↗DigitalOcean
Virtual machines billed as you use them, with separate volumes, snapshots and object storage for the parts you want to keep outside the server.
See DigitalOcean's plansRead DigitalOcean's published pricing ↗Hetzner
Cloud instances and dedicated servers with rates published per instance size, so the cost of a bigger box is visible before you move.
See Hetzner's plansRead Hetzner's published pricing ↗What to check before you buy
- A virtual machine you have root on, not a website plan with a control panel bolted on top.
- Snapshots or automated backups, and where those backups are stored.
- Block storage or object storage for the data that will outgrow the server's own disk.
- What the monthly rate renews at, rather than the first-term rate on the signup page.
- Where the data centre is, if the data has a jurisdiction attached to it.
The “See plans” links go through our own /go/ redirect and some are affiliate links, which pay us if you sign up. The descriptions and trade-offs on this page are written from the project's own documentation and are unaffected. The plain pricing link under each provider is not an affiliate link. See our disclosure.
Frequently asked questions about self-hosting Metabase
Answers restate the notes on this page or point at the project's own documentation. Self-hosting moves work to you rather than removing it, and these answers say so.
What is Metabase?
A business intelligence tool that connects to the database you already have and puts a question builder, SQL editor and dashboards on top of it. We cover it as a replacement for Hosted BI tools.
What do you need to run Metabase yourself?
The published container image, or the application JAR run directly. The project's Docker page is the documented path. The requirements table on this page lists the server, the data store, what grows and what else to arrange first. Setup steps are at Metabase's Docker installation guide.
How hard is Metabase to run yourself?
We rate it Moderate. Starting the container is easy. The work is on the database side: credentials, an application database you back up, and queries your warehouse can actually serve.
What are the trade-offs of self-hosting Metabase?
Our notes list these costs. Metabase's documentation includes activating a commercial licence, so some features sit behind one. Check which you need before you plan around the install. The application database is a real dependency: lose it and every saved question and dashboard is gone, even though your underlying data is untouched.
What do you give up by running Metabase yourself?
You take on what Hosted BI tools used to do for you. A managed BI service's hosting, upgrades and support. The features reserved for the commercial edition. Self-hosting moves that work to you rather than removing it.
What do you gain by running Metabase yourself?
Our notes list these. Dashboards over data that never leaves your infrastructure. No per-user subscription for the open-source edition.