Dashboard theme and layout kit for Superset self-hosters

Companies that self-host Superset get the full power of the tool but inherit the full weight of its visual design debt. 'The UI could look better, kind of blocky' and 'I would like to have more predefined UI themes and mobile templates' — these complaints don't come from people who want a different tool, they come from people who are already committed to Superset and want it to look less embarrassing when they share a dashboard with a non-technical stakeholder or a client.

The gap exists because Superset's theming system was bolted on rather than designed in. There's a theme object you can override, but it's underdocumented, the mobile rendering is an afterthought, and there are no community-maintained theme packs that a non-engineer could apply in under an hour. The open-source maintainers are focused on data modeling and query performance — visual polish is a permanently low-priority issue because the core users filing GitHub issues are engineers who tolerate the aesthetics.

What's missing is a maintained library of Superset-specific theme packs — CSS overrides, layout configurations, and mobile breakpoint fixes — distributed as versioned npm packages that a self-hosting team can install and update without forking the Superset codebase. Each theme ships with a preview, a one-command install, and documented compatibility with specific Superset versions.

What to build

Build a versioned library of Superset theme packs distributed as npm packages, each containing CSS variable overrides, chart color palettes, and mobile layout fixes, with a hosted preview environment where buyers can see exactly how their data will render before installing.

Where to start

Release two themes as free open-source packages to build distribution through the Superset GitHub community and Slack, then charge for premium themes, mobile templates, and a compatibility guarantee that includes patches within 72 hours of a Superset version release.

The hard part

Superset releases break CSS customizations regularly — the hardest ongoing cost is maintaining theme compatibility across Superset versions, which means you're on a permanent treadmill of regression testing every time Apache ships an update, and a theme that breaks silently after an upgrade will destroy trust fast.

How it makes money

One-time purchase per theme pack with an optional annual maintenance subscription for compatibility updates — sells to engineering teams who want a predictable cost, not a recurring seat fee.