A shields.io-style badge for your README, or a full live status widget for your site — one script tag, always reflecting the real status page.
Free forever plan, no card required.Why it matters
A status page only works if people go looking for it. A badge in your README or a widget on your homepage puts the answer in front of them before they have to ask — quiet proof that someone's actually watching. Think about how a developer evaluates an API or open-source project they're about to depend on: a green "operational" badge sitting right there in the README, updating in real time, says something a static "we take reliability seriously" paragraph never could. The same goes for a widget embedded on a SaaS homepage — it's a small, constantly-updating signal that reliability isn't just a claim, it's something being actively measured and shown, in public, all the time. It's a small, unglamorous piece of UI that quietly does a lot of trust-building work. It's a quiet form of marketing — proof of reliability shown continuously, rather than claimed once in a sales pitch. A prospective customer comparing two otherwise-similar tools is more likely to trust the one willing to show its own uptime in public, right there next to the pricing table, than one that only talks about reliability in the abstract.
One `<script>` tag for the widget; one image URL for the badge — no SDK to install. Pasting either into an existing README or homepage takes under a minute, and there's no build step, no package to add to your dependencies, and nothing that needs updating when your framework or bundler changes. It's designed to be something you could add during a coffee break, not a project that needs its own sprint. Most teams have it live within minutes of deciding to add it.
Reflects your live status page with no manual updates, cached just 60 seconds at the edge. There's no separate step to keep it in sync — the same event that updates your status page dashboard is what updates the badge and widget, so they can never drift out of date the way a manually-updated "status" line in a README eventually would. That's one less integration to babysit, and one less thing that can silently fall out of sync. There's nothing to remember to refresh manually, ever.
Renders cleanly on both light and dark embedding pages, so it never looks bolted on. It's designed to sit naturally next to your own content rather than standing out as an obviously third-party embed, which matters if the whole point is for it to read as a normal part of your site. It's built to disappear into your existing design rather than announce itself as somebody else's widget. It's meant to be one more polished detail, not a visibly bolted-on add-on. Whichever theme a visitor happens to be using, the badge or widget should look like it was designed alongside the rest of the page, not dropped in as an afterthought.
FAQ
No SDK — one <script> tag embeds the live widget, and one image URL is all the README badge needs. There's nothing to add to a package manager and no build configuration required; copy the snippet, paste it where you want it shown, and it's live. Both the badge and the widget are meant to be genuinely drop-in, not a starting point for further configuration. Copy, paste, done — that's genuinely the whole process.
It reflects your live status page with no manual updates, cached for just 60 seconds at the edge. That short cache window keeps it fast to load for every viewer while still staying close enough to real-time that it's a genuinely useful signal, not a stale snapshot from hours earlier. That's a deliberate balance between freshness and not hammering the endpoint on every single page view. It's tuned to feel live without adding meaningful load to your own infrastructure.
No — it's a lightweight script that loads asynchronously and renders from a cached edge response, so it never blocks the rest of your page from loading. Visitors see your own content render first, with the widget filling in a moment later rather than holding anything else up. It's engineered to be safe to add without a second thought about performance. It's built to be invisible in terms of performance, not just visually unobtrusive.
Get Started
Sign up and your first monitor can be live in under a minute — free, no card required.