Remedy AI software remediation for self-hosted applications.
Keep source and workloads on customer infrastructure while granting Remedy only the repository, evidence and actions required for each workflow.
A self-hosted operating model
Source may live on a self-hosted Git server while the application runs on customer infrastructure. Remedy Agent provides configured runtime evidence through an outbound connection, and repair workers operate only against authorised repository state.
Customer policy governs deployment
The organisation decides which services, repositories, environments and operational capabilities Remedy can access. Deployment may remain entirely within existing customer CI/CD and approval processes.
Useful for private and bespoke software
This architecture is intended for self-hosted SaaS, internal applications, private APIs, backend services and bespoke systems where a public GitHub-and-cloud-only workflow would not fit.
Frequently asked questions
Must source code be hosted in the cloud?
No. The repository model is designed to support authorised self-hosted Git sources where a supported connection can be established.
Does Remedy require inbound server access?
The intended Agent model communicates outbound and uses explicit capabilities rather than a general inbound administration channel.
From bug report to verified fix.
See how Remedy connects evidence, diagnosis, repair, deterministic checks and production verification.
Explore the complete workflow →