Publish a branded status page backed by real uptime probes. Your services report their own health, so visitors see what's actually happening — not a dashboard someone forgot to flip.
One page. Real probes behind every service.
A status page is the public page customers check to find out whether your service is working. It answers one question — “is it down, or is it just me?” — before it turns into a support ticket.
Most status pages are updated by hand. They stay green until someone notices an incident and flips a switch, which usually happens after customers have already felt it. The page becomes a record of what an operator remembered to do, not what actually happened.
OrgOrg's Status app backs every service with live probes. HTTP checks, synthetic login flows, and upstream provider health run on a schedule and roll up automatically, so the page reflects measured reality. You step in to communicate during an incident — never to keep the colors honest.
Everything a status page should do — backed by checks that actually run.
Real probes
HTTP checks, synthetic Playwright flows like login and signup, and native upstream health for Convex, Cloudflare, GCP, and Vercel — all running on a schedule, not on someone's memory.
Automatic service status
Group probes into services. The worst probe sets the service's status, so a single failing check surfaces immediately. No human flips a switch.
Worst probe sets the service → Degraded
Branded public page
Serve the page on your own hostname with your logo, brand color, support email, and website link. It reads like part of your product, not a third-party widget.
Incidents & maintenance
Post incident updates as they develop and schedule maintenance windows ahead of time, right alongside live status so visitors get the full picture.
Uptime history
Per-service uptime bars show the trailing window of health, giving customers and your own team an honest, at-a-glance record of reliability over time.
During an incident
The moment a probe goes red, the affected service flips to degraded or down on its own. Your team doesn't have to remember to update anything before customers start checking.
From there you post updates — investigating, identified, monitoring, resolved — and they stack into a timeline visitors can follow. One clear page answers “is it just me?” for everyone at once, so the inbound drops instead of spiking.
Elevated latency on the API. Looking into it now.
A slow upstream query. Rolling out a fix.
Fix deployed. Latency back to normal; watching.
All probes green for 15 minutes. Closing out.
Why it matters
A status page is only worth checking if it's right when it counts. When the page is measured rather than remembered, it earns the benefit of the doubt — and that changes how an incident feels for everyone watching.
Honest by construction
Because status comes from probes, the page can't quietly sit green while the API is down. The worst check wins, so partial outages surface instead of hiding.
Caught before the tickets
Probes run continuously. A broken login flow or a slow upstream shows up on the page the moment it happens — often before the first customer email lands.
One source of truth
Live status, incident updates, maintenance, and uptime history live in one place. Customers self-serve and your team stops answering the same question.
Four steps to a status page that keeps itself honest.
List what you run — web app, API, background jobs, marketing site. Each becomes a row on the public page.
Attach HTTP checks, synthetic login/signup flows, or upstream provider health. Probes start reporting on a schedule.
Add your hostname, logo, and brand color. Set a support email so visitors land where they expect.
Share the URL. From then on the page reflects real health — you only step in to communicate, not to update colors.
The difference is who decides the status — a probe, or a person who has to remember.
| Capability | OrgOrg Status | Manual status page |
|---|---|---|
| Service status source | Measured by probes | Typed by a human |
| HTTP uptime checks | Often separate tool | |
| Synthetic login / signup flows | ||
| Upstream provider health | Convex, Cloudflare, GCP, Vercel | |
| Worst-probe service rollup | Manual judgement | |
| Custom domain & branding | ||
| Incident updates & maintenance | ||
| Catches outages before customers | Continuous probes | Only once noticed |
| Bundled with 15+ apps, one flat price | Standalone tool |
The language of monitoring and incident communication.
A status page is a public page that shows whether your services are working. Customers check it to answer 'is it down, or is it just me?' OrgOrg's Status app backs every service with live probes, so the page reflects real health instead of a status someone has to remember to update.
Manual status pages stay green until a human notices an incident and flips a switch — which often happens after customers do. OrgOrg's Status app runs probes continuously and rolls them up automatically, so degraded and down states appear the moment they happen. You post incident updates for context, but the underlying status is measured, not typed.
Three kinds. HTTP checks hit an endpoint and assert on the response. Synthetic Playwright flows drive a real browser through journeys like login and signup, catching breakage that a simple ping misses. Upstream provider checks read the published health of Convex, Cloudflare, GCP, and Vercel, so you can show when an outage is your provider's, not yours.
Group one or more probes under a service. The worst probe sets the service's status: if the API's HTTP check is fine but its login flow is failing, the API shows as degraded. That means the page errs toward honesty rather than hiding a partial outage behind one healthy check.
Yes. Point a custom hostname at your status page and add your logo, brand color, support email, and website link. Visitors see a page that looks like yours, at an address like status.yourcompany.com.
Yes. Post incident updates as a situation develops and schedule maintenance windows in advance. Both appear alongside live service status and uptime history, so visitors get the whole story in one place.
Each service has an uptime bar covering the trailing window, plus a percentage. It's an honest record your customers — and your own team — can use to see reliability trends over time.
The Status app is included in the OrgOrg bundle: one flat price for the whole suite of apps, alongside Go Links, People Profiles, On-Call, and more. Start free; see the plans page for current pricing.
Free to start · No credit card · 15 apps for one flat price
