socket.io-valkey-adapter — Scale Socket.IO on open-source Valkey

The problem it solves

Real apps don't run on one server. Chat apps, live dashboards, multiplayer games, notifications — they run on 5, 10, 50 servers behind a load balancer. Without an adapter, each server is an island: it can only message its own clients. This package connects the islands. That's the entire job.

Server 1Client A 🔵

Server 2Client B 🟢

VALKEYPub/Sub bus

Server 3Client C 🟣

Server N…Client D 🟠

Why people use it

📈

Horizontal scaling

Add more servers without breaking real-time delivery.

💬

Chat & presence

Live chat, notifications, and presence across a whole cluster.

🎮

Games & live data

Multiplayer games, live leaderboards, collaborative editing.

📡

Cluster-wide rooms

Broadcast to rooms that span multiple servers, seamlessly.

🎯 Why this instead of socket.io-redis-adapter

The killer line: the same proven adapter, but on open-source Valkey instead of Redis.

	socket.io-redis-adapter	socket.io-valkey-adapter
Works	✅ battle-tested	✅ identical code (96 tests pass)
Backend	Redis	Valkey
License	No longer fully open source (RSALv2 / SSPL since 2024)	BSD — open source forever, Linux Foundation backed
Migration cost	—	Zero — drop-in, no code changes

The 3 top selling points

License freedom (the #1 reason)

In 2024 Redis changed its license away from pure open source. Many companies and OSS projects must move off Redis for legal/compliance reasons. Valkey is the official open-source fork (BSD, Linux Foundation). This package is their escape hatch — keep Socket.IO working, just point it at Valkey.

Drop-in, zero rewrite

Because Valkey speaks the same protocol as Redis, this adapter is byte-for-byte the same logic as the Redis one. A team switches by changing one import. No relearning, no risk — the "switch in 30 seconds" story is the whole appeal.

Future-proof & cost

Valkey is community-driven, actively developed, and free of the licensing/cost uncertainty hanging over Redis. Teams standardizing their whole stack on Valkey get a first-party Socket.IO integration that fits.

❌ before// tied to Redis
const { createAdapter } =
  require("@socket.io/redis-adapter");
const Redis = require("ioredis");

✅ after — one-line swap// now on open-source Valkey
const { createAdapter } =
  require("socket.io-valkey-adapter");
const Valkey = require("iovalkey");

Who it's for

Teams already on Socket.IO + Redis who want or need to leave Redis.
New projects choosing Valkey as their datastore and wanting real-time scaling.
Open-source projects that legally can't ship Redis anymore.

The value in one line: it removes the only thing tying Socket.IO scaling to Redis. It makes Valkey a first-class option.