Built for ourselves first
Condux was not planned as a product. We built it because we wanted it, and we only started selling it once we had been running on it for a while.
It started as something we needed
We were running Sentry on our own applications and it was more machinery than our problem called for. Most of it we never touched. What we did want was the part that goes past telling you something broke and actually proposes the fix, and that was the piece we could least justify paying for at the scale we were operating.
So we built a proof of concept: ingest the errors, group them properly, and let a model read the code behind one and open a pull request. It fitted the way we work almost immediately. We kept using it, kept sharpening it, and at some point it stopped being a proof of concept.
That history shapes what Condux is. It is deliberately smaller in surface than the incumbents, because it was built by people who wanted less of it, not more. Every feature in it earned its place by being something we needed on a real morning with a real production error.
We still run on it
Condux monitors Condux. The dashboard, the ingest relay and the background workers all report their own unhandled errors into it, and the Conductor opens fix pull requests against this codebase. When something is awkward, we are the ones it is awkward for, which turns out to be the most reliable roadmap we have.
A draft pull request, never a merge
The Conductor only ever opens a draft pull request. It does not merge, it does not push to your default branch, and nothing reaches production without a person reviewing it. Your CI runs on the pull request like any other. That boundary is deliberate and it is not configurable.
When a fix is merged, Condux watches the issue it was meant to solve. If the error stops occurring, the issue resolves itself with the evidence attached. If it comes back, the fix is marked as not having held, and the issue stays open.
Source-available, and portable
Condux is source-available under the Functional Source License. You can read it, self-host it and modify it, and every release becomes Apache-2.0 two years after it ships. Run it on our cloud or entirely inside your own boundary, on your own model key.
It is also deliberately easy to leave. Condux ingests the Sentry wire format, so an existing Sentry SDK works by changing one line, the DSN, and the same is true in reverse. Native OpenTelemetry logs work with no Condux SDK at all. Read the license summary.