Pusher Pricing in 2026: What You Actually Pay

Pusher Channels is the default "just add realtime" service for a lot of apps, and its pricing looks simple: pick a tier, pay a flat monthly price. That simplicity hides one meter that quietly decides your bill, and it is not the one most people budget for. This is the numbers-first version of Pusher pricing in 2026: the full ladder, three real monthly bills, the peak-connection trap that turns $99 into $499, and the point where self-hosting wins.

The meter that decides your bill: peak concurrent connections

Pusher Channels bills on two things (pricing page, July 2026): messages per day and concurrent connections. Your plan has to cover both, but in practice one of them sets your tier, and for most apps it is concurrent connections.

A connection is one live socket: one browser tab, one mobile app in the foreground, one dashboard left open. Concurrent means simultaneous. Pusher looks at your peak concurrent connections, the highest number of sockets open at the same instant during the billing period, and your plan must have a ceiling above that peak. Go over the ceiling and new connections are refused, so under-provisioning drops users rather than sending a surprise invoice.

Two things make this sting:

• Idle tabs count. A user who opened your dashboard at 9am and wandered off still holds a connection. Presence-heavy apps carry a lot of these.
• The peak, not the average, sets the price. You pay for your busiest 60 seconds all month.

Pusher's 2026 price ladder

Source: pusher.com/channels/pricing, July 2026. The message allowance is per day, not per month, so a chatty presence channel can burn it faster than you expect. Annual billing is offered at a discount Pusher does not publish a percentage for.

Three real 30-day bills

Each bill is set by whichever meter, connections or messages, forces the higher tier. Numbers use the published US list tiers.

Bill 1: the notifications feed (small B2B SaaS)

Around 300 daily users, but they do not all sit in the app at once. Peak concurrent connections land near 140 (dashboards open during business hours, including idle tabs). Messages peak near 180k per day (notifications plus light presence).

• Connections: 140 is over Sandbox's 100 ceiling, so free is out. Startup's 500 covers it.
• Messages: 180k is 18% of Startup's 1M.
• Bill: $49 per month (Startup).

The lesson is in what pushed you off free: connections, not messages. You are using under a fifth of the message allowance and paying because 140 sockets, most of them idle, exceeded a 100-connection cap.

Bill 2: the collaborative cursors app (multiplayer)

Live cursors and presence for a growing team tool. Peak concurrent around 1,600. Cursor movement is chatty, so messages run near 3.2M per day.

• Connections: 1,600 needs Pro's 2,000 ceiling; Startup's 500 is far too low.
• Messages: 3.2M fits under Pro's 4M per day.
• Bill: $99 per month (Pro).

Both meters land in the same tier, so the bill is predictable. This is the happy case.

Bill 3: the spiky consumer app (live scores, drops)

Most of the month it idles near 900 concurrent. Then a match or a product drop spikes it to about 6,200 concurrent for roughly 25 minutes, twice a month. Event-day messages hit around 9M per day.

• Baseline 900 would sit comfortably in Pro ($99).
• The spike is the problem: 6,200 concurrent blows past Business's 5,000 ceiling, so you need Premium's 10,000. The 9M messages would fit Business's 10M, but the connection ceiling forces the jump.
• Bill: $499 per month (Premium).

You are paying Premium for about 50 minutes of traffic a month. The alternative is staying on Business ($299) and having roughly 1,200 users refused at the exact moment your app matters most. That is the trap.

The peak-connection trap, in one number

Bill 3 is a 5x premium ($99 to $499) bought by under an hour of monthly peak. This is the most expensive misread in realtime budgeting: teams size their plan to average load, then a launch or a viral moment quietly re-tiers them for the whole month, or drops the users they worked hardest to earn. It is also why the "Pusher is a little expensive" complaints on Reddit usually trace back to concurrency, not messages.

If your load is spiky, the flat-tier model works against you. That is where a per-usage competitor, or self-hosting, changes the math.

Same app, three meters: why the bill can 6x

Realtime providers do not agree on what to charge for. Take Bill 2's app (1,600 peak concurrent, roughly 350 average concurrent connections across the month, about 90M messages per month, sustained multiplayer presence) and price it three ways.

Ably bills on consumption (pricing, July 2026): $2.50 per million messages, $1.00 per million connection-minutes, $1.00 per million channel-minutes, plus a $29 per month Standard base.

Liveblocks bills on collaboration time (pricing, July 2026): $0.002 per user-minute, counted only when two or more users share a room (solo sessions are free), on top of $30 per month of Pro credits.

How the estimates land:

• Ably: 90M messages x $2.50/M = $225, plus roughly 350 average connections x 43,200 minutes x $1.00/M = about $15, plus channel-minutes in the same range (about $9), plus the $29 base. The 90M messages dominate; Ably's per-message meter punishes chatty cursor traffic.
• Liveblocks: sustained presence is the worst case for a user-minute meter. Roughly 40 concurrent collaborators x 6 active hours x 22 workdays = about 317k user-minutes x $0.002 = around $634. Liveblocks is built for bursty document sessions, not always-on presence.

Now flip the app. A low-message, short-burst multiplayer doc editor (say 5M messages per month, intermittent sessions) inverts the ranking: Ably drops to roughly $12 to $40, Liveblocks can land under Pusher's floor, and Pusher's flat $49 to $99 becomes the expensive option.

The rule: match the meter to your usage shape, not the sticker price. Flat tiers (Pusher) reward steady, predictable connection counts. Per-message (Ably) rewards quiet-but-connected apps. Per-user-minute (Liveblocks) rewards short, dense collaboration. Put a chatty app on a per-message meter, or an always-on app on a per-user-minute meter, and you overpay by multiples.

When self-hosting beats Pusher

Soketi is an open-source, Pusher-protocol-compatible server (github.com/soketi/soketi). It is a genuine drop-in: keep the pusher-js client, point it at your own host, and most apps work unchanged. On a $6 to $12 per month VPS (a 2-vCPU Hetzner box or a small Fly machine) it comfortably holds a few thousand concurrent connections.

Worked comparison for Bill 2's app (1,600 peak):

• Pusher Pro: $99 per month, zero ops.
• Soketi on a $7 VPS: about $7 per month of compute, plus your time. You now own high availability (a single node is a single point of failure), horizontal scaling (add a Redis adapter and a load balancer past one machine), and monitoring, and there is no SLA or support line.

Crossover: under roughly 1,000 to 2,000 concurrent, if you can tolerate running infrastructure, self-hosting at $7 to $15 per month all-in beats $49 to $99 managed. Above that, or the moment you need multi-region, real HA, presence webhooks, or someone to call at 2am, managed wins and the $99 is cheap insurance. Centrifugo is the other serious self-host option; it uses its own protocol and ships more features (JWT auth, channel history, a built-in admin UI) at the cost of not being a pure Pusher drop-in.

If your realtime layer is one piece of a larger reactive backend, weigh it against a bundled option too. Our Convex pricing teardown prices realtime subscriptions as part of the database bill, and the when DIY beats SaaS at scale breakdown covers the ops-cost side of self-hosting honestly.

The honest summary

Pusher's flat tiers are the simplest realtime pricing to reason about and often the cheapest for steady, message-heavy apps. They punish two profiles: spiky traffic, where the peak sets the month, and apps that could ride a per-usage meter more cheaply. Price your actual usage shape before you pick, and re-check it after any launch that moves your peak.

Math check: on Pusher your bill is set by peak concurrent connections, not average load, so a single 25-minute spike from 900 to 6,200 connections is what turns a $99 month into a $499 one.