koigrid vs Svix
Outbound webhooks with HMAC signing and retries — the built-in alternative to Svix and Vercel webhooks.
Svix made webhooks-as-a-service a category: signed payloads, automatic retries, delivery logs. koigrid gives you the same — every platform event delivered to your URL, signed with HMAC-SHA256 and retried with backoff — but native to the platform your resources already live on, with no per-message bill.
| Feature | koigrid | Svix |
|---|---|---|
| Pricing | Included (no per-use fee) | Per message / MAU |
| Signed payloads (HMAC-SHA256) | Yes | Yes |
| Automatic retries + backoff | Yes (5 attempts, ~2h) | Yes |
| Delivery history / status | Yes | Yes |
| SSRF protection (no internal targets) | Yes | Partial |
| Events from your infra (apps, DBs, deploys…) | Native | You publish them yourself |
| Manage by AI agent | Native (API + CLI) | API |
What koigrid improves
Native to your events
Every koigrid event (deploys, DB failover, checks…) can fire a webhook — no glue code to publish them.
No per-message fee
Webhooks are included — no per-message or per-endpoint bill.
Secure by default
Signed with a per-webhook secret and blocked from hitting internal/private hosts (anti-SSRF).
Frequently asked questions
Is koigrid cheaper than Svix?
It depends on the workload. koigrid charges for the RAM and disk you reserve, by the hour, shared vCPU included, from a public price list — with bandwidth included and no per-request fees. Egress-heavy setups usually come out well ahead; see the estimate above.
Can I migrate from Svix without lock-in?
Yes. koigrid runs on portable primitives — standard PostgreSQL, S3-compatible storage and containers — so you can move in (or out) whenever you want.
Where is my data hosted?
In data centers in the EU, on servers we run ourselves. The privacy policy says exactly where.
Can I run everything from an API or an AI agent?
Yes — koigrid is API-first and agent-native: every action has an API and a scoped token, with llms.txt and OpenAPI so an LLM can operate it end to end.