01Quickstart

Three minutes,
one live badge.

The end-to-end path from a fresh account to a Badge embedded on your site. No agents, no YAML. Five steps, each under a minute.

1. Sign up

Open /sign-in and choose GitHub or magic-link email. We create an Account and a single Service called Main for you on first signup — you can rename it later from Services.

2. Add a Service (optional)

A Service groups related Monitors. Free is capped at one Service; Pro raises that to five. Skip this step if the default Main Service is fine.

3. Add your first Monitor

From Monitors → Add Monitor, pick a type (HTTP for endpoints; SSL for certificate expiry watch), paste a URL, and pick an interval.

  • HTTP method, headers, expected status, and content-match are all editable.
  • Free interval floor is 5 minutes; Pro drops to 1 minute.
  • Two consecutive failed checks open an Incident — single transient blips don't alarm.

4. Set up alerts

Settings → Notifications. Add at least one email recipient (must be SES-verified in the sandbox period — see in-page note) and optionally a webhook URL. Use the Send test button to confirm round-trip before a real incident fires.

5. Forge a Badge

Badges → Forge a badge. Choose Account-wide (rolls up every Service's state into one pill) or pick a specific Service. Defaults are regular size and auto theme. Submit; you'll land on the install page with the snippet ready to copy:

HTML
<a href="https://glimly.dev" target="_blank" rel="noopener">
  <img src="https://glimly.dev/b/<token>.svg" alt="acme status" />
</a>

Paste it into your site's footer, README, or marketing page. The Badge updates within ~15 seconds of state changes (CloudFront edge cache + stale-while-revalidate). No invalidation needed.

Next steps

  • Badge install — sizes, themes, attribution rules, Markdown variant for GitHub READMEs.
  • Card install — multi-Service embed for your /status section (Pro+).
  • Webhooks — payload schema and signature verification.
Quickstart · Docs · Glimly · Glimly