Channels, presence and client events over the Pusher protocol. Keep pusher-js and your server library, point them at Vixus Push, and spend your week on the feature instead of the WebSocket fleet.
import Pusher from "pusher";
const pusher = new Pusher({ appId, key, secret, host });
await pusher.trigger("presence-room-7", "message", {
from: "linus",
text: "ship it",
});// features
The Pusher protocol you know, on infrastructure you don't have to run. Create an app, copy three values, and ship.
Keep pusher-js, Laravel Echo and every Pusher server library. Swap the cluster for a host, and your channel names, events and auth endpoint stay exactly as they are.
const pusher = new Pusher("YOUR_KEY", {
- cluster: "eu",
+ cluster: "",
+ wsHost: "YOUR_HOST",
+ wssPort: 443,
+ forceTLS: true,
+ enabledTransports: ["ws", "wss"],
channelAuthorization: { endpoint: "/api/pusher/auth" },
});
Broadcast to everyone, gate channels behind your own auth endpoint, or know who is online right now.
Typing indicators and cursors go straight from client to client on private and presence channels. One switch per app.
Publish, batch-publish, read channel info and list presence users from any backend. Every Pusher server library signs the requests for you.
// POST /apps/:id/batch_events, signed with your secret
await pusher.triggerBatch([
{ channel: "orders.4821", name: "status", data: { status: "packed" } },
{ channel: "private-user-ada", name: "notify", data: { order: 4821 } },
]);Invite your team into an organization. Roles decide who can see secrets, change settings or only look.
Messages, API calls and connections, by the hour, per app. Today's messages sit next to your daily limit.
Every app has a demo room. Send the link to a second browser, no account needed, and watch messages land in both.
// quickstart
These are the real snippets, with this service's host already filled in. Paste your app id and key and run them.
Sign up, create an app and copy its app_id, key and secret. The Free plan needs no card.
Point pusher-js at your host, subscribe to a channel and bind an event. Private and presence channels call your own auth endpoint.
Call trigger from any Pusher server library. The secret stays on your server; the key is the only thing that ships to browsers.
import Pusher from "pusher-js";
const pusher = new Pusher("YOUR_APP_KEY", {
cluster: "", // not used; the host below decides where you connect
wsHost: "ws.push.vixus.io",
wsPort: 443,
wssPort: 443,
forceTLS: true,
enabledTransports: ["ws", "wss"],
});
const channel = pusher.subscribe("my-channel");
channel.bind("my-event", (data) => console.log(data));More in the quickstart and the HTTP API reference.
// from the people shipping with it
Pick the part you care about and hear from someone who uses it.
We moved off Pusher on a Tuesday afternoon. The diff was theclusterline and a few new options; channel names, the auth endpoint and everybind()call stayed exactly as they were.
The "who's here" avatars on our shared documents are one presence channel.member_addedandmember_removedfire exactly when you'd expect, and the member list is there on subscribe.
Cursor positions go client to client with client- events, so our server never sees that firehose. Turning them on was a switch in Settings, plus a reconnect, which the docs warned me about.triggerBatch is the unsung hero: one signed request fans an order update out to the customer, the courier and the ops board. The docs flag up front that errors come back in the body, so that never bit us.Echo didn't need to know anything changed. I swapped thePUSHER_*variables in.env, rebuilt the Vite assets, and broadcasting just worked on the first deploy.
Contractors get the Developer role, finance gets Billing and never sees an app secret. When someone leaves, removing them takes effect on their next request, not whenever their session runs out.
The Usage tab answers "what did that release do to our message volume?" hour by hour. Having today's messages next to the daily limit on the Apps page saved us a surprised Monday.
In workshops I open the live demo link on my laptop and my phone, and the room watches messages land on both. Nobody needs an account, and the link expires after a day on its own.
Private channels go through our own auth endpoint, so the authorization decision stays in our code. The key ships to browsers, the secret never leaves our servers, and every snippet is written that way.
We pause our staging app when nobody is using it. New connections and publishes are refused, nothing is deleted, and resume brings it straight back. Rotating a secret is one button.
Our live classroom shows which students are in the room. Presence gave us the roster for free; the only code we wrote was the auth endpoint, and we already had that from Pusher.
The quickstart has the real host already filled in. I copied the browser and Node tabs, ran them, and had a message in the console before my coffee went cold.
// no surprises
Where Vixus Push matches Pusher and where it doesn't, before you find out in production. The full table lives in the docs.
Encrypted and cache channels are supported by Soketi underneath, but not yet covered by our tests. Moving an existing app? Follow the migration guide.
// pricing
These numbers come from the same catalog the service enforces. Paid plans aren't on sale yet, and their limits may change before they are.
Build and test your realtime features.
For products going live with real users.
For busy apps and teams that need headroom.
pusher.subscribe("your-next-feature")
Create an app on the Free plan and watch your first event arrive in the browser. No servers to run, no card to enter.