Data residency

Agent telemetry can include file paths, error messages, test output, and prompts. RetrySight’s three products make different promises about where that data goes.

Lite

• API on 127.0.0.1 by default
• Data under your user profile
• No cloud upload unless you later configure remote ingest

Cloud

• Collectors on laptops push over HTTPS to https://cloud-staging.retrysight.com
• Dashboard at the same origin — JWT with account_id
• Row-level isolation: org_id on agents/tasks/keys equals the account UUID
• One per-account ingest key (rk_live_*); no global fleet key
• MEMBER role is additionally scoped to developer_email from the heartbeat
• Prompt bodies off by default (privacy.store-full-prompts: false)
• You are not running Postgres; retention follows the Cloud plan (free beta keeps a short hot window)

Details: Cloud overview and Security.

Enterprise

• Manager, PostgreSQL, and dashboard inside your network
• Collectors batch to your manager, not a vendor SaaS in the telemetry path
• BYO RDBMS: PostgreSQL default; MySQL/SQL Server best-effort; Oracle DBA-assisted
• Retention purge from Core; local archive at Analytics; network archive at Integration; object storage (S3/GCS/Azure) at Cloud Scale
• Optional ClickHouse dual-write at Integration+

SSO and keys

SSO (OIDC/SAML) is available from Core. Fleet agents authenticate with API keys, not the IdP. See SSO.

Deeper reading

• Security — controls by deployment model
• Self-hosted observability — why platform teams keep this on-prem
• Architecture