The archive · Developer & Business Tools · Product decision · 2022–2026
Svix open-sources its Rust webhook dispatcher; service still live in 2026
Svix sells reliable webhook delivery as a service; its Feb 2022 open-source Rust dispatcher drew 176 HN points and still runs in 2026
Svix
What the business is
Svix is a webhooks-as-a-service company: developers make one API call and Svix takes care of deliverability, retries, signing and security, sold as a hosted cloud service plus a self-hostable open-source Rust server.
How it started
Svix's own customers wanted webhooks to build integrations and workflows, but the team was not willing to commit the engineering time, resources and ongoing maintenance a webhook delivery system requires — so delivery became the product. Open-sourcing the dispatcher was one of the first tickets created on the issue tracker, and it shipped on 2022-02-15 with a Show HN post explaining the move.
What happened
The open-source release was scoped for self-hosting: Docker images, configuration files, symmetric and asymmetric payload signing, OpenTelemetry tracing, Redis retry queues and dead-letter handling, with the team noting that the hosted service runs far more complex infrastructure and that feature parity was a work in progress. Client libraries now span Go, Python, TypeScript, Java, Kotlin, Ruby, C#, Rust, PHP and Terraform.
How it ended up
Still running as of 2026-09-05: the svix-webhooks repo holds 3.4k stars, 278 forks and 3,922 commits, and svix.com continues to sell the hosted enterprise service with the open-source server maintained alongside it.
Background
Svix is a webhooks-as-a-service company: developers make one API call and Svix takes care of deliverability, retries, signing and security, sold as a hosted cloud service plus a self-hostable open-source Rust server.
The origin was first-party pain: Svix's own customers wanted webhooks to build integrations and workflows, but the team was not willing to commit the engineering time, resources and ongoing maintenance a webhook delivery system requires. So delivery became the product, and open-sourcing the dispatcher was one of the first tickets created on the issue tracker.
The dispatcher shipped on 2022-02-15 as 'Svix – Open-Source Webhooks Service Written in Rust', drawing 176 points and 28 comments on Hacker News, where the founders explained the bet: webhooks are 'currently a mess', done differently everywhere, and open source was the way to make them reliable and consistent. The release was scoped for self-hosting — Docker, Postgres, optional Redis, signed payloads — while the hosted service stayed the business.
As of the 2026-09-05 snapshot the project is still live: 3.4k GitHub stars, 278 forks, 3,922 commits, and an enterprise hosted service still marketed on svix.com, with the open-source server maintained as a documented product of its own.
What has to be true
- The pain was first-party: their own customers asked for webhooks, and the maintenance burden was the blocker.
- Open source made an infrastructure service inspectable before purchase, matching the founder's history as a maintainer.
- Rust's single static binary and Docker setup made self-hosting credible, turning skeptics into evaluators.
- The hosted service stayed the business; the OSS repo became the trust layer and funnel for it.
What can be applied
If every engineering team feels the same undifferentiated pain — webhook delivery — sell the fix instead of building it once for yourself; open-source the core so buyers can verify before they trust.
Aftermath
As of 2026-09-05 the svix-webhooks repo still receives commits (3,922 total) and shows 3.4k stars and 278 forks; svix.com continues to market the hosted enterprise service, self-reporting SOC 2 Type II compliance, multi-region delivery, an embeddable webhook portal, and Svix's lead role in creating the Standard Webhooks specification. The open-source server is maintained as a documented product of its own alongside the hosted offering.
Sources
spotted an error? The archive wants to know.
Your turn
You just read one. Describe what you are building, and see who is betting on the same thing.
Free account · 3 free questions · no card