Remedy The Remedy SDK gives incidents the application context they need.
Designed around Web, Node.js and React Native foundations, with an architecture that can extend to additional runtimes without making language recognition the proof standard.
Application-level evidence
The Remedy SDK is the embedded instrumentation layer for relevant errors, bounded recent events, route or screen context, application version and other configured diagnostics. It supports both human-reported incidents and machine-detected application failures.
Current foundations and planned expansion
The current Remedy foundation has been developed around web, Node.js and React Native project needs. The architecture is designed for additional adapters such as Python, .NET, Java, Go, Rust, C/C++, Flutter/Dart, native mobile and desktop applications; these should not be read as claims of universal turnkey availability today.
Language-independent repair philosophy
Remedy is not fundamentally restricted to a programming language. When an authorised repository, reproducible environment and meaningful deterministic gates are available, the repair workflow can be designed around the project’s own tools rather than a single ecosystem.
Frequently asked questions
Are all listed SDKs available now?
No. Web, Node.js and React Native describe the current foundation; additional language and runtime adapters are planned or architectural targets unless specifically confirmed.
What prevents sensitive data collection?
Project configuration, bounded event capture, sanitisation and credential rejection form part of the intended evidence controls.
From bug report to verified fix.
See how Remedy connects evidence, diagnosis, repair, deterministic checks and production verification.
Explore the complete workflow →