PostgreSQL dashboards on live SQL.
Point Widgets PRO at any PostgreSQL — managed (Supabase, Neon, RDS, Cloud SQL) or self-hosted. Write the SQL, bind parameters, the result becomes a widget. Real charts, real refresh, no BI tax.
Last updated June 2026 · By Widgets PRO Team
Direct SQL widgets
Paste a SELECT, the result becomes a chart, metric, or table. Parameters bind safely (no string concatenation). Sub-second refresh on cached results.
Read-only credentials
We recommend a read-only role. Widgets PRO never writes — the SQL editor refuses non-SELECT statements unless you explicitly opt-in.
Managed and self-hosted
Supabase, Neon, AWS RDS, Cloud SQL, Crunchy Bridge, Aiven, Render, Railway — every managed Postgres works. Or point at your own host via SSH tunnel or VPC peering.
Query result caching
Widget-level cache with TTL. Expensive aggregations don't hammer the warehouse — the TV runs smoothly, the laptop reloads fresh on demand.
TimescaleDB & PostGIS supported
Time-series via TimescaleDB hypertables, geospatial via PostGIS — same SQL widget, same connection. No extension setup on our end.
Multiple connections
Prod + staging + analytics replica + per-customer warehouses — connect them all, switch in the widget config, isolate access via roles.
For analysts and engineers who write SQL anyway
You already query Postgres in your day-to-day. The dashboard step is just "wrap that query in a widget, give it a title, drop it in a grid." No new query language to learn, no semantic layer, no LookML, no ETL.
- Read-only role + SSH tunnel = safe production access
- Parameter binding for dropdowns, date ranges, segments
- CSV export from any chart or table
- GraphQL API + CLI to script dashboards from your repo
Combine PostgreSQL with the rest
Layer SQL widgets on a dashboard with Stripe revenue, GitHub releases, Sentry errors, Plausible traffic. One screen, multiple sources — joined visually rather than in a warehouse.
- Postgres + Stripe — revenue from your DB next to MRR from Stripe
- Postgres + GitHub — code metrics tied to deploys
- Postgres + Plausible — application metrics next to web traffic
- TV-ready widgets — high-contrast, no-interaction renders for the wallboard
Frequently asked questions
Yes — every managed Postgres exposes the standard wire protocol. Supabase, Neon, AWS RDS, Cloud SQL, Crunchy Bridge, Aiven, Render, Railway — paste the connection string and pick a read-only role. SSL is on by default; we recommend it.
Each SQL widget has a configurable cache TTL (default 60 seconds, range 5s to 24h). Cached results serve everyone; only expired queries hit the database. TV signage with stable widgets effectively never hits the DB after the first render.
SSL/TLS by default. We recommend a dedicated read-only role with row-level security if applicable. For private databases, supported access patterns: SSH tunnel, VPC peering (Enterprise), or IP allowlist of our static egress IPs.
Yes — point Widgets PRO at the replica's connection string. We do not require the primary. For TimescaleDB hypertables and large aggregations, a replica is the right pattern.