Where is Apinator hosted?

Apinator is fully managed by us with data planes in the EU and the US. You pick the region per app when you create it. Payloads for an EU app never leave the EU region.

How does EU data residency work?

Pick the EU region when you create your app. WebSocket connections terminate at our EU data plane; event payloads, presence state, and connection metadata all stay in the EU. Our control plane (account info) also runs in the EU.

What happens during a reconnect?

The client SDK has built-in exponential-backoff reconnect. Apinator runs multiple nodes behind a load balancer per region, so clients reconnect to a healthy node transparently. In-flight subscriptions are restored; presence state is reconciled from Redis on the backend.

Do I need to think about sticky sessions or load balancing?

No. That is Apinator's problem. Internally the platform uses Redis pub/sub to fan out events across nodes so any node can serve any subscriber. You just call trigger() and every connected client receives it.

Is there a free tier?

Yes — the whole platform is free to use. No credit card, no trial, no paid plan above it. The current free plan includes 500 concurrent connections, 500,000 messages per day, 100 channels, and presence tracking up to 500 members per channel.

Fully Managed

Managed WebSocket Infrastructure, Production-Ready

Multi-region realtime channels, presence, and webhooks — without the ops.

Apinator is a production-grade, fully managed WebSocket platform. Channels, presence, pub/sub, and webhooks — in EU or US regions, with data residency you choose. No Docker, no load balancers, no on-call pager.

Get Started Free View Docs

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 serve clients from the closest region. Pick 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-Compatible

Existing Pusher client code works without changes. Drop in @apinator/client and keep your channels, presence, and auth flow.

Free to Use

No credit card, no trial, no paid tier above it. Presence, private channels, webhooks, 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.

quickstart.js
// 1. Create an app in the Apinator console, pick EU or US region,
//    copy the key + secret.

// 2. Connect from your frontend
import { RealtimeClient } from '@apinator/client'
const client = new RealtimeClient('APP_KEY', {
  host: 'wss://rt.apinator.io'
})
client.subscribe('updates').bind('change', (data) => refresh(data))

// 3. Publish events from your backend
import { ApinatorServer } from '@apinator/server'
const apinator = new ApinatorServer({ appId, key, secret })
await apinator.trigger('updates', 'change', { record: 42, action: 'created' })

Frequently Asked Questions

Pusher Alternative Migrate from Pusher How WebSockets Scale Scaling architecture explained Documentation Full setup and API reference

Ready to get started?

Completely free, no credit card required. Deploy in minutes.