The EU-hosted, protocol-compatible Pusher alternative
MOJAQ's realtime service speaks the Pusher protocol, so your existing Pusher client libraries work unchanged — but connections are served from the EU and bundled with analytics, errors, uptime, render and flags.
EU-hosted in Helsinki · GDPR-native · free during the beta, no fixed end date
MOJAQ vs Pusher
| MOJAQ | Pusher | |
|---|---|---|
| Protocol | Pusher-protocol compatible — drop-in | Native |
| Data residency | EU — Helsinki | US / multi-region |
| Public / private / presence channels | Yes | Yes |
| Also included | Analytics · Errors · Uptime · Render · Flags | Realtime only |
| GDPR / DPA | GDPR-native, DPA included | DPA available |
| Price | Free during the private beta | Paid, per connection / message |
Why move realtime to the EU
Realtime streams look lightweight but they carry account ids, document and channel names, chat text, presence metadata and order or deployment state. Run that through US or multi-region infrastructure and your live event bus becomes another transfer to account for.
MOJAQ terminates WebSocket connections in Helsinki and handles the data in the EU, with a DPA included. Your realtime layer stops being a compliance asterisk and starts matching the data-residency story you already tell for the rest of your stack.
Drop-in, because it speaks the Pusher protocol
There is no client rewrite. MOJAQ implements the Pusher protocol, so the official Pusher client libraries connect after you swap the app key and host. Public, private and presence channels behave the same, and your private-channel auth endpoint keeps its existing shape.
On the backend, a Pusher-compatible server library publishes events the same way once you point it at MOJAQ. You change credentials and a host, not your realtime architecture, and you inherit analytics, errors, uptime, render and flags on the same key.
Switching is easy
Keep your Pusher client code. Point it at MOJAQ's app key and endpoint — public, private and presence channels behave the same.
Questions
Will my Pusher SDK work?
Yes — MOJAQ implements the Pusher protocol, so the official Pusher client libraries connect without code changes; you swap the key and host.
Where do connections terminate?
In the EU (Helsinki). No US transfer.
Is there a connection limit?
Each app gets a generous concurrent-connection allowance, raised per plan.
Move your realtime / websockets to the EU
One API key. Six tools. Your data in Helsinki. Free while we're in beta.
Request beta access →