Apache Superset
Business intelligence and data exploration platform for SQL analysis, visualizations and shared dashboards.
5 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Install the Python application or build a Docker image; current Kubernetes guidance recommends the official Superset Kubernetes Operator. Docker Compose is documented for evaluation and customized deployments.
Runs in
Documented customer environment
Customer-operated web application and metadata database, with optional cache and Celery workers for asynchronous queries, alerts and reports
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
Customer operates the application, Kubernetes or servers, metadata database, database drivers, authentication, secrets, backups and upgrades.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Apache Superset infrastructure on Amazon EKS ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Install the Python application or build a Docker image; current Kubernetes guidance recommends the official Superset Kubernetes Operator. Docker Compose is documented for evaluation and customized deployments. |
|---|---|
| Infrastructure | Servers / containers Superset is a Python web application with persistent metadata storage. The operator deploys its components to a customer-operated Kubernetes cluster; cache and worker requirements depend on enabled features. |
| Licensing model | Open Source / Open Core The reviewed upstream project uses Apache License 2.0. This classification covers the upstream software; third-party components and separately operated services retain their own terms. |
| License | Apache License 2.0 for upstream Superset; bundled subcomponents have their listed licenses. Commercial hosted services are separate offerings. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
The official configuration guide supports OAuth2 authorization-code providers through Flask-AppBuilder and Authlib, including custom providers. Configure provider callbacks, role mappings and registration policy; SAML is not established by this OAuth configuration.
Upstream OAuth2/FAB authentication · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The upstream repository supplies Compose quickstarts for evaluation and development. Production needs separate database, secrets, authentication and deployment configuration; do not treat the quickstart as a production support guarantee.
Upstream self-hosted deployment; not a provider support or production-readiness certification · Deployment artifact ↗ (repository default branch (moving; select matching application release)) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The project FAQ reports 2 vCPUs and 8 GB RAM as a community-observed moderate instance, with sizing driven by concurrent activity rather than data volume. This is not a formal minimum or HA recommendation. Production metadata database, workers, cache and the queried warehouse must be sized separately.
Upstream workload example; production dependencies and HA excluded · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate.
Upstream core licence; commercial features, support and hosting priced separately · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The publisher-designated GitHub release checked was 6.1.0, published 2026-05-13. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package.
Upstream apache/superset release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
Current installation documentation is marked Next and recommends the operator; the older in-tree Superset Helm chart is deprecated for new deployments. Match operator, image and configuration guidance to the selected released version. Connected databases and configured services may be hosted elsewhere. Self-hosting Superset does not relocate those data sources.
Community & maintenance
Apache governance reports describe ongoing contributor activity and 2026 release work. The ASF project metrics record Superset 6.1.0 and several operator releases in 2026. The project-maintained In the Wild directory lists organizations including Airbnb, Lyft and American Express; this is adoption evidence, not an endorsement or a cloud deployment certification.
Category fit
- Data & analytics
- SQL exploration, interactive charts and dashboards over connected databases; Superset queries existing data sources rather than supplying the underlying data warehouse.
Compare within Data & analytics
- ActivityInfo (Self-Managed Server)Commercial self-managed data collection, relational records and program-reporting platform.
- Azure
- Airbyte Self-ManagedSelf-managed data movement and ELT platform with customer-operated connectors and job execution.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Apache Doris Self-HostedApache-licensed analytical database with upstream AWS EKS/Alibaba ACK/ACS guides and a separately packaged cloudimg Azure VM path.
- AWS
- Azure
- Alibaba Cloud
- Apache DruidColumn-oriented analytics database for interactive queries over streaming and historical event data.
- AWS
- Azure
- Google Cloud
- AVEVA PI System (BYOL)Commercial industrial data collection, historian and visualization system with an AWS architecture.
- AWS
- Azure Trusted Research EnvironmentOpen-source reference platform for isolated research workspaces and controlled data movement.
- Azure
- Cloud Carbon FootprintOpen-source cloud-usage, energy and carbon-estimation application.
- Google Cloud
- Cloudera on CloudCloudera-managed control plane that provisions data, analytics and AI workload services into a customer's public-cloud account.
- AWS
- Azure
- Google Cloud
Showing 8 of 43 other listings in Data & analytics. These products address related workflows; read their category-fit notes before comparing scope. See all of Data & analytics →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Apache Superset capabilities ↗superset.apache.org
- Installation methods and current Kubernetes recommendation ↗superset.apache.org
- Application and database architecture ↗superset.apache.org
- Official Kubernetes Operator installation ↗apache.github.io
- Upstream Apache-2.0 and subcomponent licenses ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Apache Superset infrastructure on Amazon EKS ↗ · AWS
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
AWS Data on EKS documents deployment of Superset with its PostgreSQL metadata backend and Redis cache in a customer EKS stack. Review the reference configuration, secrets, authentication, persistent storage and upgrades; this is self-operated Apache Superset rather than a separate hosted analytics product.
- Apache Superset infrastructure on Amazon EKS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Apache Superset board reports ↗www.apache.org
- ASF release and community metrics ↗projects.apache.org
- Project-maintained adopter directory ↗superset.apache.org