Status page badges & embeds

Vantaj lets you share live status information outside the dashboard — as a badge in a README or as a self-updating iframe panel on any website.

Both require a public status page with a slug configured. Go to Status Pages → your page → Access to set a slug and publish it.

Try the interactive Badge Builder →

Status badge

A status badge is a small SVG image that shows the current aggregate health of your status page. It refreshes automatically (cached for 60 seconds at the CDN edge).

Badge URL

https://app.vantaj.co/api/badge/{slug}

Replace {slug} with your status page's public slug.

Possible states

Embed in a README (Markdown)

[![Status](https://app.vantaj.co/api/badge/your-slug)](https://app.vantaj.co/s/your-slug)

Embed in a webpage (HTML)

<a href="https://app.vantaj.co/s/your-slug">
  <img src="https://app.vantaj.co/api/badge/your-slug" alt="Status" />
</a>

Copy from the editor

Open your status page in the editor and switch to the Share tab. All three snippet formats (Markdown, HTML, and bare badge URL) are ready to copy with one click.

Embeddable widget (iframe)

The embed widget shows your full status page — monitor list, overall status banner, and last-checked time — inside an <iframe>. It updates automatically on each page load.

Embed URL

https://app.vantaj.co/embed/{slug}

iframe snippet

<iframe
  src="https://app.vantaj.co/embed/your-slug"
  width="100%"
  height="400"
  frameborder="0"
  style="border-radius:12px;overflow:hidden"
></iframe>

Adjust height to fit your layout. The embed has no minimum width requirement and works at any reasonable size.

Where it works

The embed has been tested in:

• Notion — paste the URL as an embed block
• Confluence — use the HTML macro or the iframe macro
• GitHub wikis — paste the iframe HTML in the wiki source (note: GitHub's markdown renderer strips iframes, but the wiki raw HTML mode supports them)
• Any website — paste the snippet into your HTML

Copy from the editor

The Share tab in the status page editor includes the full iframe snippet ready to copy.

Caching

Badge responses are cached at Cloudflare's edge for 60 seconds (Cache-Control: public, max-age=60, s-maxage=60, stale-while-revalidate=300). This means:

• Badge changes propagate within ~60 seconds of a status change
• Your Supabase database is not hit on every badge request — Cloudflare serves the cached response
• GitHub's own image CDN adds another layer of caching; the badge in a README may lag by a few minutes during a sustained incident

If you need faster propagation, contact support to discuss edge cache purging on status transitions.