Feature overview

Powerful features for building realtime products that still feel controlled.

Everything from app credentials to delivery logs is organized to keep the system understandable while traffic grows.

Create isolated apps with separate keys, ownership, and event streams.

Route events through clear channels so subscriptions stay precise.

Send with cURL, fetch, axios, Guzzle, or any client that can issue a request.

Use queues and pub/sub to keep the API fast while workers handle delivery work.

Broadcast signed events to the exact connected clients that matter.

Persist messages for auditing, troubleshooting, replay, and post-incident analysis.

Manage apps, inspect channels, and follow event traffic from one dashboard.

Protect the surface with IP throttling and signed server-side forwarding.

Works with PHP, Node.js, Python, Go, Ruby, and any other HTTP-capable stack.

Why it works

Less magic. More visibility.

Simple architecture

One direct path from HTTP trigger to WebSocket delivery means the system is easy to reason about.

Developer friendly

The UI, logs, and data model make it clear what happened, when, and why.

Open and transparent

Inspect traffic, verify payloads, and keep the operational picture visible across the whole pipeline.

Launch

The API is small, the architecture is readable, and the first integration takes minutes.

Create account Back to home