Introduction
Every backend has that one small service. It receives a webhook and forwards it to three other systems. It started as 40 lines. Then one target went down for an hour, and messages were lost. So it got a retry loop. Then a queue. Then a second target needed a different payload. Then someone asked: "can it send billing questions to billing and bugs to support?"
That service is glue, and every team writes it again.
hikyaku (飛脚) is that service, written once. The name comes from the relay couriers of Edo-period Japan. They carried letters from station to station, and they found another way when a road was closed.
hikyaku is a message relay in a single Go binary:
It reads messages from one or more endpoints: a webhook, a WebSocket, a Kafka topic, an SQS queue and more.
It delivers them to one or more others.
One YAML file describes the whole relay.
Every step retries and falls back , so a message is never dropped without a trace.
An AI router can pick the destination of each message, and it…