Skip to main content
oryn

Oryn beta · Infrastructure

System status

Live platform liveness — API, database, and infrastructure health. Support-pipeline performance is at /trust/status; resolved-incident archive at /trust/incidents.

Status not yet determined

Not enough recent activity to compute an overall status. The platform itself is unaffected.

Last checked: Nov 7, 2026, 10:33 AM PT

Incident history · last 90 days

No incidents recorded

Application core

  • API Operational checked incident-derived

    Request handling for the Oryn web + desktop clients.

    No incidents
  • Database Operational checked incident-derived

    Postgres — case data, ledger entries, audit log.

    No incidents

Cache & storage

  • Redis cache Operational checked incident-derived

    Session + rate-limit data. Degradation slows the app but does not lose data.

    No incidents

Security

  • Auth0 sign-in Operational checked incident-derived

    JWKS for verifying user sessions. Degradation blocks new logins.

    No incidents
  • ClamAV file scanning Operational checked incident-derived

    Antivirus scan of every uploaded document.

    No incidents

Observability

  • Sentry error tracking Operational checked incident-derived

    Visibility into errors. Degradation is non-customer-impacting.

    No incidents

Infrastructure disclosure (R-7)

Oryn is currently deployed in a single region (us-west2 / Railway). Multi-region redundancy and automatic failover are not available during beta. Planned: post-beta GA release. Downtime in us-west2 affects all users simultaneously. Off-region backups in Cloudflare R2 (separate cloud, separate credentials) protect data even when the primary region is unreachable.