Schero D.

plugin-io

@strapi-community/plugin-io attaches a Socket.IO server to Strapi 5 and sends an event whenever a watched document is created, updated, published, unpublished, has its draft discarded or is deleted. Each client receives only what its role or API token may read through the REST API, sanitized with the same Content API sanitizer Strapi uses.

The plugin lives in the Strapi community organization on GitHub. ComfortablyCoding started it; I maintain it and publish its releases on npm.

Install

npm install @strapi-community/plugin-io
plugin-io icon
Version
v6.0.0
Strapi
^5.38.0
Node.js
^22.21.0 || >=24.9.0 <=26.x.x
License
MIT, free
Released

Version, release date and ranges are read from the npm registry at build time.

Settings, Socket.IO, Monitoring in dark mode with connections and events
Live presence panel in the Content Manager showing who edits an entry
Socket.IO settings page in the Strapi admin
Monitoring view with event totals

What it does

Use it when

Frontends need to react to content changes in Strapi without polling.

Not for

Several processes without an adapter. Then events stay on the process that produced them, and the plugin warns at boot.

What it needs

Strapi 5.38 or later and Node.js 22.21+ or 24.9+. For several processes: @socket.io/postgres-adapter with pg, or @socket.io/redis-adapter with ioredis.

Questions

Which events does it send?

An event when a watched document is created, updated, published, unpublished, has its draft discarded or is deleted, for example article:publish.

Who receives an event?

Only clients whose role or API token may read that content through the REST API. Data is sanitized with Strapi's Content API sanitizer.

Does it work on Railway or with pm2 cluster mode?

Yes, with the Postgres or Redis adapter and WebSocket-only transport, because Railway and pm2 have no sticky sessions.

Full documentation

Other plugins