Blind relay encryption
Event payloads are encrypted with AES-256-GCM before they leave WordPress, on HTTPS and plain HTTP sites alike, so the relay forwards ciphertext it cannot read.
The official WordPress plugin for the WPSignal realtime event service. Install, connect, and your site starts pushing events to browsers instantly. No polling. No server to manage.
< Setup />
No server to provision. No WebSocket infrastructure to manage.
Upload the plugin or install from the WordPress directory. Go to WP Admin > WordSocket and click Connect.
Post updates publish instantly without any code. Register custom triggers with the PHP builder to attach realtime events to any WordPress action hook.
The client script connects via WebSocket on page load. Every event fires a native CustomEvent on document. No polling, no framework required.
Need a visual guide? Watch this 1min demo
< Features />
Event payloads are encrypted with AES-256-GCM before they leave WordPress, on HTTPS and plain HTTP sites alike, so the relay forwards ciphertext it cannot read.
Map any WordPress action hook to a realtime event in one PHP call. Add a condition, custom channel, or transform the payload: all optional.
A public JavaScript API lets themes and plugins subscribe, publish, and listen for events without managing their own WebSocket connection.
Built-in admin page with live event log, publish form, token inspector, and connection status. Diagnose issues without leaving WordPress.
Yes. WordSocket relays events through the WPSignal server. Create a free account at wpsignal.io, then paste your API key into the plugin settings.
During registration: your site URL and name. During normal operation: event payloads, AES-256-GCM encrypted before they leave WordPress on HTTPS and plain HTTP sites alike, so the WPSignal server never sees their plaintext. When real-time collaboration is enabled, Yjs document updates are also relayed; these are not encrypted, so the server could read them, though it only forwards them and never parses or stores them. Data is not stored on the server.
The built-in client loads for logged-in users by default. Use the wpsignal_allow_client filter to load it for all visitors.
The client falls back to SSE automatically. Channel subscriptions are replayed on reconnect. Collaborative editing needs WebSocket, because SSE is receive-only. If the editor opens while the client is on SSE, collaboration stays off for that editor until the page is reloaded with WebSocket available.
Yes, for now. Real-time collaboration was removed from WordPress core before the 7.0 release and currently ships with the Gutenberg plugin. WordSocket detects when it is available and enabled, and skips registration otherwise.
Get Early
Create a WPSignal account, install WordSocket from the WordPress plugin directory, and connect in under a minute.