Show your customers what your stack depends on.

It renders a live status badge on your website showing the third-party services your stack depends on — AWS, Stripe, GitHub Actions, whatever you monitor on Pingoru. Each row updates within a couple of minutes when the upstream vendor flips into an incident, so visitors see what's degraded right now instead of guessing from your error messages.

Two lines of HTML. A div with your widget id, plus the script tag. Paste them into your status page, your support page, your homepage footer, your "about our stack" page — anywhere readers care about whether your dependencies are healthy.

No. The script is ~5.6KB gzipped, loads async, and renders into the page after first paint. It does one fetch to our edge-cached API (60-second cache, sub-50ms p95) and never blocks the parent page.

Yes, the widget editor gives you three embed formats: script (recommended), iframe, and bare URL. Use iframe when your CMS or CSP blocks third-party script tags. The script embed is preferred because the rendered content lives in your DOM, which lets search engines index the status state.

Yes. The widget editor lets you pick which of your monitors to include and which components within each monitor. So if you monitor AWS as a whole but only want EC2 and S3 in the widget, you can narrow to just those two. Adding or removing services takes a couple of clicks and the change goes live within 60 seconds.

Three layouts (Full, Compact, Minimal) and three themes (Auto, Light, Dark). Auto follows the embedding page's color-scheme so a dark customer site gets a dark widget without configuration. You can also toggle the title bar, the "all systems operational" banner, service logos, and per-row incident counts.

The "Status data by Pingoru →" link is non-removable on the Free and Pro tiers. It links back to pingoru.io with a UTM tag specific to your widget so we can track which embeds drive traffic. Whitelabel removal is on the roadmap for a future Business tier.

Pingoru polls every status page on a 60-second cadence. The widget hits a 60-second edge cache, so the worst case staleness is about 2 minutes from the upstream vendor posting an incident to the widget reflecting it. Cached responses keep customer page load times fast even under heavy embed traffic.

The matching row flips from green to amber or red depending on severity, the banner at the top changes to "Partial outage in progress" or similar, and a per-row "X active incidents" subtitle appears. Visitors who see this on your site instantly understand the issue is upstream, not you.

One widget per account in v1. If you have two different sites that need different sets of services, the v1 workaround is to use the per-monitor component filter to show different subsets via one widget — or wait for v2 which lifts the constraint.

Free on every plan. The widget is part of the free Pingoru tier alongside up to 25 monitors and email notifications. Pro ($15/month) unlocks more monitors and additional notification channels but the widget is identical between tiers.

The widget editor at /app/settings/widget shows total impressions, last render time, and the top sites that have embedded the widget. Each unique browser load counts as one impression; the script de-duplicates re-renders within a single page view.