SR SignalRelay
Menu
Sign in Start trial

Your Agent can sleep. The Signal will still be there.

SignalRelay accepts authenticated webhooks and CloudEvents now, holds each Signal durably, and lets your Agent claim it when it runs.

Start a seven-day trial Read the docs

No card is required for the trial. Plans start at $5 per month.

Illustrative route Durable
10:42:16 github.pull_request Accepted
10:42:29 code-review-agent Claimed
10:43:04 claim_01J… Completed

Synthetic example. SignalRelay records the route; your Agent does the work.

From incoming request to completed Claim.

The producer sends work when it happens. The Agent collects it when it is ready. SignalRelay keeps the handoff clear between those two times.

  1. 01

    A Relay verifies and accepts the request

    GitHub and Slack requests use signed ingress. Native Signal intake uses a scoped Relay secret.

  2. 02

    The Signal stays Available for one Agent

    Each Relay routes to one Agent. Durable state and duplicate detection keep ownership visible.

  3. 03

    The Agent claims and finishes later

    HTTP and MCP clients create a time-bound Claim, then complete, defer, or fail it.

Built for useful Agents that do not need to run all day.

Use SignalRelay when the outside system pushes now, but the Agent can work on its own schedule.

GitHub maintenance

Hold pull request, issue, or repository events for a review or maintenance Agent.

Slack requests

Verify Slack Events API requests and route the normalized Signal to one assigned Agent.

Scheduled Agent work

Let a cron-run, desktop, or on-demand Agent pull pending Signals through HTTP or MCP.

A narrow bridge, by design.

SignalRelay separates incoming transport from Agent execution. That small boundary is the product.

SignalRelay does

  • Verify authenticated ingress.
  • Store one durable Signal envelope.
  • Route to one assigned Agent.
  • Track Claim state and outcome.

SignalRelay does not

  • Run or schedule Agent work.
  • Transform Signal payloads.
  • Build multi-step workflows.
  • Fan out one Signal to many Agents.

HTTP for simple clients. MCP for connected Agents.

Both access paths use the same Claim rules and lifecycle. Start with the interface your Agent already understands.

See integration paths

Start small. Keep the same route.

Every public plan includes HTTP and MCP access and a seven-day trial without a card.

Compare full plan limits

Solo

1 Agent · 10 Relays

5,000 Signals / month

$5 / month

Builder

3 Agents · 30 Relays

15,000 Signals / month

$12 / month

Studio

10 Agents · 100 Relays

50,000 Signals / month

$25 / month

Let the Agent run when the work is ready.

Set up one Agent, one Relay, and one complete Signal route.

Start trial