Get started in minutes
Create a project, copy its DSN, and send your first error. Use a first-party Condux SDK or point your existing Sentry SDK at Condux by changing the DSN.
1. Create a project and copy your DSN
Every project has a DSN, the address your SDK reports to.
Sign in, create a project, and open its developer guide. It shows a DSN of the form https://<key>@ingest.condux.ai/<project> and the exact setup snippet for your platform.
2. Send your first error
A first-party SDK, or the Sentry SDK you already use.
First-party SDKs are published and installable today: npm install @condux/node (also @condux/browser, @condux/nextjs, @condux/edge and @condux/react), pip install condux, dotnet add package Condux.Sdk, and gem install condux.
import { init, captureException } from "@condux/node";init({ dsn: process.env.CONDUX_DSN });try {doWork();} catch (error) {captureException(error);throw error;}
# Change the DSN, keep the codeSENTRY_DSN="https://<key>@ingest.condux.ai/<project>"
3. Watch it group and, optionally, fix it
The event becomes an issue; the Conductor can draft the PR.
- Grouped issues
Events fingerprint into deduplicated issues with exact per-hour charts.
- Alerts
Fire on new and regressed issues to Slack, email, Discord or a webhook.
- A fix PR
Ask the Conductor to open a draft pull request your team reviews and merges.
- No SDK option
Already on OpenTelemetry? Point your OTLP logs exporter at Condux instead.
Frequently asked questions
Where is the full documentation?
The in-app developer guide has the per-platform setup for every SDK, prefilled with your project's DSN. This page is the public quickstart; sign in to get your DSN and the full guide.
Do I need a first-party SDK?
No. Condux is Sentry-SDK compatible, so an existing Sentry SDK works by changing the DSN, and OpenTelemetry apps can report with no SDK at all.
How do I get my DSN?
Create a project in the dashboard. Each project has a DSN you paste into your SDK setup; the developer guide shows the exact snippet for your platform.