Getting started

1. Create an account

Sign up at glitchreplay.com/sign-up. You start on the Free plan — 10,000 events/month, 14-day retention, one project, one seat. No card required.

2. Create a project

From the dashboard, click New project. Pick a slug (used in URLs and webhook payloads) and a platform — the platform tag controls which SDK snippet the dashboard shows you on the setup screen, but it does not affect ingest. You can change it later.

After the project is created you'll see a DSN on theSetup tab. It looks like:

https://<public_key>@glitchreplay.com/<project_id>

The public key is safe to ship in browser bundles — it's scoped to ingest only, and authenticates which project an event belongs to. It is not a secret. (The Sentry SDK convention; same trust model.)

3. Install an SDK

Any @sentry/* SDK works. The most common starter:

pnpm add @sentry/nextjs

// sentry.client.config.ts
import * as Sentry from "@sentry/nextjs";

Sentry.init({
  dsn: "<YOUR_DSN>",
  tracesSampleRate: 0,
  replaysSessionSampleRate: 0,
  replaysOnErrorSampleRate: 1.0,
  integrations: [
    Sentry.replayIntegration({
      maskAllText: true,
      maskAllInputs: true,
      blockAllMedia: true,
    }),
  ],
});

See SDK setup for React, Node.js, and the vanilla browser bundle, or Godot for game projects.

4. Trigger a test event

In the browser console of your app, run:

throw new Error("glitchreplay wiring test");

Within a few seconds the event appears on your project's Issues page, grouped by fingerprint. Delete the test issue from the issue detail view once you've confirmed.

5. (Optional) Upload source maps

Without source maps, every stack frame shows the minified bundle (e.g. lt at index-DLrL68bZ.js:1:10383). Wire the upload script into your build to get original file paths back. See Source maps.

What's next

• Replay — capture the last 30 seconds of DOM activity before each error: Session replay.
• Alerts — get pinged on new issues, spikes, or new releases: Alerts & notifications.
• PII rules — strip emails, headers, or custom fields server-side before storage: PII scrubbing.
• API access — pull issues into your own dashboards or CI: REST API.