Amazon QuickSight, now presented by AWS as Amazon Quick Sight within Amazon Quick, is AWS's managed BI service priced per user or per reader session. Pages here cover moving to self-hosted Apache Superset or Metabase.
Moving QuickSight dashboards to Apache Superset: exporting analyses and datasets as asset bundles for reference, reconnecting Superset directly to Athena, Redshift or other SQL sources, replacing SPICE with caching or a query engine, and rebuilding dashboards and row-level rules.
For teams whose QuickSight users mostly read dashboards: recreating questions and dashboards in Metabase, connecting to the same databases, mapping reader groups to Metabase groups, and which Metabase plan is needed for SSO and row-level permissions.
Comparing QuickSight with self-hosted Apache Superset: per-user and per-session pricing against infrastructure, SPICE against querying the warehouse directly, SQL Lab and chart types, embedding, identity integration and who operates and upgrades each.
For business users who want self-service questions without SQL: QuickSight against Metabase's query builder, Metabase's free open-source edition versus Starter, Pro and Enterprise features, and the operating work of a self-hosted Metabase on PostgreSQL.
Cost of ownership by component: Author, Reader and Pro prices, reader session packs, SPICE storage and Q question capacity against Apache Superset or Metabase on your own infrastructure, with database, cache, workers, upgrades, support and migration effort.
What asset bundle export jobs give you: Quick Sight JSON or CloudFormation definitions of dashboards, analyses and datasets, the data sources the APIs skip, why data itself is not exported, and how to use the bundle as a rebuild specification for another BI tool.
For organizations that need BI on-premises, in another cloud or inside a customer's environment, where an AWS-hosted service does not fit: running Apache Superset or Metabase next to the data, connecting to non-AWS warehouses, and one BI stack across environments.
QuickSight bills anonymous and embedded readers through session capacity. This page compares that model with Apache Superset's embedded SDK and guest tokens, or Metabase embedding, where cost follows infrastructure rather than sessions, and what tenant isolation the host app must enforce.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.