Migrating from Svix
The signature scheme is the same on both sides, which removes the part that usually breaks. What is left is inventory and the portal.
In short
- Consumers verifying Standard Webhooks signatures need no change — Svix wrote that spec and we implement it.
- Destinations, secrets and event types are the inventory to move.
- The real work is the embeddable portal, which we do not have yet.
- Move per tenant, and keep Svix able to deliver until the batch is proven.
How to read this page. Every claim about another product below was read off that company's own public pages on 16 August 2026, and each one links to the page it came from — check it yourself, that is what the links are for. Pricing and features move without anyone telling us, so our build fails if this page goes more than 120 days without a re-check. Everything stated about HookGet is something you can verify in the product today. If we have something wrong, tell us and it is fixed the same day.
What transfers cleanly
| Thing | How it moves |
|---|---|
| Signature verification | Unchanged. Both sides are Standard Webhooks |
| Destination URLs | Recreated through POST /v1/endpoints |
| Event types | Recreated, with an optional JSON Schema per type |
| Event type filters per destination | Same idea: a list of types on the endpoint |
| Secrets | New secret per destination, or rotate onto ours during an overlap window |
What needs a decision
- The customer portal. If your users log into Svix's embeddable portal today, there is no equivalent here yet. This is the honest blocker, and it is the reason to wait if the portal is load-bearing for you.
- Transformations. If you reshape payloads per destination, that logic has to move into your publisher before you migrate.
- Compliance. If a SOC 2 report is in your customer contracts, we do not have one.
A safe order of operations
- Open a HookGet account and prove one delivery end to end on the test project.
- Recreate destinations for one small tenant. Keep Svix running.
- Publish to both systems for that tenant and compare the delivery logs.
- Stop publishing to Svix for that tenant. Watch the timeline for a day.
- Repeat in batches, largest last.
- Only then remove the old integration from your publisher.
Verified 16 August 2026 against: Svix pricing · Svix retry schedule. Re-checked at least every 120 days.