Metabase total cost calculator

Estimate Metabase costs from edition features, dashboard concurrency, database query load, application storage, embedding and migration work.

Last updated

In short

  • The Metabase application database is separate from the databases being analyzed.
  • Query costs and data-warehouse load can exceed the BI application cost.
  • SSO, embedding and governance requirements must be checked against the selected edition.
On this page (5)

Costs and savings · Part of Metabase

Interactive worksheet · no sign-up

Estimate Metabase analytics costs

Use the same currency and scope for both options. Inputs stay in this page; they are not included in analytics or sent with an enquiry.

1. Your current bill
2. The replacement

Business management: CHF 1,590/month for up to 3 apps; onboarding from CHF 9,900. Infrastructure and paid licences are extra.

Additional warehouse compute

Only additional target-side queries. Existing unchanged warehouse costs belong in retained spend.

Keep warehouse and data-platform costs retained unless the project actually removes them. Compare embedded analytics separately from internal dashboards.

3. Transition and overlap
Optional: value internal operating time

Time released is capacity, not automatically payroll or cash saved. Keep time already billed by Pilae or another supplier out of these fields.

How the calculation works
  1. Current monthly invoices = billed units × unit price + additional current spend.
  2. Replacement monthly invoices = Pilae management + additional infrastructure + target licences + workload usage + retained services.
  3. Transition = plan onboarding + new hardware + extra migration + training + parallel months × max(0, current invoices − retained services). Parallel months are capped at the comparison horizon.
  4. Total invoices = monthly invoices × horizon, plus transition for the replacement. Payback uses the full transition commitment divided by positive monthly invoice saving, including all entered overlap months even beyond the selected horizon.
  5. Economic saving adds the change in valued internal operating time. It does not assume headcount reduction.

Business includes up to 3 apps, then a published per-app fee (CHF 390 in CHF). Starter’s published CHF price is CHF 449/month. All Pilae figures come from the same price data as the pricing page. Workload inputs are your estimates, not supplier quotes. Taxes, price growth, discount rates, opportunity costs and differences in functionality are outside this arithmetic.

A Metabase server can be a small part of the cost of delivering analytics. The queries it launches, the database they run against, access controls and dashboard maintenance all belong in the budget. The calculator estimates the operating envelope; it does not promise that replacing a BI licence will reproduce every semantic model or report.

Split the stack into three bills

First is the Metabase application and its required edition. Second is its application database, which stores questions, dashboards, users and configuration. Third is the data source being queried. Metabase’s application-database documentation makes that separation explicit.

Workload driver What to observe Where cost appears
Dashboard concurrency Simultaneous users and refresh schedules Application and source database
Query complexity Joins, scans and expensive calculations Database CPU, IO or warehouse billing
Background work Synchronization, scans and scheduled reports Off-hours load and mail services
Saved content Questions, dashboards, permissions and history Application database and backup
Embedded use Authenticated users, isolation and required features Edition and integration work
Access governance SSO and data restrictions Licence and validation effort

A dashboard loading quickly once is not a capacity test. Reproduce the morning reporting peak and the background jobs that occur at the same time.

Choose the edition from required behavior

The pricing page distinguishes product capabilities. For example, the SAML documentation identifies availability and setup requirements. Check the current edition for every essential identity, governance or embedding feature rather than assuming self-hosting unlocks it.

Keep a written requirement for row or tenant separation. A dashboard hidden from a menu is not necessarily a data-access boundary. Validate access with accounts that should see different records and with an account that should see none.

An example of query-driven cost

Imagine a dashboard with twelve cards refreshed by fifty users each morning. Without assuming any caching, that can trigger hundreds of queries. A change to refresh behavior or a better data model may reduce load more effectively than increasing application memory. The actual outcome depends on database plans, caching and usage; measure it rather than assigning a generic savings percentage.

Metabase’s production guidance is a starting point for deployment choices. Use its assumptions alongside your own query profile. Do not copy a benchmark’s user capacity into a quote for a different database and workload.

Price the migration as a rebuild where necessary

Existing dashboards may contain calculated measures, custom visuals, exports, permissions or alerting behavior that do not transfer directly. Select representative reports and compare the business answer, filtering, access and delivery format. Recreating the chart is not enough if the underlying metric changes.

Include data preparation and ownership. If analysts spend less time administering a BI server but more time repairing SQL or exports, retain that work in the economic model. Employee hours released are capacity value unless an actual expense ends.

Decide with an operating and recovery plan

Back up the application database and required configuration/secrets. The analytical source data has its own recovery responsibility. Test restoration of questions and permissions into an isolated environment and confirm data-source credentials do not expose production unnecessarily.

Use current Pilae pricing for the service component, then add the verified upstream edition and database workload. The PostgreSQL read-only integration is useful when that is the data source; a Power BI rebuild assessment addresses a different migration question. Bring a handful of important dashboards and their query history to make the estimate concrete.

Sources and further reading

Use the linked documentation to confirm the version, edition and contract that apply to your project.

Budget our analytics platform

Bring your current bill, required capabilities and workload assumptions. We will separate recurring operation from migration and retained services.