
# Metabase Self-Hosted

Business intelligence and dashboards on your infrastructure.

Canonical page: https://launchinyourcloud.com/directory/metabase/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Metabase Self-Hosted

Business intelligence and dashboards on your infrastructure.

- Listing: https://launchinyourcloud.com/directory/metabase/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source and commercial options
- Licensing model: open-source
- Installation: Docker image or Java JAR
- Architecture: Customer-operated application and database
- Operations: Your team manages hosting, upgrades and the application database.
- Product website: https://www.metabase.com/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Metabase documents self-hosting on AWS, Google Cloud, Azure and DigitalOcean. This entry covers self-hosting rather than Metabase Cloud. Infrastructure sizing, the application database and feature entitlements depend on the selected edition. Metabase's critical security advisory affects 0.64.0 through 0.64.3.3 and corresponding Enterprise versions. Self-hosted operators should use Open Source 0.64.3.4 or later, or Enterprise 1.64.3.4 or later. The hardening release strengthens API validation and permission checks, limits metadata exposure, improves deactivated-user session handling, removes database secrets from serialization exports, and adds optional session-signing and encryption keys.

The self-hosted platform offers an AGPL Open Source Edition alongside commercial capabilities and licensing. The classification covers the platform family described in this entry.

The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.


### Category fit

- data-analytics: Business intelligence and dashboards on your infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale (checked 2026-11-12). 

- digitalocean: Boundary not confirmed; Customer-operated; control plane: not-assessed. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale (checked 2026-11-12). 


### Cloud deployment evidence

- Metabase production hosting compatibility (aws, azure, gcp, digitalocean): https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale
  The vendor names AWS Elastic Beanstalk and Docker, and explicitly identifies Google Cloud, Azure and DigitalOcean as alternative hosts for the Metabase application. Pair this compatibility statement with the current installation guide and a production application database; this is self-hosting, separate from Metabase Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Installing Metabase: https://www.metabase.com/docs/latest/installation-and-operation/installing-metabase

- Production hosting options: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale

- Licensing and edition terms: https://www.metabase.com/license

- Metabase 64 critical security update: https://github.com/metabase/metabase/security/advisories/GHSA-v44v-x8x4-mvcw

### Licensing sources

- https://www.metabase.com/license

### Infrastructure sources

- https://www.metabase.com/docs/latest/installation-and-operation/installing-metabase

- https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. SAML authentication is available on Pro and Enterprise for self-hosted deployments. This does not establish SAML for the free/open-source edition. Scope: Self-hosted Pro and Enterprise. Source: https://www.metabase.com/docs/latest/people-and-groups/authenticating-with-saml (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. Pro and Enterprise support SCIM. The documentation names Okta and Microsoft Entra ID; Okta supports user/group provisioning while Entra supports user provisioning only. Scope: Self-hosted Pro and Enterprise; identity-provider behavior differs. Source: https://www.metabase.com/docs/latest/people-and-groups/user-provisioning (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor supplies separate Open Source and Enterprise images and publishes Compose examples. Production needs an external supported application database; embedded H2 is evaluation-only. Pin the selected image, configure persistence, TLS and backup, and do not assume an officially supported Helm chart. Scope: Official self-hosted Docker/Compose distributions. Source: https://www.metabase.com/docs/latest/installation-and-operation/running-metabase-on-docker (reviewed 2026-11-20). Deployment artifact: https://www.metabase.com/docs/latest/installation-and-operation/running-metabase-on-docker#example-docker-compose-yaml-file. Artifact reference: v65 documentation; select a compatible image tag.

- Minimum footprint / sizing: Documented. The vendor gives an application baseline of 1 core/1 GB, plus 1 core/2 GB per 20 concurrent users. The application database starts at 1 core/2 GB and needs additional capacity. Query databases, HA replicas, storage and background jobs are extra; total registered users alone is insufficient for sizing. Scope: Post-v52 production sizing guidance by concurrent users, not registered accounts. Source: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-in-production (reviewed 2026-11-20).

- License pricing: Documented. The repository separates AGPL core code from the commercial enterprise directory and enterprise binaries. Self-hosted Pro/Enterprise features require commercial terms; the core licence does not establish paid-edition prices, support or hosting cost. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/metabase/metabase/master/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Metabase 64 critical security update (security-advisory): The advisory records API, permission, metadata, session and serialization hardening in the 64 release line. Scope: Open Source 0.64.0 to before 0.64.3.4 and corresponding Pro/Enterprise 1.64 versions. Conditions: Self-hosted edition, configured integrations and exposed endpoints determine which fixes apply; optional key settings need explicit configuration. Action: Upgrade Open Source to at least 0.64.3.4 or Pro/Enterprise to at least 1.64.3.4 and follow the vendor security checklist. Source: https://github.com/metabase/metabase/security/advisories/GHSA-v44v-x8x4-mvcw; reviewed 2026-11-17.



