Skip to content

Your dedicated instance

SheerSight runs on a dedicated instance provisioned for your organization — a hardened, single-tenant environment that collects from your sources, runs detections, and reports into the console. You don't install or administer it; SheerSight stands it up for you and keeps it maintained.

How it works

  • Single-tenant. Your instance is yours alone. The raw data it collects stays on it and is never shared with other customers. Only short summaries reach the shared console (see How SheerSight works).
  • Outbound-only. It reaches out to your sources' APIs and to the console. Nothing is exposed inbound — no public IP, no open ports, no firewall changes on your side.
  • Read-only into your world. It collects using the read-only credentials you provide (see Connecting sources). SheerSight never needs inbound access to your network.

Getting set up

  1. You're invited. SheerSight provisions your dedicated instance and adds your work email to the access list.
  2. Sign in. Open the console and sign in with Zero-Trust access — your organization's SSO or a one-time PIN by email. See The console.
  3. Connect your sources. In Integrate → Sources, paste read-only credentials for the tools you want monitored; they're encrypted in your browser before they leave it. See Connecting sources.
  4. Confirm data is flowing. Sources move to live and detections begin appearing, usually within a few minutes.

Checking your instance status

  • The Sources panel shows each source's state: not connected, activating, live, partial, stalled or error. See Using the console for what each one means.
  • The relayed credentials panel shows each credential you submit as pending → applied once your instance loads it.

Not enrolled yet?

If the console shows your instance isn't enrolled yet, provisioning is still finishing. If that persists, contact us.

Troubleshooting

  • A source won't connect. Re-check the credential's read-only scope and any account/org/project IDs on the vendor side — see the per-source steps in Connecting sources.
  • No detections. Give a new source a few minutes; if it stays empty, confirm the credential is still valid in the vendor.
  • Still stuck. Contact support.