Docs · Get started

Three steps.
No setup wizard

Drop the SDK into your <head>, or install the browser extension. Each captured failure becomes a ticket on the board — no configuration files, no build step.

Install the SDK

One line in the document head:

index.html

html

<script
  src="https://optics-qa.com/sdk/v1/optic.js"
  data-key="YOUR_PROJECT_KEY"
  async
></script>

Or via npm if you prefer a build-step install:

terminal

bash

$ pnpm add @optic/browser

Initialise

Module-style init — call once on app boot:

app.ts

import { Optic } from "@optic/browser";

Optic.init({
  apiKey: "YOUR_PROJECT_KEY",
  projectId: "YOUR_PROJECT_ID",
});

That’s it. The SDK starts the recorder, registers the error and network listeners, and begins masking PII at the DOM boundary.

Or install the extension

Prefer a zero-code path for QA? Install the Optic browser extension. While anyone on your team browses, the extension records what’s happening, runs end-to-end tests around any failure it catches, and logs the bug before the tab closes — same data, no SDK required.

What you get out of the box

Full-fidelity DOM session replay around each failure.
Errors, slow requests, and broken flows — auto-captured.
Smart triage: severity inferred, owner assigned from the failing module.
PR-ready tickets with replay link, stack trace, and starter branch name.
Privacy-first: PII masked at the SDK before anything leaves the browser.

Where to next

Sign in to create a project key, then come back and paste it into the snippet above. Need a hand? support@optics-qa.com replies the same day.

Ready

Create a project. Paste the snippet

Your first 3 days are on us. No credit card. Cancel by removing the script tag.

Start 3-day trial

Three steps.No setup wizard.