Embeddable status widget + oEmbed

Why you need it

The badge gives you one bit of information ("up or down?"). The widget gives you the next ten — overall status, per-monitor state, link to the full page — in a packaged iframe other tools render automatically.

• Zero-dependency HTML at /embed.html. Inline CSS only — no external assets means hostile parent stylesheets can't leak in. Works the same everywhere.
• oEmbed v1 auto-discovery. The public page advertises application/json+oembed via a <link rel="alternate">; Slack, WordPress, Discord, Notion all detect it and render the iframe without extra setup.
• Tenant-bound resolution. The oEmbed endpoint validates the ?url= matches the resolved page, so the iframe can never be coaxed into wrapping a third-party URL.
• Sized to fit. Default 460×360 px; the spec's maxwidth / maxheight are honoured (clamped to sane bounds) so embedders control the visual footprint.

Where it pays off

Anywhere customers or teammates discuss the system:

• Slack channel. Paste the URL into #incidents at the start of an event — everyone now has a live read without alt-tab.
• WordPress / marketing site. Drop the URL into the editor; the oEmbed plugin substitutes the iframe at publish time.
• Notion / Confluence ops runbook. Paste the URL into a runbook page — every visitor sees current state alongside the procedure.
• Internal status TV. Iframe the /embed.html URL directly into a kiosk dashboard for the operations bullpen.

Related

• Status badge
• Status pages
• Custom domain