Apache Superset Problems & Issues
Real user-reported problems, complaints, and limitations for Apache Superset. Based on analysis of 13 signals.
Overall score: 64/100
Issues by Category
Superset is too hard for business users
G2 summaries, DashboardFox, Ksolves and Hacker News commenters all describe a steep learning curve, especially without SQL skills. Superset is seen as a tool engineers and analysts use to build reports, not one that non-technical staff explore on their own.
Superset has lots of small UI bugs
Users list many papercuts: cryptic error messages, odd table behavior, things that cannot be copied, and dashboards that look different after upgrades. The 6.0 release reworked the visual design, which itself broke some existing layouts.
Superset upgrade broke my dashboards
Upgrades are a recurring source of pain: GitHub discussions report broken dashboard styling and duplicate-label errors after moving from 4.x to 6.0, and an Open Food Facts incident report shows dashboards failing with missing-column errors when migrations did not run. One Hacker News user lost dashboards after an update.
Superset alerts and reports are hard to get working
Scheduled email and Slack reports need Celery beat, workers, a headless browser and SMTP settings. The dev config sends nothing by default (dry run), and GitHub issues show reports silently failing when the worker cannot reach the webdriver URL.
Superset documentation is outdated and sparse
Hacker News users say the docs are thin and that renamed concepts left online guides out of date; ToolRadar also lists documentation gaps. Many fixes live only in GitHub issues and discussions, often answered by a bot.
No official support for self-hosted Superset
Self-hosted Superset has community support only (GitHub, Slack). Reviews say there is no fast, real-time help unless you pay Preset for its managed service, where standard support starts on the Professional plan.
Superset default SECRET_KEY vulnerability
In 2023 researchers found thousands of Superset servers still using the default SECRET_KEY, letting attackers forge sessions (CVE-2023-27524). Since 2.1 Superset refuses to start with the default key, which now trips up many first-time installs.
Superset permissions are confusing
Granting access is hard to manage: database access does not cascade to datasets, Gamma users need dataset access per table, and 6.0 tightened checks that caused new 403 errors. DashboardFox and several GitHub issues say it is hard to see who has which permission.
Is Apache Superset hard to set up?
Installation is the most repeated complaint on Hacker News and in blog reviews: a production setup needs a metadata database, Redis, Celery workers, a secret key and a reverse proxy. Users report Docker init failures, Python version conflicts and a broken welcome screen on first run.
Is Apache Superset really free?
The software is free under the Apache 2.0 license, but reviewers point out that servers and developer time to run, secure and upgrade it add up. The managed alternative, Preset, charges $20-25 per user per month and $500 per month for 50 embedded viewers.
Why is Superset so slow?
Slow dashboards and chart timeouts show up in G2 cons, Hacker News and many GitHub threads. The default client-side chart timeout is 60 seconds, and slow source queries, missing caching and proxy timeouts produce 504 errors on big dashboards.
Superset embedded dashboard not working
Embedding with guest tokens needs a feature flag, allowed domains, Talisman/CSP changes and correct guest role permissions. GitHub and forum threads are full of 403 errors, 'refused to connect' iframes and CSRF token errors when embedding.
Superset has no real semantic layer or easy joins
Hacker News users note that joins across databases are limited and that there is no built-in semantic layer, so teams add dbt, Cube or Trino. Metabase is often recommended for teams that want joins without writing SQL.
Regret Patterns
Common reasons users regret choosing Apache Superset.
Underestimated maintenance
Teams pick Superset because it is free, then spend significant engineering time on upgrades, security, workers and drivers.
Business users never adopted it
Non-technical staff find the Explore view and datasets confusing and keep asking analysts for reports.
Upgrade broke dashboards
A major-version upgrade left dashboards with broken styling or errors that had to be fixed one by one.
Embedding took weeks
Guest tokens, CSP, CORS and role permissions took far longer than expected to get working in production.
Missing semantic layer
Metrics got defined differently across datasets, pushing teams to add dbt or Cube on top.
When Apache Superset Breaks Down
Specific scenarios where Apache Superset fails or underperforms.
Large dashboards on slow warehouses
Dozens of charts each firing a query hit the 60-second client timeout or proxy 504s.
Major version upgrades
Skipped or failed db migrations, or layout changes, break dashboards after upgrading.
Embedding in a SaaS product
Guest token, Talisman/CSP and role permissions cause 403s and blank iframes.
Scheduled reports
Reports silently fail when Celery beat, the headless browser or SMTP are misconfigured.
Many teams with separate permissions
Per-dataset access grants become hard to audit and maintain.
Non-technical self-serve analytics
Users without SQL struggle to create datasets and metrics.