RetrySight Cloud staging is live.

Open Cloud
RetrySight
Download Lite Start trial
Documentation menu
Docs home

Docs cloud

Sign up and accounts

Create a RetrySight Cloud staging account, starter trial, roles, and how the per-account agent API key is issued.

On this page
  1. Create an account
  2. Login
  3. Roles
  4. Agent API key
  5. Rotate
  6. Automation (optional)
  7. Related

Signup creates one account (your organization), an OWNER user, and a unique ingest key. There is no shared dev-agent-key in Cloud.

Staging console: cloud-staging.retrysight.com.

Create an account

  1. Open cloud-staging.retrysight.com/signup (or use Start trial on retrysight.com).
  2. Enter organization name, slug, email, password, and display name.
  3. On success the manager:
    • Creates the account on the starter plan with a 14-day trial
    • Creates an OWNER membership
    • Generates a per-account agent API key (rk_live_*)
    • Issues a JWT with an account_id claim
  4. You land on Welcome (installer) then the dashboard — empty until a collector connects.

Login

cloud-staging.retrysight.com/login — email and password. If you belong to a single account, that account is selected automatically.

Roles

RoleAccess
OWNER / ADMINFull account dashboard — collectors, tasks, cost, Account settings, key copy/rotate
MEMBEROwn developer activity (matched by developer_email from the collector heartbeat)
VIEWERRead-only views

Platform operators use a separate secadmin path. That is not a customer login.

Agent API key

  • Created at signup; copy it from Account (owners/admins) or the Welcome installer panel.
  • Prefix rk_live_. Treat it like a password — it can write ingest for the whole account.
  • Account ID (Welcome) identifies the organization. Agent ID (Collectors → open a machine) identifies one laptop after the first heartbeat. Neither is the API key.
  • Signup may return account.agentApiKey once. Later views can be masked — copy it immediately.

Rotate

Account → Regenerate. Update every developer machine. The old key stays valid for the rotation grace window (default 24 hours).

Every machine in the org currently shares the same account key (fleet key). Per-developer sub-keys are not issued yet.

Automation (optional)

GraphQL signup accepts accountName, slug, email, password, and displayName, and returns token plus account { id name slug agentApiKey }. Prefer the dashboard unless you are provisioning accounts in bulk.

Cloud overview · Install the collector