Metabase Open Source vs Cloud Which Deployment Fits an Indie SaaS

Before calling the deployment cheap, name an instance owner, database owner, backup retention, rollback plan, and alert recipient. If only one person knows how to restore the instance, the license price hides an on-call obligation.

The Cloud responsibility boundary

Metabase Cloud hands several platform actions to the vendor. The official explanation includes running the service, backups, upgrades, and monitoring, which lets a small SaaS team spend its first week on definitions and access instead of on a production platform. The time saved can matter more than the subscription line during a validation phase.

Cloud does not decide which customer can see which row. The application database, Metabase collections, questions, and dashboards still require a permission design. If analytics will be embedded in a customer console, draw the tenant boundary first and verify that the selected plan supports the required permission and embedding model.

Cloud also changes the first place to investigate an incident. A team may check service status and account settings before debugging a local container or database. That is a relocation of responsibility, not the disappearance of an incident process.

How to read the displayed prices

The Metabase pricing page fetched today lists Open Source as free. Cloud Starter displays 100 dollars per month, or 90 dollars per month on the annual display, plus a per-user structure of 6 dollars per user per month or 65 dollars per user per year. The first five users are included, and the page shows a 14-day free trial. Cloud Pro displays 575 dollars per month, or 517.50 dollars per month on the annual display, plus 12 dollars per user per month or 130 dollars per user per year. The first ten users are included.

Those are the current page values, with taxes excluded. The page also explains that people who log in to Metabase are counted as users. This is the per-user billing rule shown on the page, so use logged-in accounts rather than a vague audience estimate when you budget. Do not turn a visitor count, database row count, or dashboard count into a user count, and do not assume that included users make every embedded scenario free. Confirm the account's purchase flow before budgeting.

A self-hosted budget needs different rows. Servers, a managed database, backups, SMTP, monitoring, and engineering time may all cost money. The official comparison page describes the responsibility without promising one total for every cloud region or architecture. Keep those rows visible beside the Cloud subscription so the comparison has the same unit of account.

Permissions, embedding, and team size

An internal dashboard with a few colleagues is a good Open Source trial because the page's unlimited-user description keeps the first experiment simple. The database account should still receive only the required read access, and Metabase administrators should be separated from ordinary viewers. Free software does not replace least privilege.

When customers must see their own tenant data, permissions become the central design question. The Pro capability list includes row and column permissions, multi-tenant embedded analytics, and white-label delivery. Those features can matter to a product that sells analytics, but the team still has to verify data modeling, tenant identification, identity flow, and contract requirements. A feature name cannot certify the whole security design.

SSO, required two-factor authentication, caching, and usage analytics also appear in the Pro list. Turn each into an upgrade reason only after naming the person who uses it, the manual work it removes, and the failure owner. If the team is only exploring SQL internally, the advanced list may be a later option.

Three deployment situations

A solo founder or two-person team building an internal dashboard can use the official OSS installation path for a low-risk trial. Connect sanitized data, document backups and upgrades, and decide about Cloud after the metrics have a stable job. The first goal is to validate the question, not to win a platform contest.

An early SaaS team preparing a customer demo can compare the Cloud Starter starting price with the engineering time of self-hosting. Write down the first logged-in users, expected active users after the trial, and embedding needs. The 14-day trial is displayed on the pricing page; whether it gives your team enough acceptance time is a project decision.

A team with multi-tenant analytics, audit expectations, or single sign-on should treat Pro as a capability check rather than an automatic purchase. Validate data isolation and identity mapping first, then decide whether Cloud Pro or a self-hosted Pro deployment gives the better responsibility boundary.

Selection checklist

Read the Cloud versus self-hosting comparison and the pricing page, then answer these questions.

• Who owns the database, instance, backups, upgrades, monitoring, and incident response.
• Does the team already have Docker, network isolation, secret rotation, and rollback procedures.
• How are internal users, customer users, and embedded visitors counted, and who will log in to Metabase.
• Are row and column permissions, SSO, required two-factor authentication, caching, usage analytics, multi-tenant embedding, or white-label delivery current needs.
• What are the displayed Starter or Pro charges beside the self-hosted server, database, backup, and engineering rows.
• Who checks permissions, restores a backup, and removes trial data when the pilot ends.

If the team cannot answer the first question, the free label is not yet a launch plan. If external customers already need tenant-specific analytics in the product, validate the Pro permission and embedding path before choosing a deployment.

Common questions

Is Metabase Open Source actually free

The pricing page lists Open Source as a free self-hosted plan and describes its product capabilities. Servers, databases, backups, email, monitoring, and staff time remain the team's responsibility.

Does Cloud Starter include every user

The page displays a starting monthly charge, a per-user rate, and five included users for Starter. It also says people who log in to Metabase are counted as users. Confirm the exact account bill in the purchase flow.

Is self-hosting automatically cheaper

No conclusion is safe without counting operations. The software license is free, but infrastructure and maintenance still cost time or money. Compare those rows with the Cloud subscription and launch time.

When should a team consider Pro

Consider Pro when row and column permissions, SSO, required two-factor authentication, cache controls, usage analytics, multi-tenant embedding, or white-label delivery already affect a current release. Verify the permission and tenant model first.

Will Cloud design data security for us

No. Cloud takes on part of the platform operations. Database authorization, data modeling, tenant isolation, collection permissions, and external sharing still require the team to design and review.