Managed WebSocket Infrastructure, Production-Ready
Multi-region realtime channels, presence, and client events — without the ops.
Apinator is a production-grade, fully managed WebSocket platform. Channels, presence, and pub/sub — in EU or US regions, with data residency you choose. No Docker, no load balancers, no on-call pager.
EU Data Residency
Pick the EU region and event payloads stay in the EU. Useful for healthcare, finance, and teams with GDPR obligations that do not want data in the US.
No Per-Message Billing
Apinator is free to use — no per-message fees, no peak-connection overage, no surprise invoices when traffic spikes.
Multi-Region Topology
EU and US data planes run independently. Choose US or EU per app — connections stay close to your users and your data stays where you want it.
Zero Ops
No servers, no Docker, no Redis to monitor, no Caddy certificates to rotate. Create an app in the console and start publishing.
Pusher-Style Channels
The same channel model as Pusher. Swap in @apinator/client and keep your channel names, events, and auth signature format.
Free to Use
No credit card, no trial, no paid tier above it. Presence, private channels, client events, and multi-region are all included.
Connect and Publish
Create an app in the console, then connect from your frontend and publish from your backend. No infrastructure to run.
// 1. Create an app in the Apinator console, pick EU or US region,
// copy the key + secret.
// 2. Connect from your frontend
import { Apinator } from '@apinator/client'
const client = new Apinator({
appKey: 'APP_KEY',
cluster: 'eu'
})
client.connect().subscribe('updates').bind('change', (data) => refresh(data))
// 3. Publish events from your backend
import { Apinator } from '@apinator/server'
const apinator = new Apinator({ appId, key, secret, cluster })
await apinator.trigger({ name: 'change', channel: 'updates', data: JSON.stringify({ record: 42, action: 'created' }) })Frequently Asked Questions
From the blog
What Is WebSocket Infrastructure?
WebSocket infrastructure is the layer that manages persistent connections at scale — handling auth, routing, fanout, and delivery so your app doesn't have to.
How to Scale WebSockets to 1 Million Connections
Scaling WebSockets beyond a single server requires careful architecture. Here's what actually breaks and how to fix it — from sticky sessions to Redis fanout and horizontal scaling.
Redis Pub/Sub Explained
Redis Pub/Sub is the backbone of most WebSocket scaling architectures. Here's how it works, what it's good at, and where it falls short.
WebSocket Load Balancing Explained
Load balancing WebSockets is trickier than HTTP — persistent connections and stateful servers mean round-robin doesn't cut it. Here's what actually works.
Ready to get started?
Completely free, no credit card required. Deploy in minutes.