# coss.com vs Svix (https://coss.com/compare/svix)

> Svix is the more complete webhooks service. coss.com Hooks covers the core, with a portal, on the API key you use for everything else.

Svix and coss.com Hooks work the same way: applications for your customers, event types, endpoints with their own secrets, a portal, and the same retry schedule. Svix goes further, with channels, transformations, FIFO endpoints, receiving webhooks (Ingest) and a self-hostable MIT server. coss.com Hooks sits next to email, SMS and the rest of coss.com, with no per-message price.

Facts about Svix checked on 2026-10-30 against the sources listed below.

## At a glance

| | coss.com | Svix |
| --- | --- | --- |
| Price | No per-message price: included in every coss.com plan, within the limits below | Free; Basic from $20 a month; Professional from $490 a month; 50,000 messages included, then $0.0001 a message |
| Send rate | 50 messages a second per organization (bursts of 200), 100,000 deliveries a day | 50, 200 or 800 messages a second by plan |
| Retries | 5 seconds, 5 minutes, 30 minutes, 2 hours, 5 hours, 10 hours, 10 hours | The same schedule |
| Failing endpoints | Disabled after 5 days of failures, with a webhook to you | Disabled after 5 days of failures |
| Signatures | Standard Webhooks headers (webhook-id, webhook-signature) | Unbranded webhook- headers from Basic |
| Portal | Included: your name, accent color and theme, embeddable on origins you allow | Embeddable on every plan; unbranded from Professional |
| Message retention | 30 days | 7, 30 or 90 days by plan; custom on Enterprise |
| Channels and transformations | — | Both, on every plan |
| Ordering | Not ordered: payloads carry their own timestamps | FIFO endpoints on Enterprise |
| Receiving webhooks | — | Ingest |
| Self-hosting | — | MIT-licensed server, Docker image |
| SSO | Scale and Enterprise | Google Workspace on every plan; OIDC and SAML on Enterprise |

## When Svix is the better choice

- **You need channels, transformations or custom headers.** Svix filters by channel as well as event type, and lets customers rewrite the URL, method, body and headers with JavaScript before delivery. coss.com Hooks has neither.
- **Order matters.** Svix offers FIFO endpoints on Enterprise. coss.com doesn't deliver in order.
- **You run it yourself.** Svix's server is MIT-licensed and ships as a Docker image, with an on-prem option on Enterprise.
- **You also receive webhooks.** Svix Ingest gives you endpoints to share with webhook providers. coss.com Hooks only sends.
- **Higher throughput and compliance terms.** Up to 800 messages a second on Professional, and HIPAA with a BAA, mTLS and custom regions on Enterprise.

## When coss.com is the better choice

- **No per-message bill.** Hooks has no meter: it comes with every coss.com plan, sandbox included.
- **It's on the account you already have.** One API key, SDK, audit log and dashboard for Hooks, email, SMS, Verify and Risk. Portal changes show in the audit log as made by the key that opened it.
- **Recovery built in.** Requeue every delivery an endpoint missed since a time, from the API or the portal.
- **Sandbox environments.** Sandbox keys deliver to real URLs under lower limits, so tests never mix with production messages.

## Moving from Svix

1. **Recreate event types and applications.** Svix's event types and applications map one to one: coss.hooks.eventTypes.create() and coss.hooks.applications.create() with your own uid for each customer. (/docs/hooks)
2. **Move endpoints and tell your customers.** Create each endpoint with coss.hooks.endpoints.create(). Its signing secret is new, so customers update it; receivers already on Standard Webhooks verification keep their code. (/docs/hooks/receiving)
3. **Swap the send and the portal.** Sending a message becomes coss.hooks.messages.send({ application, event_type, payload }), and portal links come from coss.hooks.portal.createSession(). (/docs/hooks/portal)

## Frequently asked questions

### What does coss.com Hooks cost?

Hooks has no per-message price: it is part of every coss.com plan, within its send and delivery limits. See coss.com/pricing for the plans.

### Is the retry schedule the same as Svix's?

Yes. Both retry after about 5 seconds, 5 minutes, 30 minutes, 2 hours, 5 hours, 10 hours and 10 hours, and both disable an endpoint that has failed for 5 days.

### Can my customers keep their verification code?

If they verify with a Standard Webhooks library, yes: coss.com sends webhook-id, webhook-timestamp and webhook-signature headers. They need the endpoint's new signing secret.

### Does coss.com Hooks support transformations or channels?

No. Endpoints filter by event type only, and payloads are delivered as sent. Svix has both.

## Sources

- [Svix pricing](https://www.svix.com/pricing/)
- [Svix docs: retries](https://docs.svix.com/retries)
- [Svix docs: channels](https://docs.svix.com/channels)
- [Svix docs: transformations](https://docs.svix.com/transformations)
- [svix-webhooks on GitHub](https://github.com/svix/svix-webhooks)