Integrations
Opsis turns real user sessions into proven bugs. You're not locked into one vendor: bring whatever session and error tools you already run. Connect more than one if you like; every connected source flows through the same analysis pipeline.
One-click OAuth sources
These connect in a single OAuth click, with no API keys to copy. Self-hosted or SSO orgs can use a scoped API token instead.
| Source | What Opsis reads |
|---|---|
| PostHog | Session replay. Connect via one-click OAuth (read-only scopes); Opsis pulls replays and event signals. Detailed setup on the PostHog page. |
| Sentry | Errors and issues. One-click OAuth, no API keys. Opsis imports recent issues and cross-references them with session signals. |
Full PostHog setup, scopes, and troubleshooting: PostHog integration.
Read-only key sources
These tools don't offer self-serve OAuth, so Opsis reads them with a read-only key you generate, following the exact steps shown in-app. Keys are stored encrypted (AES-256-GCM) and used only server-side.
| Source | What Opsis reads |
|---|---|
| Amplitude | Product analytics. Connect with a read-only API key following the in-app steps; Opsis imports behavioral events for analysis. |
| Microsoft Clarity | Free session replay and heatmaps. Connect with a read-only key; Opsis ingests sessions and signals. |
| Datadog RUM | Real-user monitoring and errors. A scoped, read-only API key + application key gives Opsis access to RUM sessions and error events. |
| Mixpanel | Product analytics + session replay. Connect with a Mixpanel service account; Opsis exports session record events and signs replay chunk URLs. |
First-party Opsis SDK
Prefer not to depend on a third party at all? Opsis ships a zero-dependency browser recorder you drop in with one script tag. It streams uncaught errors, failed requests, and a value-free interaction timeline straight to Opsis. Input values are never read and query strings are stripped before anything leaves the page. Two modes are available: initOpsis (first-party) and initOpsisWithPostHog (a thin wrapper for teams already on PostHog session replay).
The SDK also ships its own heatmaps (Pro+) — turn on captureHeatmapCoords during init to aggregate click, scroll and attention maps across every session. Coordinates are normalized 0–1 document fractions, so no PII is added. See the heatmaps guide.
Security, across every source
- OAuth access and refresh tokens are encrypted at rest and never sent to your browser.
- API keys are read-only, encrypted at rest, and never exposed client-side.
- All imported text passes through redaction before being stored or analyzed. See Privacy & redaction.
- You can revoke any source anytime from your project's Integrations tab.
Related
- Scans & retention: how and when each connected source is imported.
- Quickstart: connect a source and run your first scan.