Migrate from Sentry to Epure in 60 seconds (DSN swap)

Migration is not a new client library. Epure speaks the Sentry wire shape your SDK already uses. You are changing host + project id in dsn and turning off product lines Epure discards on ingest.

60-second checklist

• Epure running — Install or Cloud waitlist; GET /health returns ok.
• Project DSN — Settings → SDK connection → copy https://PUBLIC_KEY@your-host/PROJECT_ID.
• Update env — SENTRY_DSN, NEXT_PUBLIC_SENTRY_DSN, or framework-specific vars.
• Init once per surface — client, server, worker; same options you already use.
• Zero discarded lines — tracesSampleRate: 0, replaysSessionSampleRate: 0, profilesSampleRate: 0 (Python: traces_sample_rate=0.0).
• Verify — Sentry.captureException(new Error('Epure verify')) → 202 → Issues row (Verify).

JavaScript / TypeScript

In Sentry.init, set dsn to your Epure project URL, keep environment and release, and set tracesSampleRate, profilesSampleRate, replaysSessionSampleRate, and replaysOnErrorSampleRate to 0. Sentry JS 8.x: add enableTracing: false when the option exists.

Next.js: set both SENTRY_DSN and NEXT_PUBLIC_SENTRY_DSN to the same project. Config files: Next.js integration (sentry.client.config.ts, sentry.server.config.ts). Docs depth: Migrate from Sentry.

Python / FastAPI

Keep FastApiIntegration or DjangoIntegration. Only dsn changes. Guide: FastAPI integration.

What not to expect

• No import of old Sentry issues — forward ingest only.
• No replay, APM, or profiling in Epure — keep Sentry if those are required.
• JS/TS sourcemaps yes; other languages stay on raw frames.