← Topics

Hosted Pusher-compatible services compared: keep pusher-js, change the host

Pusher, Vask, Soketify, Socketo, managed Reverb, Apinator and Hibira side by side: which keep pusher-js unchanged, how each counts messages, and where the servers are.

A hosted Pusher-compatible service runs the WebSocket servers for you and speaks the Pusher Channels protocol, so pusher-js, Laravel Echo and the Pusher server libraries keep working after you change the host, key and secret. Several services now offer this. They differ in how they count messages, where their servers are, what happens at a limit and what comes with the channels.

What "Pusher-compatible" should mean

Check three things before you switch:

  1. The client library stays. pusher-js or Laravel Echo connects with a different wsHost; you do not install a new client package.
  2. The server libraries stay. Your backend publishes with the official Pusher libraries for PHP, Node.js, Ruby, Python or Go through the same HTTP API.
  3. Auth and webhooks stay. Private and presence channel signatures, and webhook payloads, use Pusher's format, so your auth endpoint and webhook handler need no changes.

A service that passes all three is a configuration change. One that ships its own client package is closer to a rewrite, even if its channel model looks the same.

Hosted services side by side

Figures are from pusher.com/channels/pricing, vask.dev/pricing, soketify.com/pricing, socketo.dev, Laravel Cloud's pricing docs and apinator.io, checked on 2026-11-18. Hibira's are on the pricing page.

Pusher Channels99 US$Managed Reverb on Laravel Cloud100 US$Hibira19 US$Soketify19 US$Vask20 US$
Monthly price of the cheapest paid plan with at least 1,000 connections

How the counting changes your bill

The same traffic costs very different amounts depending on what a service counts. Take one server event sent to a channel with 200 subscribers:

  • Pusher Channels and managed Reverb count 201 messages: the publish plus each delivery. A busy presence channel uses up a daily allowance fast.
  • Hibira counts 1 message on paid plans, against a daily allowance, and still caps peak connections and data per month.
  • Vask and Socketo count 1 broadcast against a monthly allowance.

If your events go to large channels, a service that counts broadcasts once is several times cheaper. If most channels are private with one subscriber each, the counting matters less and price per connection matters more. The cost calculator compares Pusher, Ably and Hibira for your own numbers.

When each one fits

  • Pusher Channels: you want the original service, its 40-plus SDKs and US or EU clusters, and your fan-out is small.
  • Hibira: your users are in Hong Kong, Taiwan, Japan, Southeast Asia or nearby; you need presence channels larger than 100 members (presence-large- channels hold up to 100,000); or you want push notifications to iOS, Android and the web on the same plan. The dashboard, docs and support are in seven languages.
  • Vask or Socketo: your users are spread around the world and you want each to connect to a nearby edge location; Socketo can also run in your own Cloudflare account.
  • Soketify: you want a low price per connection and your users are mostly in the US or Europe.
  • Managed Reverb: your Laravel app already runs on Laravel Cloud.
  • Apinator: you are starting fresh, are fine with its own client package and want a free service with no paid tiers.

Detailed comparisons: Pusher, Vask, Socketo, Soketify and Laravel Reverb.

Self-hosted servers with the same protocol

If you would rather run the server yourself, Laravel Reverb, Soketi and Sockudo speak the same protocol, so the client code is the same. You take on the process, TLS, file limits, scaling across machines and upgrades. The Soketi alternatives and Laravel Reverb hosting pages cover those options.

What switching looks like

For a Laravel app, only .env changes:

BROADCAST_CONNECTION=pusher
PUSHER_APP_ID=YOUR_APP_ID
PUSHER_APP_KEY=YOUR_APP_KEY
PUSHER_APP_SECRET=YOUR_APP_SECRET
PUSHER_HOST=ws.hibira.io
PUSHER_PORT=443
PUSHER_SCHEME=https

In pusher-js, set wsHost to the new host and keep forceTLS: true. To switch without downtime, publish each event to both services for a while, release the client change, and stop publishing to the old one when its connections reach zero. The migration guide walks through each step.

Common questions

Which hosted services work with pusher-js without changes?

Pusher Channels itself, Hibira, Vask, Soketify, Socketo and managed Reverb on Laravel Cloud all accept pusher-js and Laravel Echo with a different host. Apinator follows Pusher's channel model but asks you to replace pusher-js with its own client.

What is the cheapest hosted Pusher alternative?

It depends on your fan-out. By price per connection, Soketify and Vask are the lowest. If your events go to channels with many subscribers, a service that counts each broadcast once, such as Hibira, Vask or Socketo, costs far less than one that counts every delivery.

Is there a Pusher-compatible service with servers in Asia?

Hibira runs in Hong Kong, which gives low round trips to Taiwan, southern China, Japan, Korea and Southeast Asia. Pusher has an Asian cluster too, and edge services such as Vask and Socketo connect each user to a nearby location.

Do I need to change my backend to switch?

No. The Pusher server libraries take a host option, so you change the host, key and secret. Channel names, events, auth endpoints and webhook handlers stay as they are.

Product names are trademarks of their owners.