Remedy Connect the evidence and controls your repair workflow actually needs.
Every integration is labelled by status. Planned architecture is not presented as generally available functionality.
Source control
Remedy is repository-independent by design. GitHub, GitLab, Forgejo, Bitbucket and generic Git are intended connector targets for exact-commit repair workflows.
Runtime and infrastructure
Remedy Agent, Docker and Linux form the intended runtime evidence and capability layer. The Agent is in development; operational actions remain explicitly permissioned.
Observability and application evidence
Remedy Reporter and the existing Web, Node.js and React Native foundation provide native evidence paths. Sentry, Datadog and OpenTelemetry are planned connector directions, not replacement claims.
Database and deployment
PostgreSQL diagnostics and deployment connections are designed around read-only evidence, governed source change, existing CI/CD, Docker and customer-controlled self-hosted workflows.
Integration status
The labels below distinguish the working foundation from components being developed and architectural targets. They are not blanket claims of turnkey availability.
| Category | Connection | Status |
|---|---|---|
| Application evidence | Reporter, Web, Node.js, React Native foundations | Core foundation |
| Repair | Diagnosis, repair orchestration and verification | Core foundation |
| Runtime | Remedy Agent for Linux, services and Docker | In development |
| Probes | API, health and deterministic assertions | Planned expansion |
| Source control | GitHub, GitLab, Forgejo, Bitbucket, generic Git | Connector targets |
| Observability | Sentry, Datadog, OpenTelemetry | Planned connectors |
| Database | PostgreSQL read-only diagnostic evidence | Planned connector |
| Deployment | Docker, CI/CD and customer-hosted workflows | Workflow-dependent |
Frequently asked questions
Are all integrations available now?
No. The site distinguishes current foundations, components in development and planned connectors. Specific production availability should be confirmed during onboarding.
Can Remedy work without an observability platform?
It is designed with its own Reporter, SDK, Agent and Probe evidence paths while also allowing relevant external evidence in future connector workflows.
From bug report to verified fix.
See how Remedy connects evidence, diagnosis, repair, deterministic checks and production verification.
Explore the complete workflow →