RetrySight Cloud staging is live.

Open Cloud

Security by deployment model

Controls and data residency for Lite, Cloud, and Enterprise — how telemetry moves, who can access it, and how to report issues.

Lite controls

  • API bound to 127.0.0.1 by default — no network exposure
  • Host-header guard blocks DNS rebinding when on loopback
  • Admin token stored in OS secure storage (Keychain / DPAPI / libsecret)
  • Data under your user profile — no cloud upload unless you configure remote ingest

Cloud tenancy

  • Row-level isolation — org_id on agents, tasks, and keys equals the account UUID
  • Per-account ingest keys (rk_live_*) — no shared global agent key; JWT account_id on dashboard GraphQL
  • Collectors push over HTTPS to cloud-staging.retrysight.com (X-Agent-Api-Key); dashboard is the same staging origin
  • Strict tenancy — requests without an account context are rejected
  • MEMBER views are additionally scoped to the developer email from the collector heartbeat
  • Prompt bodies off by default; rotate leaked keys (24h grace)

Enterprise controls

  • Full stack inside your network — manager, PostgreSQL, dashboard
  • OIDC / SAML SSO from Core; API key management with rotation grace
  • 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 at Cloud Scale
  • Optional ClickHouse dual-write at Integration and above
  • No third-party SaaS in the telemetry path

Data handling

Collectors read local IDE agent logs. Events batch to the manager (local in Lite, hosted at cloud-staging.retrysight.com in Cloud staging, on-prem in Enterprise) over authenticated REST. The dashboard queries via GraphQL. Cloud console detail: Cloud dashboard. Architecture: How RetrySight works.

Vulnerability reporting

Report issues privately. Contact details and disclosure expectations are in security.txt (RFC 9116).

Do not disclose publicly until we have had a reasonable window to investigate and remediate. We aim to acknowledge reports within a few business days.

Need a security review?

Ask for data residency docs, tier gating details, and SSO guides for your security team.