Deploy Apache Superset in one click.
The open-source business intelligence platform. We review it, secure it and run it in production for you. Pick a region in Switzerland, France or Germany, and reach your databases through a secure tunnel. We keep it patched, backed up and online. You just query.
★ 73k stars · Apache-2.0 · TypeScript · tested versions · shipped with a runbook
What is Apache Superset?
Open-source business intelligence from the Apache Software Foundation. SQL-first and warehouse-native.
Apache Superset is an open-source business intelligence platform. SQL Lab for writing and exploring queries, a no-code builder with dozens of visualization types, and dashboards the whole company can share. It connects to virtually any SQL-speaking database, including Postgres, MySQL, ClickHouse and BigQuery, and queries your data where it lives.
Your BI layer sees everything the business does: revenue, customers, margins, the queries your analysts run and the credentials to every database behind them. Self-hosting Superset keeps that layer on infrastructure you control instead of a third-party BI vendor’s cloud.
The catch: production Superset is more than one container. A metadata database, a cache, async workers for long-running queries, plus reverse proxy, TLS, authentication, upgrades and backups. Assembling and running all of it is usually your job, at the worst possible time.
Apache Superset, without the ops.
Everything below is what you’d otherwise build and babysit yourself.
Your BI stays where you put it.
Deploy to ch-zh1 (Zurich), fr-pa1 (Paris) or de-fr1 (Frankfurt). Dashboards, saved queries, users and database credentials stay in the region you choose, under Swiss or EU law and in line with GDPR.
Reviewed before it ships.
Our Apache Superset package is reviewed, secured and locked to versions we have tested, and it ships with a runbook. We track CVEs upstream and patch them fast.
Your data never moves.
Superset queries your databases where they live. Nothing is copied into a vendor’s warehouse. With our secure tunnel it reaches databases inside your own network without you exposing them to the internet.
TLS, upgrades, scaling: handled.
Certificates issued and renewed, rolling zero-downtime updates, instant rollback, health checks. The metadata database, cache and workers ship as one reviewed package. You stay current without re-assembling it.
Backups you can actually restore.
Offsite backups of your dashboards, charts, saved queries and settings. We run restore drills, not just snapshots.
Leave whenever you want.
Apache Superset is open source and so is your exit: your dashboards and metadata leave with you, in usable form, and your data never left your databases to begin with. Pilae runs it for you. It never owns it.
Self-hosting Apache Superset: DIY vs Pilae.
Both paths end with Apache Superset in production. Only one of them ends there this afternoon.
| Self-hosted DIY | On Pilae | |
|---|---|---|
| Initial setup | Docker, reverse proxy, DNS, auth. An afternoon if nothing fights back | One click, live in minutes |
| TLS certificates | Issue, wire up, remember to renew | Issued and renewed automatically |
| Upgrades | Frequent releases to track, test and apply yourself | Tested versions, rolled out with instant rollback |
| Security patching | You watch the CVE feed | Upstream tracked, CVEs prioritized |
| Backups | cron + object storage + hope | Offsite, verified with restore drills |
| Data residency | Wherever your VPS happens to be | You pick: Zurich, Paris, Frankfurt, or your own racks |
| 3 a.m. failures | Yours | Ours |
| Production architecture | Metadata DB, cache, async workers, assembled by hand | Shipped as one reviewed and tested package |
| Reaching your databases | Open firewall holes to your warehouse, carefully | Secure tunnel; databases stay inside your own network |
From catalog to production in three steps.
No servers to set up, no configuration to write. The platform work is already done.
Pick Apache Superset.
Find it in the catalog: reviewed, secured, locked to tested versions, runbook included.
Choose where it runs.
A Pilae region in Switzerland, France or Germany, or your own machine connected through a secure tunnel. Same console either way.
Deploy and connect your databases.
One click to production with TLS and backups from day one. Point Superset at Postgres, ClickHouse, BigQuery or anything else it speaks to, invite your analysts, done.
BI data is your business. Keep it close.
Every Apache Superset deployment is pinned to the region you choose. Encryption, dedicated VLANs, and the option to hold your own encryption keys for regulated workloads, plus a secure tunnel to the databases it queries.
Deploying Apache Superset: the questions we get.
If yours isn’t here, reach out and we’ll answer it, usually the same day.
What’s the easiest way to self-host Apache Superset?
Deploying it through a managed platform. On Pilae you pick Apache Superset from the catalog, choose a region, and click deploy. TLS, backups, patching and upgrades are handled for you from the first minute. You get self-hosting’s control without its ops.
What databases does Apache Superset connect to?
Virtually anything that speaks SQL: Postgres, MySQL, ClickHouse, BigQuery and many more through its database driver system. With Pilae’s secure tunnel it can also reach databases inside your own network without you exposing them to the internet.
Is Apache Superset hard to run in production?
Harder than the demo suggests. Production Superset wants a metadata database, a cache and async workers for long-running queries, plus TLS, auth and backups around all of it. On Pilae the whole assembly ships as one reviewed and tested package with a runbook.
Where does my Superset data live?
Dashboards, saved queries, users and credentials live in the region you choose: Zurich, Paris or Frankfurt. Everything is encrypted, and you can hold your own encryption keys. Your actual data stays in your databases: Superset queries it at the source rather than copying it.
Does Apache Superset support roles and row-level security?
Yes. Superset has role-based access control built in, plus row-level security filters so different users see different slices of the same dashboard. For single sign-on, deploy Keycloak from the same catalog and put OIDC in front of it.
Can I move my Apache Superset deployment off Pilae later?
Yes, and that’s by design. Superset is open source, your dashboards and metadata exit with you in usable form, and your data never left your own databases. No proprietary formats, no lock-in.
Runs well next to.
Build your stack from the same catalog. One console, one click each.
Postgres-based development platform. Auth, storage, edge functions.
Ask questions of your data, build dashboards, share with the team.
Metrics, logs and traces in one place. Dashboards pre-wired per pod.
Single sign-on, OIDC and SAML. The identity layer for the rest of the stack.
Apache Superset, without the ops.
Deploy it in minutes, keep your data in the country you choose, and leave whenever you want. Your data goes with you.