RetrySight Cloud staging is live.

Open Cloud
Documentation menu
Docs home

Docs get-started

Lite vs Cloud vs Enterprise

Choose local Lite, managed Cloud, or self-hosted Enterprise based on who needs visibility and where telemetry can live.

On this page
  1. RetrySight Lite
  2. RetrySight Cloud
  3. RetrySight Enterprise
  4. Rule of thumb

Pick the deployment that matches who is looking at the data and where it is allowed to live. You can start on Lite and move to Cloud or Enterprise later — collectors still read the same local agent logs.

RetrySight Lite

Use Lite when you want visibility on your machine only.

  • Free, open-source Flutter desktop app (macOS, Windows, Linux)
  • In-process collectors — no Docker, no fleet agent service
  • REST, GraphQL, and MCP on 127.0.0.1:18081
  • No cloud upload unless you later point it at a remote manager

Start here: Lite quickstart or download Lite.

RetrySight Cloud

Use Cloud when a team needs one console and you are fine with a managed manager.

  • We host the manager and dashboard at cloud-staging.retrysight.com (staging)
  • Fleet collectors run on developer laptops (bundled JRE — no JDK)
  • Per-account ingest keys (rk_live_*) and row-level multi-tenant isolation
  • Full Cloud collector set (including traces and git context) — not Enterprise tier gates

Start here: Cloud quickstart or Cloud overview.

RetrySight Enterprise

Use Enterprise when telemetry must stay inside your network.

  • Self-hosted manager, PostgreSQL, and dashboard
  • Four tiers: Core (free), Analytics, Integration, Cloud Scale
  • Fleet agent installers plus Docker images and a Helm chart
  • SSO from Core; MCP, ClickHouse, and object archive unlock at higher tiers

Start here: Enterprise Core quickstart or compare tiers.

Rule of thumb

  • Solo, local-only → Lite
  • Team, managed → Cloud
  • Fleet + data residency → Enterprise Core, then upgrade tiers as you need FinOps, MCP, or archive