Keep your monitors. Change where the alert lands.

How it works

1. Create a free account and generate a relay token on the Integrations page. You get a URL that belongs to you.
2. Paste it into whatever already alerts you, as a webhook.
3. That is the whole setup. The next alert that tool fires comes to you through us.

curl -X POST https://alertkite.com/api/relay/YOUR_TOKEN \
  -H "content-type: application/json" \
  -d '{"source":"Uptime Kuma","message":"db-backup is down"}'

Both fields are optional and several aliases are accepted (msg, title), because most tools will not let you choose the field names. Anything that can POST JSON works without a plugin.

What people point at it

• Uptime Kuma

  Add a webhook notification and paste the URL. Self-hosted, stays self-hosted.

• UptimeRobot

  Add a web-hook alert contact. Keep all 50 of their free monitors.

• n8n, Make, Zapier

  An HTTP Request node. Replaces the paid step that was bridging this.

• GitHub Actions

  One curl in a failure step, so a red build reaches your phone.

• Any cron job

  Pipe a failure into curl. No agent, no library, no account on the box.

• Your own code

  A POST with a JSON body. If it can reach the internet, it can alert you.

What this is not

The relay does not check anything. Your existing tool decides what is broken and when — we only carry the message. That means an outage it misses is one we never hear about, and if that tool goes down, nothing tells you. If you want the checking as well, we do that too and the free plan includes 25 monitors. But you do not have to decide that today.

Relayed alerts are rate limited per token and metered like our own, so a misconfigured loop cannot quietly empty your allowance. Tokens are revocable one at a time.