See all articles

Internal dashboards: build them in your app or add Metabase

Build internal dashboards in your app when a few people need a few fixed numbers that your code already computes. Add Metabase when your ops, sales or support teams ask new questions every week, or when several teams want their own dashboards. It also fits when people who don’t write SQL want to explore the data and get a weekly email. Metabase connects to your app’s own PostgreSQL or MySQL database with a read-only user, so you don’t need a data warehouse or a pipeline first.

The open-source edition is free to self-host with unlimited users, and it runs as one Docker container. Metabase Cloud Starter costs $100 a month with 5 users included, and Metabase handles setup, backups and upgrades. Every plan, including the free one, can email a dashboard or post it in Slack every week. Prices and plans on this page were checked on November 12, 2026.

When is a page of numbers in your app enough?

A page in your app is enough when a few people check a fixed set of numbers, your code already computes them, and nobody asks for new breakdowns. A support lead who checks open tickets, or a founder who checks this week’s orders, is well served by an admin page. That page reuses your app’s sign-in and permissions, and it needs no new service, database user or bill.

Each number on the page is a query, an endpoint and a chart, and on PostgreSQL a weekly count is one statement:

-- Orders per week: this week and the 11 full weeks before it.
SELECT date_trunc('week', created_at) AS week,
       count(*) AS orders
FROM orders
WHERE created_at >= date_trunc('week', now()) - interval '11 weeks'
GROUP BY 1
ORDER BY 1;

A chart library such as Chart.js, which is open source under the MIT license, loads from a script tag and draws the result.

Watch for requests that repeat: one more filter, a breakdown by plan, a CSV export, the same page for another team, or a Monday email. Each one is code that you write, review, test and deploy, and each new team that uses the page brings its own requests. A steady stream of these requests is the sign that a BI tool will save you time.

When does adding Metabase save your team time?

Metabase saves time when the questions change faster than you can ship code, and these cases come up most often:

  • Questions that change every week. In the query builder, people pick data, join tables, filter, summarize and chart without writing SQL. On those charts, drill-through lets them click a point to see the records behind it. Your SQL keeps working too: the weekly query above works as it is in the SQL editor. A dashboard filter can change several cards at once.
  • Several teams. Permissions go to groups, so each team gets a group and a collection for its dashboards. Collection permissions decide which dashboards a group sees, and Create queries permissions decide which tables it can use in the query builder and whether it can write SQL. Both come with every edition, and so does Google sign-in.
  • Weekly emails. Dashboard subscriptions send a dashboard by email or Slack every hour, day, week or month, as the section on weekly emails below explains.
  • People who don’t write SQL. Metabot, the AI assistant in Metabase, creates charts from questions in plain English, and it’s on every plan with your own AI provider. Each chart that Metabot creates is a question that you can open in the query builder or the SQL editor, so you can check the query behind it.
  • One definition for each number. Define a number such as monthly recurring revenue (MRR) once as a metric, and people pick it in the query builder. When you edit the metric, every question that uses it switches to the new definition right away.

Can your coding agent build the dashboards in Metabase?

Yes. The Metabase MCP server, on every plan, gives AI clients such as Claude Code or Cursor tools to create questions, dashboards, alerts and dashboard subscriptions. Every tool works with the permissions of the person who connects. When you connect, a consent page lists the permissions that the client asks for, such as creating content or running SQL. None of them goes beyond what you can do in Metabase yourself. The client brings its own model, so you don’t need an AI provider in Metabase for this.

If you’d rather script the setup, the Metabase API creates database connections, questions, dashboards and subscriptions on every edition. On Pro and Enterprise, Remote Sync keeps dashboards and questions as YAML files in Git.

Do I have to run another service?

Yes, Metabase is its own service, and you choose who hosts it. On Metabase Cloud, Metabase manages the server, uptime, backups and every upgrade, from $100 a month on Starter.

To self-host, run one container from the official Docker image, which works on any system that runs Docker. In production, Metabase keeps its users, questions and dashboards in an application database. Metabase recommends PostgreSQL for it, on a database instance used for nothing else. Plan for at least 1 CPU core and 1 GB of RAM, plus 1 CPU and 2 GB for every 20 people who use Metabase at the same time. This command from the Docker docs, pinned to v0.65.4.1, starts Metabase with a PostgreSQL application database:

docker run -d -p 3000:3000 \
  -e "MB_DB_TYPE=postgres" \
  -e "MB_DB_DBNAME=metabaseappdb" \
  -e "MB_DB_PORT=5432" \
  -e "MB_DB_USER=name" \
  -e "MB_DB_PASS=password" \
  -e "MB_DB_HOST=my-database-host" \
  --name metabase metabase/metabase:v0.65.4.1

Create an empty metabaseappdb database on that PostgreSQL server first, and Metabase creates its tables in it on the first start. Replace the tag with the newest release in the Metabase 65 changelog, which lists the Docker image for each release. For a compose file, the encryption key, backups and upgrades, follow Run Metabase in production with Docker. If you start on open source, you can move to Metabase Cloud later and keep your questions, dashboards, people and settings. The recipes for Rails, Django, Next.js and Go apps walk through the setup for each stack.

How does Metabase reach the app’s database safely?

Metabase doesn’t copy your tables, because your database does the work of each query. Of your data, Metabase keeps only the metadata it syncs, samples of column values for filter dropdowns, and any cached results. Four choices keep that access safe for a production database.

Give Metabase a read-only database user

Metabase recommends a dedicated database user with read-only access to the tables you analyze. Grant only the tables your teams need, and leave out tables that hold password hashes, tokens or other secrets. On PostgreSQL, run these statements as an admin, with your own table names:

-- Run as an admin on the app's database.
-- Adapted from "Database users, roles, and privileges" in the Metabase docs.
CREATE ROLE analytics;
GRANT CONNECT ON DATABASE app_production TO analytics;
GRANT USAGE ON SCHEMA public TO analytics;

-- Grant the tables your teams need. Leave out tables with password hashes or tokens.
GRANT SELECT ON public.orders, public.customers, public.tickets TO analytics;

CREATE USER metabase WITH PASSWORD 'use-a-long-random-password';
GRANT analytics TO metabase;

A table that you add later stays unreadable to this user until you grant it. On MySQL, the same setup is a user with SELECT on each table:

-- Run as an admin on the app's MySQL server.
-- Adapted from the MySQL connection page in the Metabase docs.
CREATE USER 'metabase'@'%' IDENTIFIED BY 'use-a-long-random-password';
GRANT SELECT ON app_production.orders TO 'metabase'@'%';
GRANT SELECT ON app_production.customers TO 'metabase'@'%';
GRANT SELECT ON app_production.tickets TO 'metabase'@'%';

Then go to Admin > Databases and click Add database. MySQL 8 and later give this user the caching_sha2_password plugin, which needs a secure connection to check the password. Turn on Use a secure connection (SSL) in the connection form, or on MySQL 8.0 follow Connecting to MySQL 8+ servers.

Use a read replica when long queries could slow the app

Metabase’s guide to making dashboards faster suggests a replica as an analytics-only database, so long-running queries don’t affect the day-to-day work of your production database. A replica accepts only reads and copies changes from the primary asynchronously, so its numbers can be a little behind the app. On a PostgreSQL replica, changes from the primary can cancel a long query. For a replica that serves dashboards, the PostgreSQL docs suggest a high max_standby_streaming_delay. Create the read-only user on the primary, and the replica receives it with the other changes.

Metabase’s post You don’t need a data warehouse describes the same path. Start by querying your production database, and when queries get big, move them to a replica. On PostgreSQL, you can add materialized views on the primary for the heaviest queries, and the replica receives them with the other changes.

Let Metabase Cloud in, or keep the database private

Metabase Cloud connects to your database from three fixed IP addresses in each region. If your database has a public endpoint, allow your region’s addresses on the database port, as listed in Metabase Cloud IP addresses.

If the database has no public endpoint, use an SSH tunnel, which is available on every Metabase Cloud plan. Turn on Use an SSH tunnel in the connection form, and Metabase connects through a bastion host that you set to accept SSH only from those addresses. A self-hosted Metabase in the same private network reaches the database’s private address, like your app does. Dashboards on a private database: SSH tunnel or VPC covers both options step by step.

Choose when Metabase reads metadata

By default, Metabase does a light schema sync every hour and a daily scan of field values for filter dropdowns. On a busy database, you can schedule both in the connection’s advanced options, for example at night. On every plan, a default caching policy can also serve stored results for slow questions.

How do weekly emails to the team work?

Dashboard subscriptions send the results of a dashboard’s questions by email or Slack, hourly, daily, weekly or monthly. You pick the time, and the day for weekly and monthly sends. Email recipients don’t need a Metabase account, and subscriptions come with every plan, including the free open-source edition.

An admin sets up email or Slack once, and then people can create their own subscriptions. Metabase Cloud manages an email server for you, and a self-hosted Metabase uses your SMTP server, set in Admin > Settings > Email. Recipients see the data that the subscription’s creator can see, because Metabase uses the creator’s permissions.

An email can attach results as .csv or .xlsx files, and any subscription can attach a PDF of the dashboard. Metabase can also skip the send when the questions return no results. On Pro and Enterprise, each subscription can set its own filter values, so one dashboard can send the support view to support and the sales view to sales.

In your app, the same email needs a scheduler, an HTML template, chart images, an email provider, a Slack app and a recipient list that you maintain. A job in your app still makes sense when the message is part of your product, such as a weekly summary for each customer about their own account. Dashboard subscriptions: send weekly reports by email or Slack shows the setup in the UI and through the API.

If you compare weekly numbers between your app and Metabase, check where each week starts, because date_trunc('week', ...) in PostgreSQL starts weeks on Monday. On a timestamptz column, date_trunc also uses the session’s time zone. To get the same weeks in your app and in Metabase, pass the zone, as in date_trunc('week', created_at, 'UTC'). The query builder starts weeks on Sunday until an admin changes First day of the week in Admin > Settings > Localization, a setting that doesn’t change SQL questions.

What does it cost? Metabase pricing in 2026

Building in your app has no license fee, and you pay in developer time for each chart, filter, export and email. Metabase prices by plan and by user, and it costs the same no matter how many dashboards you build or queries you run.

PlanPrice (checked 2026-11-12)What it adds for internal dashboards
Open SourceFree, self-hosted, unlimited usersQuery builder, SQL editor, dashboards, email and Slack subscriptions (email through your SMTP server), Metabot with your own AI provider, MCP server
Starter$100 a month, or $90 a month billed yearly, with 5 users included, then $6 per user a monthThe open-source features on Metabase Cloud, with hosting, backups, upgrades, managed email and 3-day support
Pro$575 a month, or $517.50 a month billed yearly, with 10 users included, then $12 per user a monthSAML, JWT and OIDC sign-in, row and column security, filter values for each subscription, Remote Sync and usage analytics, on Cloud or self-hosted
EnterpriseFrom $20,000 a yearPro features with custom pricing, a dedicated success engineer and a 1-day support SLA

Paid plans count user accounts, and people who only receive the weekly email don’t need one. Starter and Pro start with a 14-day free trial.

Build or add Metabase: a short checklist

  • Build a page in your app when a few people check a few fixed numbers that your code already computes, and nobody asks for new filters, exports or emails.
  • Add Metabase open source, free on one container, when several teams ask new questions every week or people who don’t write SQL want to explore.
  • Use dashboard subscriptions, on every plan, when the team wants a weekly email or Slack post.
  • Choose Metabase Cloud Starter, at $100 a month, when you’d rather not run another service.
  • Connect with a read-only user limited to the tables your teams need, and use a read replica if long queries could slow the app.
  • Choose Pro when you need SAML, JWT or OIDC sign-in, row and column security, filter values for each subscription, or dashboards in Git.

Next steps

# Internal dashboards: build them in your app or add Metabase

Build internal dashboards in your app when a few people need a few fixed numbers that your code already computes. Add Metabase when your ops, sales or support teams ask new questions every week, or when several teams want their own dashboards. It also fits when people who don't write SQL want to explore the data and get a weekly email. Metabase connects to your app's own PostgreSQL or MySQL database with a read-only user, so you don't need a data warehouse or a pipeline first.

The open-source edition is free to self-host with unlimited users, and it runs as one Docker container. Metabase Cloud Starter costs $100 a month with 5 users included, and Metabase handles setup, backups and upgrades. Every plan, including the free one, can email a dashboard or post it in Slack every week. Prices and plans on this page were checked on November 12, 2026.

## When is a page of numbers in your app enough?

A page in your app is enough when a few people check a fixed set of numbers, your code already computes them, and nobody asks for new breakdowns. A support lead who checks open tickets, or a founder who checks this week's orders, is well served by an admin page. That page reuses your app's sign-in and permissions, and it needs no new service, database user or bill.

Each number on the page is a query, an endpoint and a chart, and on PostgreSQL a weekly count is one statement:

```sql
-- Orders per week: this week and the 11 full weeks before it.
SELECT date_trunc('week', created_at) AS week,
       count(*) AS orders
FROM orders
WHERE created_at >= date_trunc('week', now()) - interval '11 weeks'
GROUP BY 1
ORDER BY 1;
```

A chart library such as Chart.js, which is open source under the MIT license, loads from a script tag and draws the result.

Watch for requests that repeat: one more filter, a breakdown by plan, a CSV export, the same page for another team, or a Monday email. Each one is code that you write, review, test and deploy, and each new team that uses the page brings its own requests. A steady stream of these requests is the sign that a BI tool will save you time.

## When does adding Metabase save your team time?

Metabase saves time when the questions change faster than you can ship code, and these cases come up most often:

- **Questions that change every week.** In the query builder, people pick data, join tables, filter, summarize and chart without writing SQL. On those charts, drill-through lets them click a point to see the records behind it. Your SQL keeps working too: the weekly query above works as it is in the SQL editor. A dashboard filter can change several cards at once.
- **Several teams.** Permissions go to groups, so each team gets a group and a collection for its dashboards. Collection permissions decide which dashboards a group sees, and Create queries permissions decide which tables it can use in the query builder and whether it can write SQL. Both come with every edition, and so does Google sign-in.
- **Weekly emails.** Dashboard subscriptions send a dashboard by email or Slack every hour, day, week or month, as the section on weekly emails below explains.
- **People who don't write SQL.** Metabot, the AI assistant in Metabase, creates charts from questions in plain English, and it's on every plan with your own AI provider. Each chart that Metabot creates is a question that you can open in the query builder or the SQL editor, so you can check the query behind it.
- **One definition for each number.** Define a number such as monthly recurring revenue (MRR) once as a metric, and people pick it in the query builder. When you edit the metric, every question that uses it switches to the new definition right away.

## Can your coding agent build the dashboards in Metabase?

Yes. The Metabase MCP server, on every plan, gives AI clients such as Claude Code or Cursor tools to create questions, dashboards, alerts and dashboard subscriptions. Every tool works with the permissions of the person who connects. When you connect, a consent page lists the permissions that the client asks for, such as creating content or running SQL. None of them goes beyond what you can do in Metabase yourself. The client brings its own model, so you don't need an AI provider in Metabase for this.

If you'd rather script the setup, the Metabase API creates database connections, questions, dashboards and subscriptions on every edition. On Pro and Enterprise, Remote Sync keeps dashboards and questions as YAML files in Git.

## Do I have to run another service?

Yes, Metabase is its own service, and you choose who hosts it. On Metabase Cloud, Metabase manages the server, uptime, backups and every upgrade, from $100 a month on Starter.

To self-host, run one container from the official Docker image, which works on any system that runs Docker. In production, Metabase keeps its users, questions and dashboards in an application database. Metabase recommends PostgreSQL for it, on a database instance used for nothing else. Plan for at least 1 CPU core and 1 GB of RAM, plus 1 CPU and 2 GB for every 20 people who use Metabase at the same time. This command from the Docker docs, pinned to `v0.65.4.1`, starts Metabase with a PostgreSQL application database:

```bash
docker run -d -p 3000:3000 \
  -e "MB_DB_TYPE=postgres" \
  -e "MB_DB_DBNAME=metabaseappdb" \
  -e "MB_DB_PORT=5432" \
  -e "MB_DB_USER=name" \
  -e "MB_DB_PASS=password" \
  -e "MB_DB_HOST=my-database-host" \
  --name metabase metabase/metabase:v0.65.4.1
```

Create an empty `metabaseappdb` database on that PostgreSQL server first, and Metabase creates its tables in it on the first start. Replace the tag with the newest release in the [Metabase 65 changelog](/changelog/65), which lists the Docker image for each release. For a compose file, the encryption key, backups and upgrades, follow [Run Metabase in production with Docker](/articles/run-metabase-in-production-with-docker). If you start on open source, you can move to Metabase Cloud later and keep your questions, dashboards, people and settings. The recipes for [Rails](/articles/dashboards-for-rails-apps), [Django](/articles/dashboards-for-django-apps), [Next.js](/articles/dashboards-for-nextjs-apps) and [Go](/articles/dashboards-for-go-apps) apps walk through the setup for each stack.

## How does Metabase reach the app's database safely?

Metabase doesn't copy your tables, because your database does the work of each query. Of your data, Metabase keeps only the metadata it syncs, samples of column values for filter dropdowns, and any cached results. Four choices keep that access safe for a production database.

### Give Metabase a read-only database user

Metabase recommends a dedicated database user with read-only access to the tables you analyze. Grant only the tables your teams need, and leave out tables that hold password hashes, tokens or other secrets. On PostgreSQL, run these statements as an admin, with your own table names:

```sql
-- Run as an admin on the app's database.
-- Adapted from "Database users, roles, and privileges" in the Metabase docs.
CREATE ROLE analytics;
GRANT CONNECT ON DATABASE app_production TO analytics;
GRANT USAGE ON SCHEMA public TO analytics;

-- Grant the tables your teams need. Leave out tables with password hashes or tokens.
GRANT SELECT ON public.orders, public.customers, public.tickets TO analytics;

CREATE USER metabase WITH PASSWORD 'use-a-long-random-password';
GRANT analytics TO metabase;
```

A table that you add later stays unreadable to this user until you grant it. On MySQL, the same setup is a user with `SELECT` on each table:

```sql
-- Run as an admin on the app's MySQL server.
-- Adapted from the MySQL connection page in the Metabase docs.
CREATE USER 'metabase'@'%' IDENTIFIED BY 'use-a-long-random-password';
GRANT SELECT ON app_production.orders TO 'metabase'@'%';
GRANT SELECT ON app_production.customers TO 'metabase'@'%';
GRANT SELECT ON app_production.tickets TO 'metabase'@'%';
```

Then go to **Admin > Databases** and click **Add database**. MySQL 8 and later give this user the `caching_sha2_password` plugin, which needs a secure connection to check the password. Turn on **Use a secure connection (SSL)** in the connection form, or on MySQL 8.0 follow [Connecting to MySQL 8+ servers](/docs/latest/databases/connections/mysql#connecting-to-mysql-8-servers).

### Use a read replica when long queries could slow the app

Metabase's guide to [making dashboards faster](/learn/metabase-basics/administration/administration-and-operation/making-dashboards-faster) suggests a replica as an analytics-only database, so long-running queries don't affect the day-to-day work of your production database. A replica accepts only reads and copies changes from the primary asynchronously, so its numbers can be a little behind the app. On a PostgreSQL replica, changes from the primary can cancel a long query. For a replica that serves dashboards, the PostgreSQL docs suggest a high `max_standby_streaming_delay`. Create the read-only user on the primary, and the replica receives it with the other changes.

Metabase's post [You don't need a data warehouse](/blog/no-data-warehouse-necessary) describes the same path. Start by querying your production database, and when queries get big, move them to a replica. On PostgreSQL, you can add materialized views on the primary for the heaviest queries, and the replica receives them with the other changes.

### Let Metabase Cloud in, or keep the database private

Metabase Cloud connects to your database from three fixed IP addresses in each region. If your database has a public endpoint, allow your region's addresses on the database port, as listed in [Metabase Cloud IP addresses](/docs/latest/cloud/ip-addresses-to-whitelist).

If the database has no public endpoint, use an SSH tunnel, which is available on every Metabase Cloud plan. Turn on **Use an SSH tunnel** in the connection form, and Metabase connects through a bastion host that you set to accept SSH only from those addresses. A self-hosted Metabase in the same private network reaches the database's private address, like your app does. [Dashboards on a private database: SSH tunnel or VPC](/articles/dashboards-on-a-private-database) covers both options step by step.

### Choose when Metabase reads metadata

By default, Metabase does a light schema sync every hour and a daily scan of field values for filter dropdowns. On a busy database, you can schedule both in the connection's advanced options, for example at night. On every plan, a default caching policy can also serve stored results for slow questions.

## How do weekly emails to the team work?

Dashboard subscriptions send the results of a dashboard's questions by email or Slack, hourly, daily, weekly or monthly. You pick the time, and the day for weekly and monthly sends. Email recipients don't need a Metabase account, and subscriptions come with every plan, including the free open-source edition.

An admin sets up email or Slack once, and then people can create their own subscriptions. Metabase Cloud manages an email server for you, and a self-hosted Metabase uses your SMTP server, set in **Admin > Settings > Email**. Recipients see the data that the subscription's creator can see, because Metabase uses the creator's permissions.

An email can attach results as .csv or .xlsx files, and any subscription can attach a PDF of the dashboard. Metabase can also skip the send when the questions return no results. On Pro and Enterprise, each subscription can set its own filter values, so one dashboard can send the support view to support and the sales view to sales.

In your app, the same email needs a scheduler, an HTML template, chart images, an email provider, a Slack app and a recipient list that you maintain. A job in your app still makes sense when the message is part of your product, such as a weekly summary for each customer about their own account. [Dashboard subscriptions: send weekly reports by email or Slack](/articles/scheduled-email-slack-reports) shows the setup in the UI and through the API.

If you compare weekly numbers between your app and Metabase, check where each week starts, because `date_trunc('week', ...)` in PostgreSQL starts weeks on Monday. On a `timestamptz` column, `date_trunc` also uses the session's time zone. To get the same weeks in your app and in Metabase, pass the zone, as in `date_trunc('week', created_at, 'UTC')`. The query builder starts weeks on Sunday until an admin changes **First day of the week** in **Admin > Settings > Localization**, a setting that doesn't change SQL questions.

## What does it cost? Metabase pricing in 2026

Building in your app has no license fee, and you pay in developer time for each chart, filter, export and email. Metabase prices by plan and by user, and it costs the same no matter how many dashboards you build or queries you run.

| Plan | Price (checked 2026-11-12) | What it adds for internal dashboards |
| --- | --- | --- |
| Open Source | Free, self-hosted, unlimited users | Query builder, SQL editor, dashboards, email and Slack subscriptions (email through your SMTP server), Metabot with your own AI provider, MCP server |
| Starter | $100 a month, or $90 a month billed yearly, with 5 users included, then $6 per user a month | The open-source features on Metabase Cloud, with hosting, backups, upgrades, managed email and 3-day support |
| Pro | $575 a month, or $517.50 a month billed yearly, with 10 users included, then $12 per user a month | SAML, JWT and OIDC sign-in, row and column security, filter values for each subscription, Remote Sync and usage analytics, on Cloud or self-hosted |
| Enterprise | From $20,000 a year | Pro features with custom pricing, a dedicated success engineer and a 1-day support SLA |

Paid plans count user accounts, and people who only receive the weekly email don't need one. Starter and Pro start with a 14-day free trial.

## Build or add Metabase: a short checklist

- Build a page in your app when a few people check a few fixed numbers that your code already computes, and nobody asks for new filters, exports or emails.
- Add Metabase open source, free on one container, when several teams ask new questions every week or people who don't write SQL want to explore.
- Use dashboard subscriptions, on every plan, when the team wants a weekly email or Slack post.
- Choose Metabase Cloud Starter, at $100 a month, when you'd rather not run another service.
- Connect with a read-only user limited to the tables your teams need, and use a read replica if long queries could slow the app.
- Choose Pro when you need SAML, JWT or OIDC sign-in, row and column security, filter values for each subscription, or dashboards in Git.

## Next steps

- [Dashboards for Rails apps](/articles/dashboards-for-rails-apps)
- [Dashboards for Django apps](/articles/dashboards-for-django-apps)
- [Dashboards for Next.js apps](/articles/dashboards-for-nextjs-apps)
- [Dashboards for Go apps](/articles/dashboards-for-go-apps)
- [Start with Metabase for free: open source or Metabase Cloud](/articles/start-free-open-source-or-cloud)
- [Run Metabase in production with Docker](/articles/run-metabase-in-production-with-docker)
- [Dashboards on a private database: SSH tunnel or VPC](/articles/dashboards-on-a-private-database)
- [Dashboard subscriptions: send weekly reports by email or Slack](/articles/scheduled-email-slack-reports)
- [Build customer analytics in your app or embed Metabase](/articles/build-or-embed-customer-analytics), for numbers your customers see
- [Metabase vs Google Data Studio (Looker Studio) for BigQuery and Cloud SQL](/articles/metabase-vs-looker-studio)
- [Database users, roles, and privileges](/docs/latest/databases/users-roles-privileges)
- [Connect to PostgreSQL](/docs/latest/databases/connections/postgresql) and [connect to MySQL](/docs/latest/databases/connections/mysql)
- [MCP server](/docs/latest/ai/mcp)
- [Compare Metabase plans](/pricing)