Svix pricing in 2026: the real 30-day webhook bill (and why $490 is almost never a volume decision)
Svix bills webhooks on attempted messages, and in 2026 the Free, $20 Basic and $490 Professional plans all include the same 50,000 a month. A numbers-first teardown: three real 30-day bills, the 64 KiB chunking trap, why Free is a hard cap with no overage, and why the jump to $490 is about throughput, not volume.
Updated on September 28, 2026

On this page
Quick answer: Svix bills webhooks on "attempted messages," and in 2026 the Free, $20 Basic and $490 Professional plans all include the same 50,000 messages a month. Free is a hard cap with no overage at all, so crossing 50,000 pushes you onto Basic at $20. Basic and Professional then carry the identical $0.0001 per message overage, so Basic stays cheaper until roughly 4.75 million messages a month. Professional buys throughput (200 to 800 messages per second) and features like static source IPs, not more volume. The two line items that actually surprise people are the 64 KiB chunking rule and a feature gate that has nothing to do with how many webhooks you send.
What the meter actually counts
Svix sends webhooks on your behalf and bills a single unit: the attempted message. Two things are explicitly free on Svix's 2026 pricing page: retries, and messages that get filtered because no endpoint is subscribed. So a flaky consumer that forces five delivery attempts still costs you one message, and an event with no listeners costs you nothing.
The part nobody reads is the chunk rule. Svix counts each message in 64 KiB blocks. A payload up to 64 KiB is one message. A 180 KiB payload is three. That single line turns "50,000 free messages" into a moving target that depends on how fat your JSON is, not how many events you fire.
The four plans, in real 2026 numbers
Scroll to see more
| Plan | Price / mo | Included messages / mo | Throughput | Overage | Payload retention | What the price actually unlocks |
|---|---|---|---|---|---|---|
| Free | $0 | 50,000, hard cap | 50 msg/s | None. The plan stops at 50,000 | 7 days | No SLA, community support only |
| Basic | from $20 | 50,000 | 200 msg/s | $0.0001 / msg | 30 days | The right to go over 50,000 at all, 99.9% SLA, unbranded webhook headers |
| Professional | from $490 | 50,000 | 800 msg/s | $0.0001 / msg | 90 days | Static source IPs, unbranded application portal, object storage endpoints, advanced RBAC, 99.99% SLA |
| Enterprise | Custom | Custom | Custom | Custom | Custom | 99.999% SLA, SSO, mTLS, on-prem, volume terms |
Read that included-messages column twice. Free, Basic and Professional all include exactly 50,000. You do not buy volume anywhere on this ladder. What $20 buys is the right to exceed 50,000 at all; what $490 buys is 4x throughput and a short list of features.
Correction, September 28, 2026: this teardown previously published a three-plan ladder, put Free at 200 msg/s with overage at $0.0001 per message, and argued that "Free-plus-overage stays cheaper until roughly 4.95 million messages a month." All three claims are contradicted by Svix's own 2026 pricing page. Svix publishes four plans, not three. Free is capped at 50 msg/s, not 200, and its "Additional messages (on-demand)" cell is a dash rather than a rate, so Free carries no overage path at all. The 200 msg/s ceiling and the $0.0001 overage both belong to the $20 Basic plan, which this page did not carry. The corrected crossover is Basic against Professional at roughly 4.75 million messages a month. Every bill below has been recomputed.
Three real 30-day bills
Same rough event count, three very different invoices, each for a reason that is not obvious from the sticker.
Scroll to see more
| Cohort | Events / mo | Payload size | Billable messages | Plan | Monthly bill |
|---|---|---|---|---|---|
| Disciplined SaaS | 36,000 | under 64 KiB | 36,000 | Free | $0 |
| Payload-bloat app | 36,000 | ~180 KiB (x3) | 108,000 | Basic, forced off Free | $25.80 |
| Static-IP requirement | 21,000 | under 64 KiB | 21,000 | Professional (forced) | $490 |
Cohort 1: the disciplined SaaS pays $0
A B2B app fires order.created, order.updated, and subscription events: about 1,200 events a day, 36,000 a month. Each webhook is a thin envelope, well under 64 KiB. Average throughput is under half a message per second. That is 36,000 billable messages against a 50,000 free allowance. The bill is zero, and it stays zero until either the event count or the payload size moves.
Cohort 2: the payload-bloat app triples its own meter
Same 1,200 events a day. But this team ships the entire nested order object on every webhook, plus a base64 receipt thumbnail, so each payload lands around 180 KiB. At three 64 KiB chunks per message, 36,000 events become 108,000 billable messages. That is more than double the 50,000 Free allowance, and Free has no overage to absorb it, so the account has to move to Basic. The bill is $20 plus 58,000 overage messages at $0.0001, so $25.80 a month.
The $25.80 is not the point. The point is that they budgeted for 50,000 free events and actually got about 16,600, because every event spends three units. They hit the paywall at one third of the volume they planned for, and the invoice never explains why. The chunk rule did not merely add overage here, it pushed a genuinely small app off the Free plan altogether.
Cohort 3: the static-IP requirement is a $490 tax on 21,000 messages
A fintech customer will only accept your webhooks if they arrive from a fixed set of IP addresses they can allowlist in their firewall. Static source IPs are a Professional feature. This app sends 700 thin events a day, 21,000 a month, comfortably inside the free tier and worth exactly $0 on volume. One compliance checkbox moves it to $490 a month, or $5,880 a year, none of which is about webhook count. A nightly batch that bursts above 200 messages per second produces the same jump for a different reason.
There are two cliffs, and they cost $20 and $490
The first cliff is a volume one, and it is cheap. Free stops dead at 50,000 messages, so the moment the meter crosses that line you are on Basic at $20 a month. Nothing about throughput or features is involved.
The second cliff is the $490 one, and that one really is about features and throughput rather than count. Because Basic carries the same $0.0001 overage rate as Professional, you can run enormous volume on Basic before the plan price wins. Solve for it: the $470 gap between the two plans divided by $0.0001 is 4.7 million overage messages, plus the 50,000 included, so about 4.75 million messages a month before Professional beats Basic on volume alone. At 4.75 million messages spread across a month that is 1.8 messages per second on average, nowhere near the 200 msg/s Basic ceiling.
So the honest decision rule is short. Move to Basic when you cross 50,000 messages or need more than 50 msg/s. Move to Professional for burst throughput above 200 msg/s, for static source IPs, or for an unbranded application portal. Do not move to Professional because you crossed 50,000 messages. Below roughly 4.75 million a month, staying on Basic and paying overage is cheaper.
The cheaper lever: trim the envelope
The single highest-leverage move is to stop shipping fat payloads. Send a thin event: the type, the resource ID, and a timestamp, and let the consumer call your API for the full object if it wants detail. That keeps every message inside one 64 KiB chunk, which turns Cohort 2's 108,000 billable messages back into 36,000, puts the account back under the 50,000 cap, and takes the bill from $25.80 to $0. It also tightens your webhook contract, since consumers stop depending on the exact shape of a payload you might change later. This is the same "match the unit you are billed on" discipline that shows up in Ably's message meter, which we broke down in the Ably pricing teardown.
The escape hatch: Svix is MIT open source
If a feature gate rather than volume is what pushes you to $490, self-hosting is on the table. The Svix server is open source under the MIT license as svix-webhooks, a Rust service backed by PostgreSQL and an optional
Redis 6.2+ for the task queue. Run it yourself and both the per-message meter and the throughput ceiling disappear, and you control the egress IPs and branding outright, which are the exact two things the paid plan was gating.
The crossover is about features, not compute. Professional is $5,880 a year. A modest self-host stack (a small VPS, managed Postgres, a small Redis) runs in the rough range of $30 to $60 a month in 2026, call it $360 to $720 a year, plus your own operations time. If you were only paying $490 for static IPs or an unbranded application portal, self-hosting delivers both for a fraction of the cash cost. The trade you accept is real: you now own uptime, upgrades, and the managed add-ons and SLAs you give up. When the question is genuinely build versus buy, we walk the full math in when DIY beats SaaS at scale.
When paying actually earns its price
Managed Svix is worth the money in three honest cases. First, you send real burst volume and cannot afford to be throttled at 200 msg/s. Second, you have enterprise customers whose security teams demand static source IPs or a signed SLA, and self-hosting those guarantees would cost more in engineering time than $490 a month. Third, you want the surrounding products, since competitors such as Hookdeck meter events and throughput on a different curve and the right pick depends on which shape fits your traffic. Outside those cases, the Free plan with disciplined payloads is the correct default, and the $490 line item is a tax you have not yet earned.
Math check: Svix's $490 Professional plan includes the same 50,000 messages as the $20 Basic and $0 Free plans; Free is a hard cap, so the only volume cliff on this ladder costs $20, and on volume alone Basic-plus-overage stays cheaper than Professional until about 4.75 million messages a month.
Written by
Camille ForsterFrequently asked questions
Does Svix charge per webhook endpoint or per subscriber?
No. Svix bills per attempted message, not per endpoint or per subscriber. Adding more endpoints does not change the per-message meter described on its 2026 pricing page.
Do retries count against my Svix message quota?
No. Per Svix's 2026 pricing, retries and messages filtered out because no endpoint is subscribed are both free. Only attempted messages are counted.
What is the Svix 64 KiB chunking rule?
Each message is counted in 64 KiB blocks. A payload up to 64 KiB is one message; a 180 KiB payload is three. Large payloads silently multiply how fast you burn the free allowance.
Is the Svix Free plan enough for production in 2026?
For small apps, yes, but know exactly where it stops. Free includes 50,000 messages a month at up to 50 messages per second, with 7-day payload retention and no SLA. Svix publishes no overage rate on Free, so the plan is a hard cap: crossing 50,000 messages, or needing more than 50 msg/s, moves you to Basic at $20 a month.
When is the $490 Professional plan worth it?
When you need burst throughput above the 200 messages per second Basic allows, static source IPs for a customer firewall allowlist, or an unbranded application portal. Professional adds no included volume: it carries the same 50,000 messages as Basic and Free. Unbranded webhook headers are a $20 Basic feature, so check which kind of unbranding you actually need.
At what message volume does Professional beat Basic?
On volume alone, not until roughly 4.75 million messages a month: the $470 gap between the two plans divided by the $0.0001 overage rate is 4.7 million messages, plus the 50,000 included. Below that, the reasons to upgrade are throughput and features, not count. Professional never beats Free on volume, because Free is capped at 50,000 with no overage at all.
Can I self-host Svix instead of paying?
Yes. The Svix server is open source under the MIT license as svix-webhooks, a Rust service backed by PostgreSQL and optional Redis. Self-hosting removes the per-message meter and throughput cap, at the cost of running and operating the infrastructure yourself.
Related reading
Build vs buy: when DIY beats SaaS at scale
Build-vs-buy isn't a values debate, it's a breakeven date. SaaS wins early because it converts a big upfront build into a small monthly fee. DIY wins once your usage-based SaaS bill exceeds the fully-loaded cost of owning the code, typically around month 18 for infrastructure-style tools. This piece gives you the formula, a worked example, and the three traps that make teams build too early.
Ably Pricing in 2026: Why Your Bill Is Deliveries, Not Sends
Ably pricing in 2026 in real numbers: the three-meter model now shared across all six Ably products, per-delivery message counting, three worked 30-day bills, the volume-discount floor, and the lever that cut a bill 48.8%.
Pusher Pricing in 2026: What You Actually Pay
Pusher Channels pricing in 2026 runs from a free Sandbox (100 concurrent connections, 200k messages/day) to $49 Startup, $99 Pro, $299 Business, and up to $1,199, billed on two meters: peak concurrent connections and messages per day. The trap is peak connections, because your plan must cover your highest simultaneous connection count, so a single 25-minute spike can push you from $99 to $499 for the whole month. This teardown works three real monthly bills, shows why the same app costs $99 on Pusher, about $278 on Ably, and about $630 on Liveblocks purely because each bills on a different meter, and does the self-host crossover math with Soketi.

