How to Deploy Metabase

You can deploy Metabase in two ways: self-host it with a single Docker command, or use Metabase Cloud, which offers a free trial. The self-hosted route is the fastest way to get a running instance — the official command is docker run -d -p 3000:3000 metabase/metabase, which spins up a free instance in minutes and ships with AI features. Choose Cloud instead if you'd rather not manage infrastructure yourself.

Self-hosting with Docker

This is the path Metabase documents directly on its site, and it's the quickest way to a working instance.

Prerequisites: Docker installed and running on your machine or server, and port 3000 available.

Steps:

1. Run the container:

   docker run -d -p 3000:3000 metabase/metabase
   

   • -d runs it in the background.
   • -p 3000:3000 maps port 3000 on your host to Metabase's internal port.
   • metabase/metabase is the official image.

2. Open http://localhost:3000 in your browser. You should see Metabase's setup wizard.

3. Complete the setup wizard, then connect your database or warehouse.

Expected result: A running, self-hosted Metabase instance you can log into and start querying.

Common snags:

• If port 3000 is already in use, map a different host port (for example -p 3001:3000) and visit that port instead.
• The -d flag means the container runs detached — if the page doesn't load, check that the container is actually running with docker ps.
• Because this command doesn't mount a volume, your data lives inside the container. For anything beyond a quick trial, plan where your application database will persist before you rely on it.

Metabase Cloud (hosted option)

If you don't want to run Docker or manage a server, Metabase Cloud is the hosted alternative and offers a free trial. This is the better fit when you want to skip infrastructure work and get straight to connecting data.

After deployment: connect your data and tools

Once Metabase is running, the next step is connecting your database or warehouse so you can query and visualize it. From there you can work with your data through several surfaces the site lists: the MCP server, a CLI, APIs, and Slack.

For teams, Metabase also supports a governed semantic layer in Data Studio, where you define trusted, reusable metrics and mark vetted data sources so both people and AI build on consistent foundations.

Scaling and security

Metabase is designed to start simple and scale as you grow — the site frames it as suitable "from pre-seed to post-IPO." On the security side, it states compliance with SOC1, SOC2, GDPR, CCPA, and more, so you can keep data secure and compliant as usage expands.

Which deployment should you pick?

If you just want to see Metabase working, run the Docker command. If you'd rather not maintain a server, start with the Cloud free trial. Either way, the first real task after deployment is connecting a database — that's what turns a running instance into usable analytics.