Migrate

Switch from Sentry. Keep your SDK, change the DSN.

Condux speaks the Sentry wire format, so migrating is a one-line change, not a rewrite. Your existing SDK keeps sending events; they just arrive in Condux, where an AI fix engine can open the PR.

The whole migration

Change the DSN. That is the migration.

Before and after (any Sentry SDK)
// Before: reporting to Sentry
Sentry.init({ dsn: "https://abc123@o456.ingest.sentry.io/789" });
// After: same SDK, new DSN, now reporting to Condux
Sentry.init({ dsn: "https://abc123@ingest.condux.ai/019faf08-..." });

Provision a project in Condux, copy its DSN, and paste it in place of your Sentry DSN. That is it. No new SDK, no new event shape, no code churn.

What carries over, and what you gain

You keep the good parts and drop the sharp edges.

  • Your SDK and instrumentation

    Unchanged. The Sentry envelope is the wire contract.

  • Grouped issues and stack traces

    Events fingerprint into deduplicated issues with exact per-hour charts.

  • An AI fix engine

    The Conductor opens draft PRs your team reviews and merges. Included in the plan.

  • Free seats and hard caps

    No per-contributor AI pricing, and caps that throttle instead of surprise-billing.

  • A real self-host option

    One Compose stack or Helm chart under the FSL, with the AI running on your own key.

Frequently asked questions

Do I have to rewrite my instrumentation?

No. Condux ingests the Sentry envelope and store formats, so your existing Sentry SDK keeps working. You change the DSN and events start flowing into Condux.

Which SDKs work?

Any Sentry SDK that sends the standard envelope or store payload. Condux also ships first-party SDKs and accepts native OpenTelemetry logs if you would rather report with no SDK at all.

What do I gain by switching?

The Conductor, an AI fix engine that opens draft pull requests your team reviews and merges, free unlimited seats, hard caps instead of surprise overage bills, and a first-class self-host path under the FSL.

Can I run both during the migration?

Yes. Point a staging service at Condux first, confirm the issues and grouping look right, then move production by changing the DSN there too.

Keep exploring

Start catching errors in minutes

Create a project, send your first event and let the Conductor open your first fix.

Get started free