A wallboard for your reliability team.
Pull deploys, incidents, SLO burn rate, error budgets, on-call rotation, and Grafana panels into one operational pane. Mount it on the team's TV, mirror it to phones, drive it from CI.
Last updated June 2026 · By Widgets PRO Team
Deploys + change tracker
Last 50 production deploys across services — author, commit, status, duration, link to the run. Vercel, Fly, GitHub Actions, ArgoCD, Spinnaker — all on one tile.
Incidents in flight
Active incidents pulled from PagerDuty, Opsgenie, FireHydrant, incident.io — severity, on-call, time-since-page. Calm during quiet hours, loud the moment an SEV-1 lands.
SLO burn + error budget
For each service, the current SLO, burn rate over 1h / 6h / 24h, and remaining error budget for the month. The team sees when the budget is about to redline before the alert fires.
Grafana panels embedded
Use both. Embed any Grafana panel via iframe widget — we wrap with business context (deploys, change windows, on-call rotation) Grafana doesn't track.
On-call & runbooks
Who is on-call right now, when the next handover is, and a one-tap link to the active runbook. No "who do I page?" delay during an incident.
CLI + GraphQL + MCP
Version dashboards as code with the `widgets` CLI. Programmatic provisioning via GraphQL. Drive from Claude / Cursor via the MCP server — same surface, all the time.
Use it next to Grafana, not instead of it
Grafana wins on Prometheus, Loki, and PromQL — that's where it belongs. Widgets PRO wraps your SRE work with the business context your team needs around incidents: who shipped what, what changed in the last hour, who is on-call, how the customer-facing SLO is holding up.
- Grafana for time-series depth — embed via iframe widget
- Widgets PRO for business + change + on-call context
- WebSocket sync — the team's laptops, phones, and TV stay aligned
- No either/or — pick the right tool per audience
Wallboard for the on-call room
Pair a TV with a 6-digit code, rotate dashboards as a playlist — active incidents during US hours, deploys during EU hours, last-week post-mortems for Friday review. Status widgets glow red the second a service degrades; the team sees the dashboard, not a notification on a laptop someone closed.
- TV signage flow built-in — no separate signage tool
- Per-shift dashboards — incident response vs cap-planning vs review
- Real-time push over WebSocket — no manual refresh
- Status tiles that auto-resolve when the incident clears
Frequently asked questions
No — and it shouldn't. Grafana is the standard for Prometheus / Loki / PromQL time-series. Widgets PRO sits next to it: business context (deploys, change windows, customer-facing SLOs, on-call) that doesn't belong in a metrics tool. Most teams embed Grafana panels via the iframe widget and let Widgets PRO handle the wrapper.
PagerDuty, Opsgenie, FireHydrant, and incident.io expose documented REST APIs — we wrap them via the declarative integrations DSL. Status pages from Statuspage.io and Better Stack feed in too. If your incident tool has any API surface, it plugs in within a working day.
Yes. The `widgets` CLI emits portable JSON/YAML — drop it into the repo, review changes in PRs, deploy with `widgets push` in CI. Dashboards become artifacts, not whiteboard memory.
Yes — pull the burn rate and budget remaining from those tools via REST. If you have Prometheus SLO recordings, point the dashboard at the same recording rules Grafana reads from. The SLO widget formats them — we don't reimplement the SLO engine.