Skip to content
Projects

jamsocket/plane has 2,028 GitHub stars and 50 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-07 23:23 UTC. Last push 2026-01-13.

How these counts are measured

A distributed system for running WebSocket services at scale.

Measured star growth

in 24h
0
in 7 days
Collecting history
in 15 days
Collecting history
in 1 month
Collecting history

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

README.md

Original

Docker image Build Docker Image Tests Chat on Discord crates.io

Plane is a distributed system for running stateful WebSocket backends at scale. Plane is heavily inspired by Figma’s mulitplayer infrastructure, which dynamically spawns a process for each active document.

Use cases include:

  • Scaling up authoritative multiplayer backends.
  • Running isolated code environments (like REPLs, code notebooks, and LLM agent sandboxes).
  • Data-intensive applications that need a dedicated high-RAM process for each active user session.

How Plane works

You can think of Plane as a distributed hashmap, but instead of storing data, it stores running processes. When you ask Plane for the process associated with a key (via an HTTP API), it either returns a URL to an existing process, or starts a new process and returns a URL to that.

Plane will keep the process running for as long as there is an open connection (usually a WebSocket connection) to it. Once all connections to a process have been closed for some time threshold, Plane will shut down the process.

Plane guarantees that only one process will be running for each key at any given time, allowing that process to act as an authoritative source of document state for as long as it is running.

Architecture

Read more about Plane’s architecture.

Architecture diagram of Plane

Learn more

Explore related projects