Does self-hosted Metabase cost less than ThoughtSpot?
Metabase Open Source has no license fee, so a self-hosted Metabase comparison turns on infrastructure, the application database, upgrade effort, identity and permission requirements, and migration work. ThoughtSpot pricing depends on users, credits or a negotiated quote, and the ThoughtSpot figures for your organization must come from your own order form or quote, not from this page. On the Metabase side, the published plans are Open Source at $0, Starter at $100 per month or $90 per month billed yearly for the first 5 users, Pro at $575 per month or $517.50 per month billed yearly for the first 10 users, and Enterprise priced by quote starting at $20,000 per year, according to the Metabase pricing page. Confirm current figures on that page before you compare them with your renewal.
The license line is not the whole cost. Your team pays for the servers or cloud accounts that run the Metabase JAR, the PostgreSQL or MySQL instance that holds the application database, backups, monitoring, and the staff time to apply upgrades. Upgrades run application database migrations automatically, so the work includes a tested backup and a planned window. Support is also a recurring line: Open Source relies on community channels and your own engineers, while paid tiers include vendor support. Ask your team to estimate these components in hours and infrastructure spend, then compare them with the ThoughtSpot quote as a whole.
Access requirements can change the answer. Single sign-on, row and column level permissions, multi-tenant data segregation and usage auditing appear only in Pro and Enterprise. Open Source and Starter support Google sign-in and LDAP, while JWT, OIDC, SAML and SCIM provisioning require Pro or Enterprise. If your regulators or internal policy require SAML-based SSO or column-level restrictions on customer data, the cheapest self-hosted route may not meet them, and the Pro price becomes the realistic baseline for the comparison. Before you model costs, list the access controls your ThoughtSpot deployment enforces today and check each one against the Metabase plan that provides it.
Which cost components change between the two options
This table compares ThoughtSpot and self-hosted Metabase by cost component, marking each row as one-time or recurring. Use it to see who is paid for what, then request quotes that break out the same components. The main takeaway is that ThoughtSpot's largest recurring cost is the subscription or credit charge, while Metabase shifts most recurring cost to your own infrastructure, staff time and any paid Metabase plan you choose.
| Cost component | ThoughtSpot | Self-hosted Metabase | One-time or recurring |
|---|---|---|---|
| License or subscription | Per-user or credit-based subscription, with Enterprise priced by quote; confirm term, user tiers and credit consumption in writing | Open Source edition is free to self-host; Starter is $100 per month ($90 billed yearly) and Pro is $575 per month ($517.50 billed yearly), per Metabase's pricing page; Enterprise is quoted from $20,000 per year | Recurring |
| Infrastructure | Usually included in the vendor's cloud service; for self-managed software, you pay for the servers and platform it runs on | Your own servers or cloud accounts for the Metabase JAR or container and the data warehouse connections it queries | Recurring |
| Application database | Managed by the vendor in cloud; in self-managed deployments, you run and back up the supporting databases | PostgreSQL recommended for production in place of the embedded H2 database; hosting, storage and backups are your cost | Recurring |
| Implementation and identity setup | Mostly vendor-led configuration; confirm any professional services fees | Installation, network design, TLS, reverse proxy and identity integration; SSO and SCIM need Pro or Enterprise plans | One-time |
| Migration of content | Export Models and Liveboards as TML, then rebuild answers and search-based content by hand in Metabase models, metrics and dashboards | Rebuilding dashboards, questions and permissions; a one-time load-from-h2 step if you move from the embedded database | One-time |
| Support | Included in the vendor subscription; confirm support tier and response terms | Community support on the open source edition; paid support and SSO require Pro or Enterprise; external support is a separate retainer | Recurring |
| Upgrades and maintenance | Handled by the vendor in cloud; self-managed upgrades are your team's work | Your team plans upgrades, backs up the application database first, and follows the version support schedule; each upgrade cycle is recurring effort | Recurring |
| Internal skills | Less administration on cloud; users still need training on search and Liveboards | Staff to run Java-based service, database, backups and access control; reduce the load with a support retainer if needed | Recurring |
What moves the comparison most
Price on the ThoughtSpot side and the Metabase side depends on a small set of variables. Users, credit consumption, data volume, availability, identity requirements and in-house skills each shift the total, so confirm them before comparing quotes.
User count against Metabase tiers
Metabase's free Open Source edition has no per-user fee, but Starter and Pro add a monthly charge for users beyond the included seats. Per the Metabase pricing page, additional users cost $6 per month on Starter and $12 per month on Pro. Count named viewers, editors and embedded end users separately, because embedded users may be priced differently from internal seats. Ask ThoughtSpot for the per-user rate that applies to your mix of creators and consumers.
ThoughtSpot credit consumption
Where ThoughtSpot is sold on credits, cost follows query and compute activity rather than seat count. Heavy search use, frequent Liveboard refreshes and scheduled jobs can consume credits faster than headcount suggests. Ask the vendor how credits are metered for your workload, what a typical month of usage would draw, and whether overage terms apply. Model the same usage pattern on Metabase, where the cost is the infrastructure that runs it.
Data volume and warehouse query load
Metabase and ThoughtSpot both push queries to your warehouse, so warehouse compute is a cost that appears on neither license. Dashboards with wide date ranges, unfiltered joins or frequent refreshes drive that cost. Caching and summary tables reduce it. Ask your data platform team to measure current query volume for the dashboards you plan to move before sizing the Metabase server.
Availability and the application database
A single Metabase node with an embedded H2 database is suitable for demos only. Production use calls for PostgreSQL as the application database, and a highly available setup adds a managed or replicated database, redundant application nodes and a tested backup and restore path. Upgrades also run database migrations, and the docs advise reducing a cluster to one node for major upgrades. Price the database tier and the failover design explicitly, since they recur every month.
Identity requirements and the Pro tier
Google sign-in and LDAP work on Open Source and Starter. SSO through JWT, OIDC or SAML, advanced LDAP group sync and SCIM provisioning require Pro or Enterprise, and row and column level permissions are also limited to those plans. If your identity provider rules or data access policies depend on these features, the Pro price applies to all users, not only the ones who need them. Confirm the identity standard and permission model early, because it often decides the tier.
In-house PostgreSQL and Java skills
Metabase runs as a JAR on a Java runtime and keeps its state in PostgreSQL. Your team needs people who can operate the database, rotate secrets, apply upgrades in release order and roll back a failed migration. If those skills are missing, the cost is either training time or external support, which recurs with every release cycle. Ask whether support is needed for installation only or for ongoing upgrades, and whether a quote covers both.
What you run yourself on Metabase
The self-hosted Metabase stack has four parts you will own: the Metabase application, which runs either as a JAR or from the open-source metabase/metabase Docker image, a PostgreSQL application database, the connections to your data warehouses, and the surrounding controls for TLS, backups and monitoring. MySQL 8.4.0 or MariaDB 10.6.0 and later (with utf8mb4) are also supported for the application database, but PostgreSQL is the option Metabase recommends for production, so confirm your team can operate it before you choose otherwise. Each of these components has an owner, and that owner's time is the main recurring cost of running Metabase yourself, alongside the database and compute hosting.
Do not run production on the embedded H2 database. Metabase ships H2 for demos and evaluation only. When you move to PostgreSQL or MySQL, the one-time load-from-h2 command migrates the data, and it must be run with the same Metabase version that last wrote the H2 file. Check the version before you start, and rehearse the move in a staging environment with a copy of the file. For the upgrade routine, Metabase 64 is an LTS release published on 16 September 2026 and supported until 1 December 2027, which is 14 months of support for LTS releases. Non-LTS releases usually reach end of life after about 2 months, so plan your upgrade cadence around LTS versions unless you need specific features earlier.
Every upgrade runs application database migrations automatically, so treat the backup of the application database as a required step, not an option. Metabase's upgrade guidance also asks you to reduce a cluster to a single node for major upgrades because of a migration lock, and to upgrade one release at a time from versions older than 40. Build a runbook covering the backup, the node reduction, the staged upgrade and a rollback path, and test it in staging first. Ask your Metabase contact or check the Metabase upgrading documentation for the current guidance before you schedule any production change.
How to build the comparison with your own numbers
This sequence turns the ThoughtSpot and Metabase comparison into a model built from your own user counts, quotes and infrastructure rates, so the result reflects your organization rather than list prices. The output is a three-year cost view with a sensitivity test on user growth that your finance and platform teams can review.
Export the current user, group and content inventory
Your ThoughtSpot administrator exports the list of active users, their roles, the groups they belong to and the count of Liveboards, Answers and Models in use. Include users who log in monthly as well as daily, because license tiers and credit consumption often depend on who actually uses the platform. Separate creators who build content from consumers who only view it, since they usually sit in different cost lines. The step is complete when you have a single table with user counts by role, group membership and content volume, signed off by the BI owner.
Price ThoughtSpot from a written quote
Ask your ThoughtSpot account team for a quote or order form that uses the same user counts, role mix, credit assumptions and deployment model (cloud or self-managed) from the inventory. Ask the quote to state the per-user and credit rates, any minimum commitments, the renewal uplift and what happens to usage above the included allowance. Confirm whether support, upgrades and any self-managed infrastructure requirements are included or billed separately. The step is complete when you hold a document that states all three years of expected spend, with each line traceable to a number from your inventory.
Select the Metabase tier that meets your access needs
List the access controls your organization requires, such as single sign-on through your identity provider, row and column level permissions, multi-tenant data separation and usage auditing. Check these against Metabase's current pricing page, which places some of these features in paid plans and not in Open Source or Starter. Confirm the identity protocols you need (for example, SAML, OIDC, SCIM provisioning or LDAP group sync) against the Metabase people and groups documentation, because support differs by plan. The step is complete when you have one selected plan, or the open-source edition with a documented decision to run without those features, and the price of that plan is recorded from the vendor's page at the date you check it.
Estimate infrastructure and PostgreSQL run cost
Size the Metabase application server and the PostgreSQL application database for your user count and expected concurrency, then price them at your own cloud or data center rates. Include compute, storage, backup storage, network egress, load balancing and any high availability replica your standards require. Metabase recommends PostgreSQL for production, so price that database rather than the embedded H2 database used for demos. Your platform team should produce the monthly and annual figures from your internal rate card. The step is complete when the infrastructure lines are in a spreadsheet with the rate source noted beside each line.
Add migration, testing and upgrade effort
Estimate the one-time work to export ThoughtSpot content, rebuild Models, Liveboards and Answers as Metabase models, questions and dashboards, migrate identities and permissions, and test with business users. Then list the recurring work: applying Metabase upgrades, which run database migrations automatically and should follow a backed-up application database, plus monitoring, backups and any support contract you choose. Estimate effort in hours from your own team or your implementation partner's written scope rather than from a published figure. Separate one-time lines from recurring lines so they can be amortized correctly. The step is complete when each line has an owner, a basis for the estimate and a clear one-time or recurring tag.
Build a three-year cost view
Combine the ThoughtSpot quote, the Metabase plan price, the infrastructure estimate and the migration and upkeep lines into one table covering three years. Show ThoughtSpot and Metabase side by side, with the same currency, the same user base and the same timing for one-time costs. Add a line for internal staff time that is not already in the infrastructure estimate, such as administrator time for patching and access reviews. The step is complete when the table gives a total for each option over three years, and the assumptions beside it can be traced to the inventory, the quote, the rate card or the scope.
Test the model against user growth
Run the three-year view again with user counts that rise and fall around your current baseline, and with a higher credit consumption scenario for ThoughtSpot if your quote is credit-based. Note the points where a plan change, an additional user block or an added PostgreSQL capacity tier changes the result, and check the thresholds against the current pricing and the quote. Share the results with finance and the BI owner so they can see which assumptions drive the difference. The step is complete when you have a sensitivity table, the break-even points you care about, and a list of the assumptions that need to be confirmed with vendors before a decision is made.
Common questions on cost, effort and skills
Is Metabase Open Source really free to run?
The software itself is free: Metabase's Open Source edition is self-hosted with unlimited users and dashboards, so the license fee is zero. What you still pay for is everything around it: the servers or cloud accounts that run the Metabase JAR or Docker image, a PostgreSQL or MySQL application database, backups, monitoring, staff time for upgrades and access administration, and the warehouse compute your queries consume. Those costs recur and scale with usage and data volume. Confirm the figures for your own environment, since the open source edition does not include SSO or row and column level permissions.
Why does Metabase Enterprise start at $20,000 per year?
According to Metabase's pricing page, Enterprise is priced by quote starting at $20,000 per year. The quote depends on the features and deployment you need, and only the Enterprise plan offers air-gapped deployment. Ask the vendor what the quote covers, including the number of users, support terms, air-gapped rights and any deployment or environment limits. Compare it with the Pro plan, which the same pricing page lists at $575 per month or $517.50 per month billed yearly with the first 10 users included, plus $12 per additional user per month.
Does the SSO and row-level permission requirement change the price?
Yes, it changes which plan you need. According to the Metabase pricing page, SSO, row and column level permissions, multi-tenant data segregation and usage analytics and auditing are included only in the Pro and Enterprise plans, not in Open Source or Starter. Advanced SAML, JWT, OIDC and SCIM provisioning also require Pro or Enterprise. If you need these controls, the realistic comparison is Pro against the self-hosted cost of building equivalent access controls yourself, so confirm the feature list with Metabase before you budget.
How long does a migration from ThoughtSpot to Metabase take?
No migration duration has been supplied for this page, and the answer depends on scope. The main drivers are the number of Models, Liveboards and Answers to rebuild, how many data sources and joins they use, how many users need SSO and row-level permissions, and how much of the work your team has done before. Ask for a written scope with deliverables and a timeline before work starts. DeployOpen plans and implements migrations under fixed-scope agreements, and the timeline follows from that scope.
Can an internal team run Metabase without outside help?
Often yes, for a team with experience running a Java application backed by a relational database. Metabase runs as a JAR or Docker image, recommends PostgreSQL for production, and runs automatic application database migrations during upgrades. The docs recommend backing up the application database first and reducing a cluster to a single node for major upgrades. Whether your team can do this alone depends on your existing platform skills, on-call coverage and change process. Many organizations pair internal ownership with an outside partner for the first migration and for upgrades.
What skills and hours does running Metabase require?
Plan for roles rather than a fixed headcount, because no effort figure has been supplied. You need someone who can deploy and secure the application, operate PostgreSQL with backups and restores, manage TLS, identity provider integration and secrets, and handle upgrades using the version support schedule. Analysts or data owners also need time to maintain models, metrics and permissions. Ask any implementation partner to state the roles, the hours by phase and the handover material in the written scope, and track recurring hours for upgrades and access reviews.
Which Metabase version should we plan around for support?
Plan around an LTS release when you need a longer support window. According to Metabase's version support page, LTS versions are supported for 14 months, while non-LTS versions usually reach end of life after 2 months. Metabase 64 is an LTS release published on 16 September 2026 with end of life on 1 December 2027. Confirm the current version and its end-of-life date on the version support page before you commit, since newer releases appear regularly.
Does a ThoughtSpot Enterprise quote compare directly with Metabase?
Not line for line. ThoughtSpot pricing combines per-user plans or credit-based usage with quoted enterprise terms, while Metabase Open Source has no license fee and paid tiers are priced per plan and user. Build the comparison from components: licenses or credits, infrastructure, application database, support, upgrades and migration effort. Ask ThoughtSpot for the quote's assumptions and ask yourself which of your users need the features that Metabase reserves for paid plans.
When staying on ThoughtSpot still makes sense
Staying on ThoughtSpot is a defensible decision in several situations, and the quote should be judged on those merits rather than on the cost of Metabase alone. The strongest case is heavy search-style self-service by non-technical users, where business people type a question and expect an answer without building it. If that habit is central to how your organization works, the cost of retraining users and rebuilding their question-asking workflow is a real cost that does not appear on a per-user price comparison. Ask your business sponsors to list the five most common ways people use ThoughtSpot today, then test each one against Metabase's query builder and models before assuming the migration is a like-for-like swap.
A second case is an existing ThoughtSpot Software investment in your own datacenter. If the self-managed release line already runs on hardware you operate, the marginal cost of staying may be lower than the cost of standing up a new BI stack, including the application database, backups, upgrades and user migration. Confirm with ThoughtSpot which license terms, support entitlements and upgrade windows apply to your deployment, and compare them directly with the self-managed comparison page in this group. A third case is an operating team that cannot absorb the work. Running Metabase well means owning PostgreSQL, the application database backups, release-by-release upgrades and access control, including SSO and row-level permissions on paid Metabase plans. If your platform team has no capacity for that, a managed or vendor-supported path may be the honest answer.
Before you accept or reject the quote, run a feature fit check with the sibling comparison pages rather than assuming Metabase matches search-driven analysis. The ThoughtSpot vs Metabase comparison covers editions, embedding and the query builder against ThoughtSpot search, and the ThoughtSpot vs Apache Superset page covers the semantic model trade-offs. Document the questions that matter most to your users, the data permissions they need, and the identity provider you must integrate, then confirm each item in writing with the vendor. A decision made on that evidence will hold up better in a renewal discussion than one made on the headline price.
How DeployOpen scopes a fixed-price Metabase implementation
DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own infrastructure. For a move from ThoughtSpot to self-hosted Metabase, we start by writing down what your users, data sources and permissions require, so the cost comparison rests on your environment rather than on assumptions.
How we scope
- Inventory the ThoughtSpot Models, Liveboards and users that must move, using your own TML exports as the starting list
- Confirm which Metabase plan your SSO and row or column permission needs require before the scope is written
- Agree in writing the Metabase edition, hosting target, application database and data sources covered by the work
- Name the components you will pay for directly, including infrastructure, the application database and support, so the quote is comparable
How we build
- Deploy Metabase on PostgreSQL for production, rather than the embedded H2 database used for demos
- Connect your data sources, rebuild models and metrics, and configure groups and permissions to match your access rules
- Test dashboards, embedding and authentication in a staging environment before any user sees the new platform
- Document every configuration decision, including the upgrade path between Metabase releases
How we hand over
- Deliver the runbook covering installation, backup of the application database and the upgrade procedure
- Provide a list of rebuilt dashboards mapped back to the original ThoughtSpot Liveboards, with open gaps stated plainly
- Run a walkthrough with your platform and analytics teams so they can operate the system without us
- Record the handover checklist and the scope items closed, signed off against the written scope
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer, scoped separately from the implementation
- Plan upgrades release by release and confirm each target version against Metabase's version support dates before scheduling
- Agree in advance who owns security patching, backup restore tests and user access reviews after go-live
- Ask for the retainer terms in writing, including response expectations, before committing to ongoing work
