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.
Incident history · last 90 days
1 incident-affected day
Application core
- API Operational
Request handling for the Oryn web + desktop clients.
1d affected - Database Operational
Postgres — case data, ledger entries, audit log.
No incidents
Cache & storage
- Redis cache Operational
Session + rate-limit data. Degradation slows the app but does not lose data.
No incidents
Security
- Auth0 sign-in Operational
JWKS for verifying user sessions. Degradation blocks new logins.
No incidents - ClamAV file scanning Operational
Antivirus scan of every uploaded document.
No incidents
Observability
- Sentry error tracking Operational
Visibility into errors. Degradation is non-customer-impacting.
No incidents
Get notified when something changes
Email when an Oryn incident is published or updates status. Confirm via the link we send you — one-click unsubscribe in every message. No marketing, no other lists.
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.