The most common self-hosted BI shortlist: Superset fully Apache-2.0 with SQL Lab and a semantic layer against Metabase, AGPL with paid Pro features, aimed at non-technical users. Verdict by who builds dashboards, permissions needs and which features need a Metabase plan.
Business intelligence on SQL databases against observability dashboards for metrics, logs and traces: which questions each answers well, Apache-2.0 versus AGPL and Grafana Enterprise, and when an organization runs both.
Two SQL-first tools for analysts: Superset with a metadata database, Celery workers and a Kubernetes operator in alpha against Redash, BSD-2-Clause with a lighter footprint and a release history that paused from 2021 to 2025. Weighs maintenance risk, scale and migration effort.
For teams shortlisting all three open-source BI tools: a side-by-side of licensing and paid tiers, required services, sign-in options and who each suits, ending with a pick by team profile rather than a single winner.
Embedding dashboards in a customer-facing product: Superset's Embedded SDK with guest tokens and row level security against Metabase guest embeds on the open-source edition and the SSO and full-app embedding that need Pro or Enterprise. Covers multi-tenant data isolation and licensing cost.
Which documented way to deploy Apache Superset fits: Kubernetes with the official Superset Kubernetes Operator, Docker Compose on one host, or a PyPI install with components you wire together. Covers what the Superset docs call best practice for production, the deprecated Helm chart, custom images, metadata database backups and what each method leaves to you.
SQL-first, Apache-2.0 Superset against Lightdash, an open-core BI layer that reads metrics from a dbt project. Covers who writes the queries, where metric definitions live, what sits behind the Lightdash ee license and paid tiers, and which fits a team already running dbt.
What each costs to run for a given number of users: Superset has no paid edition, while Metabase sells Starter, Pro and Enterprise plans whose prices and included users are published. Shows where Metabase features such as SSO, row-level security and interactive embedding force a paid plan and what Superset needs instead.
Whether to buy Preset Cloud, the managed Apache Superset service, or run Superset yourself: Preset's published per-user prices and viewer licenses for embedded dashboards, what moves to Enterprise (SSO with SCIM, audit logs, managed private cloud), and the metadata database, cache and Celery workers you operate when self-hosting.
When a self-hosted Superset can run as just the web application and metadata database, and when it needs Redis and Celery worker and beat processes: async queries, alerts and reports, and dashboard thumbnails all depend on them. Covers the extra services to run and monitor and how this changes sizing and upgrades.