Svix

Key capabilities

Sending webhooks

• Simple API: send a webhook with a single API call.
• Message fanout to multiple endpoints per customer.
• Multi-tenancy to isolate endpoints, logs, and configuration per customer.
• Advanced endpoints beyond standard webhooks, including polling endpoints, FIFO-ordered delivery, and endpoints that stream events into object storage, message brokers, and databases.
• Throttling and rate limiting per endpoint to protect slow or overloaded consumers.

Developer and customer experience

• Embeddable and standalone application portal for customers to add and remove endpoints, inspect logs, and view reports.
• Tools to simulate, inspect, and replay events for end-to-end debugging.
• Event filtering so each endpoint subscribes only to the events it cares about.
• Payload transformations to reshape or enrich payloads in flight before they reach each endpoint.
• Connectors and transformations to offer pre-built integrations for webhook consumers.

Reliability and scale

• Automatic and manual retries with exponential backoff to maximize deliverability.
• Logging and monitoring to track webhook delivery, detect failures, and notify customers.
• Designed to handle billions of webhooks, serving customers from startups to Fortune 500 companies.
• Multi-region delivery, including options such as US, EU, Canada, Australia, and more, to help meet data residency requirements.

Core products

• Svix Dispatch – webhook infrastructure for sending webhooks to customers.
• Svix Stream – data sharing and streaming platform so customers can route data to their own systems of choice.
• Svix Ingest – service for receiving webhooks at scale from external providers.
• Svix Play – webhook tester and debugger for testing, debugging, and inspecting webhooks.

Who Svix is for

• SaaS platforms and API providers that need to offer webhooks to their customers.
• Engineering teams that want to avoid building and maintaining their own webhook infrastructure.
• Organizations that require high reliability, observability, and a strong developer experience for webhooks.

Running the server

• The server can be run using the official Svix Docker image from Docker Hub or precompiled binaries.
• Configuration, deployment, and maintenance details are documented in the server README and related documentation.
• The open source server is designed to provide reliable delivery, retries, security, logging, and the Svix webhook API for self-hosted environments.

When to use open source vs. managed service

• The managed Svix service (webhooks as a service) is suitable when teams want Svix to operate the infrastructure, including scaling, monitoring, and security.
• The open source server is an option for teams that need to self-host for compliance, networking, or internal policy reasons.

For specific installation, configuration, or contribution instructions, callers should be directed to the official Svix documentation and GitHub repositories.

• Price: from $0 per month.
• Designed for small teams starting to send and receive webhooks for free.
• No credit card required.
• Uptime SLA of 99.9%.
• 200 messages per second.
• 30-day payload retention.
• Embeddable webhooks UI.
• Connectors and transformations included.
• Includes access to Svix Dispatch, Stream, and Ingest.

Professional plan

• Price: from $490 per month.
• For use cases that need a seamless brand experience, higher limits, and support.
• Includes everything in the Free plan, plus:
• Uptime SLA of 99.99%.
• 800 messages per second.
• 90-day payload retention.
• Fully unbranded experience.
• White-label headers.
• Static source IPs.

Enterprise plan

• Pricing: contact sales for a custom quote.
• For companies with strict security, compliance, and availability requirements.
• Includes, among other benefits:
• Enterprise support.
• Uptime SLA of 99.999%.
• Custom rate limits.
• Advanced endpoint types.
• OpenTelemetry log streaming.
• Enterprise security and compliance features.
• Cloud and on-premises deployment options (including FIPS 140-3 support).
• OIDC and SAML Single Sign-On (SSO) and other enterprise features.

How usage is counted

• Only attempted or transformed messages are counted toward usage.
• Messages filtered by Svix (for example, when there are no endpoints) are not counted.
• Retries are free and do not count toward usage.
• Each 64 KiB chunk of payload is billed as one message.
• Plans include an allowance of messages per month (for example, the Free and Professional plans each include 50,000 messages per month); additional messages are billed on a per-message basis, with volume discounts available through sales.

Startup and custom plans

• Early-stage startups may be eligible for special startup plans.
• Custom enterprise agreements, including annual contracts and volume discounts, are available by contacting the Svix sales team.

Common use cases

• Offering webhooks as part of a SaaS or API product.
• Replacing or augmenting an in-house webhook system that is difficult to maintain or scale.
• Providing reliable event notifications to customers' systems, including:
• User lifecycle events.
• Billing and payments events.
• Operational and workflow events.

Benefits reported by customers

Based on customer stories on the Svix website, typical benefits include:

• Launching webhook support significantly faster than building in-house.
• Reducing ongoing engineering time spent maintaining webhook infrastructure.
• Improving webhook reliability and reducing failed deliveries.
• Delivering a better developer experience, including self-serve management for webhook consumers.
• Unlocking new deals or avoiding lost deals by more quickly meeting integration requirements.

For specific customer stories, detailed case studies, or named customer examples, callers should be directed to the customers section of the Svix website.

Compliance

Svix advertises compliance with:

• SOC 2 Type II.
• HIPAA.
• PIPEDA.
• PCI-DSS.
• GDPR.
• CCPA.
• Additional enterprise security and compliance options are available on higher tiers.

Data residency and regions

• Svix operates in multiple regions to support data residency requirements.
• Delivery can be configured from regions such as US, EU, Canada, Australia, and others.
• Isolated regions and environment-level separation (for example, production, staging, and development) are supported.

Access control and audit

• Role-based access control (RBAC) is available, with more advanced options on higher plans.
• Audit logging of account activity is available on enterprise-oriented plans.
• Single sign-on options include Google Workspace SSO and enterprise SSO with OIDC and SAML on applicable plans.

For any security or compliance questions beyond what is listed here, callers should be directed to speak with Svix directly for the latest details and any required documentation.

Ask anyway — the agent will say plainly that it is not published rather than guess.