Sery network status

All systems operational

Last verified end-to-end on . Subscribe below for incident notifications.

Network components

Each piece of the Sery network, what it does, and its current state. Components listed in dependency order — the ones at the top affect the most users when they're degraded.

  • Sery Cloud — coordinationOperational

    Identity, catalog, routing, and connection-brokering. The network layer.

  • Sery-managed AI (cloud /chat)Operational

    LLM inference for the cloud workspace `/chat` page. Backed by Anthropic with zero-retention configured. The agent runs server-side and dispatches SQL to your machine through the workspace tunnel.

  • Sery Link auto-updaterOperational

    Signed-release manifest endpoint. The desktop app fetches this directly from GitHub releases — Sery cloud is not on the path.

    Hosted by GitHub — see status.github.com for upstream.

  • Storage credentials trust boundaryN/A

    AWS keys, Drive OAuth tokens, SFTP passwords — all stored in your OS keychain on disk. Sery cloud never sees them. The cloud agent reaches your data through a private tunnel to your local Sery Link, which runs the storage call from your machine. There's no Sery-side component holding the credentials.

    By architecture, not by promise. Read more on /trust.

Incident history

Last 90 days

No incidents in the last 90 days.

When something does happen, the post-mortem lands here with a timeline, root cause, and what we changed so it doesn't recur. Same shape as the better-run network operators' incident writeups.

Why this page exists

Operating a data network requires the kind of trust that doesn't survive the first un-disclosed outage. So we keep this page accurate even when nothing's wrong, because the way we report problems is itself a feature.

The desktop app is open-source under AGPL-3.0; if Sery cloud ever fails, your local features keep working — see /trust for the structural reasons.

Reading this page mid-incident? We're sorry. Email [email protected] if you need help, or check GitHub issues for known problems.

See the trust posture