Skip to content
@@ 00 · status @@

System status.

Pyor keeps none of your code on a server — there isn’t one in the path — so there’s remarkably little of yours that can go down. Here’s a plain look at the few pieces people do ask about, and where to watch the one that matters most: GitHub.

@@ 01 · components @@

What’s up right now.

Operational
Website (pyor.review)
The marketing site and these pages.
Operational
Downloads / CDN
The macOS, Windows, and Linux installers served to you.
Operational
Billing (Stripe)
Checkout and subscription management for Teams, handled by Stripe.
Operational
GitHub API (upstream dependency)
Not ours — but it’s where your PRs actually live, so Pyor is only as available as it is. githubstatus.com
Operational
@@ 02 · why so little can break @@

No server holding your code.

Pyor runs on your machine and talks directly to GitHub with your own credentials. There’s no Pyor backend storing your repositories, proxying your requests, or sitting between you and your reviews — so there’s no such backend to suffer an outage.

In practice that means the thing most likely to affect your review session is GitHub itself. When GitHub is healthy, Pyor is too; when it isn’t, that’s where to look. The website, downloads, and billing above are the small surface that’s genuinely ours to keep up.

@@ 03 · live history @@

This page is a lightweight overview, not a real-time monitor. For live uptime history and incident notices, watch our external status provider at «status.pyor.review» — and for the upstream that matters most, GitHub publishes its own at githubstatus.com.

@@ Spotted something we haven’t? support@pyor.review · @@