EchoRelay
What is EchoRelay?
EchoRelay is a managed runtime for custom API integrations.
Teams that maintain their own adapters carry the cost of every change at the other end. A vendor renames a field and someone edits adapter code, deploys it, and hopes nothing else moved. A credential rotates and the adapter breaks until somebody notices. EchoRelay moves that work out of application code.
An integration is described once as configuration: what comes in, the target system, its credentials, the retry policy, and how the answer maps back. Each inbound request is validated and mapped, then answered synchronously, passed through as a stream, fanned out to several targets, or queued for delivery with automatic retry, a dead-letter queue and replay.
Every configuration change is versioned. Changes can be previewed, diffed, dry-run, scheduled, published and rolled back, so a vendor's API change or a credential rotation becomes a configuration edit rather than a release.
Integrations are built and operated through a REST API, an MCP server so an AI agent can do the wiring, or a web panel. All three edit the same versioned model. Every delivery leaves a receipt recording the target, the outcome, the attempts and the callback, so a question about whether an order arrived is answered from the record rather than from logs.
Free to start, no card required.
Teams that maintain their own adapters carry the cost of every change at the other end. A vendor renames a field and someone edits adapter code, deploys it, and hopes nothing else moved. A credential rotates and the adapter breaks until somebody notices. EchoRelay moves that work out of application code.
An integration is described once as configuration: what comes in, the target system, its credentials, the retry policy, and how the answer maps back. Each inbound request is validated and mapped, then answered synchronously, passed through as a stream, fanned out to several targets, or queued for delivery with automatic retry, a dead-letter queue and replay.
Every configuration change is versioned. Changes can be previewed, diffed, dry-run, scheduled, published and rolled back, so a vendor's API change or a credential rotation becomes a configuration edit rather than a release.
Integrations are built and operated through a REST API, an MCP server so an AI agent can do the wiring, or a web panel. All three edit the same versioned model. Every delivery leaves a receipt recording the target, the outcome, the attempts and the callback, so a question about whether an order arrived is answered from the record rather than from logs.
Free to start, no card required.
Categories & Use Cases
Media
1 / 6
Screenshot of One address in. Many systems out, each shaped by a configuration you can preview, publish and roll back. Deploy nothing.
