PROVIDER - Managed Apache Superset cloud

Preset

Preset is the managed Apache Superset cloud run by the project's core authors: SQL Lab, dashboards, SSO and row level security, plus alerts and scheduled reports, with a self hosted open source option kept open. Good for teams that want Superset without operations, while deep customisation stops at the upstream boundary.

Data Visualization & BI United States 2026.11.20
3.9pts

Detailed Notes

Pros 5 items

Run by the core Apache Superset authors, delivering 1 ready to use managed service
Keeps SQL Lab and dashboards so analysts write queries and publish them as 1 board
Supports SSO, row level security and role permissions for 2 or more governance tiers
Ships alerts and scheduled reports that push 1 dashboard to email or chat on a cadence
The open source edition self hosts, so 2 deployment shapes can be swapped for compliance

Cons 4 items

Built on Superset, so complex interaction and front end customisation inherit its ceilings
Managed tiers price seats and features separately, which raises cost as teams grow
Large query performance still depends on engine and model tuning
Access from mainland China and data residency need a separate review

Service Overview

Preset is the managed cloud for Apache Superset, run by the project's core authors and occupying the open source plus managed branch of data visualisation and BI. The engine is the same open source project; what is sold is operations relief, account governance and commercial support.

The reason teams pick it is practical: they like Superset's SQL first dashboards but do not want to maintain upgrades, SSO and permissions themselves. The cost is that the product boundary follows upstream, so deep customisation stays in house.

Key Strengths

  • Same engine: skills and dashboards transfer to and from the open source edition
  • SQL first: analysts write definitions in SQL Lab and publish them as boards
  • Complete governance: SSO, row level security and roles ship in the box
  • Alerts and reports: dashboards push to email and chat on a schedule
  • Self hosting fallback: compliance or cost can move to the open source path

Product Ecosystem

Platform capabilities

SQL Lab, dashboard and chart libraries, datasets and metric definitions, SSO with row level security, alerts and scheduled reports, plus usage and workspace management.

Integrations

Connects to common relational databases and cloud warehouses, with an API and embedding options for other systems.

Typical scenarios

Internal dashboards, recurring business reporting, SQL centric analyst teams, and compliance cases that need a self hosted alternative.

Limitations

  • Upstream boundary: complex interaction and front end customisation hit Superset limits
  • Tiered billing: seats and features are priced separately and scale upward
  • Performance dependency: heavy queries rely on engine and model tuning
  • Regional questions: mainland access and residency need separate review

Use Cases

  • SQL oriented analyst teams (★★★★☆): capability matches habit
  • Managed open source BI (★★★★☆): governance features included
  • Heavy front end products (★★☆☆☆): upstream limits apply
  • Spreadsheet only users (★★★☆☆): SQL remains a barrier

Pricing

Item Billing model Notes
Cloud service Per seat by edition Includes hosting and support
Enterprise Contact sales Adds embedding and governance
Self hosted Open source, no licence fee Operations are yours

FAQ

How does it differ from Apache Superset?

The capability is the same project; Preset adds hosting, governance and support.

Which data sources work?

Common relational databases and cloud warehouses through drivers.

Can it use our company SSO?

Yes, SSO with row level security scopes visible data per role.

How is performance at large volume?

It follows the underlying database and modelling, so aggregates and indexes in the warehouse help most.

Code Examples

# List dashboards through the Superset REST API, which the managed service also exposes
import os, requests

host = "https://your-workspace.preset.io"
r = requests.get(f"{host}/api/v1/dashboard/", headers={"Authorization": f"Bearer {os.environ['PRESET_TOKEN']}"})
for item in r.json().get("result", [])[:5]:
    print(item["id"], item["dashboard_title"])
# Verify the token is valid
curl -s "$PRESET_HOST/api/v1/me" -H "Authorization: Bearer $PRESET_TOKEN" | head -c 200

Community & Resources

Visit Preset Website → https://preset.io/
Visit Website ↗