Preset

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Build me the dashboards I actually need instead of paying for hosted Superset — noting that **the product is open source and running it yourself is the honest first answer.**

Two paths. Take the first unless you have a reason.

PATH ONE: RUN SUPERSET
- Docker Compose on a small server, a Postgres for metadata, and a reverse proxy
- It is a real application: budget for upgrades, and pin the version rather than tracking latest
- Everything the hosted version offers, minus somebody being on call

PATH TWO: BUILD THE SMALL VERSION, WHICH IS OFTEN ENOUGH
Most teams use ten saved queries and six charts. That is a weekend.

STACK
- Node 20+ with Fastify, server-rendered HTML
- SQLite through better-sqlite3 for the definitions; your real database for the data
- Inline SVG or canvas for the charts, no charting library needed for bars and lines
- Caddy in front

THE DATA MODEL
- sources: id, name, dsn_encrypted, kind, read_only_user
- queries: id, name, source_id, sql, params_json, created_by, updated_at
- charts: id, query_id, kind, config_json
- dashboards: id, name, layout_json, is_public
- runs: id, query_id, started_at, ms, rows, error — **so a slow dashboard is diagnosable rather than merely annoying**

RUNNING SQL SAFELY, WHICH IS THE ONLY DANGEROUS PART
- **Connect with a read-only user, always.** Not a user you promise not to write with; one that cannot
- A statement timeout on every query and a row cap on every result. One unbounded join must not take the database down for everybody
- Parameters bound, never interpolated, even though the author is trusted — a saved query with a parameter in a dashboard is reachable by everybody who can open it
- Cache results with a per-query freshness, and show the cache time on the chart. **A dashboard that does not say when it was computed gets quoted in a meeting as if it were live**

CHARTS WITHOUT A LIBRARY
- Line, bar, stacked bar, single number, and a table. That is every dashboard anybody has ever needed
- Tabular numerals so columns align, and units on every axis
- Server-render the SVG so a dashboard loads instantly and prints correctly

SHARING
- Read-only dashboard links, and a scheduled email with the numbers inline rather than an attachment
- Access per source and per dashboard, checked on the server

WHAT MATTERS MOST
A genuinely read-only connection with a timeout, and the computed-at timestamp on every chart. One protects the database; the other protects the decisions.