# jamsocket/plane

A distributed system for running WebSocket services at scale.

Repository: https://github.com/jamsocket/plane
Canonical: https://ross.abutalabs.com/products/jamsocket-plane
Homepage: https://plane.dev
Language: Rust
License: NOASSERTION
License Family: other
Topics: rust, websocket
Last push: 2026-01-13T16:11:14+00:00

## Health v2 (maintenance only)
Score: 58/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 62, release rhythm 28, longevity 100
- inputs: {"age_days": 1757, "days_push": 232, "days_rel": 569, "gap_med": 54, "n_releases_24m": 2}
- flags: no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2023, forks 51 (observed 2026-08-28T04:06:06.599669+00:00)

## What it is
Plane is a distributed system for running stateful WebSocket backends at scale, acting like a distributed hashmap of running processes keyed by session. It dynamically spawns, routes to, and reaps per-session processes, inspired by Figma's multiplayer infrastructure.

## Use cases
- scale authoritative multiplayer backends per document
- run isolated code environments like REPLs and LLM agent sandboxes
- spawn a dedicated high-RAM process per active user session
- route WebSocket connections to per-key backend processes
- automatically shut down idle session backends
- ensure a single authoritative process per document key

## When to choose
- you need per-session or per-document stateful WebSocket backends that scale dynamically
- you want isolated ephemeral compute environments (sandboxes, REPLs, agent runtimes)
- you need a single authoritative process per key with automatic lifecycle management
- you want a Figma-style session backend architecture without building it yourself

## When to avoid
- you only need stateless HTTP request handling or simple load balancing
- your workload is batch or background processing with no live connections
- you need long-running services that persist without active connections
- you want a fully managed cloud service rather than self-hosted infrastructure

## Facets
- artifact type: service
- maturity: active
- function: websocket, deployment, container-orchestration, http-server, api-framework
- domain: backend, web-development, microservices, developer-tools
- platform: rust, cloud, self-hosted
- tags: session-backends, websocket-orchestration, multiplayer, sandboxing, process-scheduling, ephemeral-compute, real-time, docker, linux

## Member repositories
- jamsocket/plane (main) score 58

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:06.599669+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:00:03.184231+00:00, confidence not recorded.
  - readme: https://github.com/jamsocket/plane (fetched 2026-08-28T04:06:06.599669+00:00, sha 50fe6228887c)
  - registry_crates: https://crates.io/api/v1/crates/plane (fetched 2026-08-29T10:39:59.654188+00:00, sha e4298b9b6abe)
- Data as of 2026-08-30T08:39:29.467469+00:00.