[](https://github.com/jamsocket/plane) [](https://hub.docker.com/r/plane/plane/tags) [](https://github.com/jamsocket/plane/actions/workflows/build-image.yml) [](https://github.com/jamsocket/plane/actions/workflows/tests.yml) [](https://discord.gg/N5sEpsuhh9) [Plane](https://plane.dev) is a distributed system for **running stateful WebSocket backends at scale**. Plane is heavily inspired by [Figma’s mulitplayer infrastructure](https://www.figma.com/blog/rust-in-production-at-figma/), which dynamically spawns a process for each active document. Use cases include: - Scaling up [authoritative multiplayer backends](https://jamsocket.com/blog/you-might-not-need-a-crdt). - 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. Read more about [Plane’s architecture](https://plane.dev/concepts/architecture). [](https://plane.dev/concepts/architecture) ## Learn more - Read the [quickstart guide](https://plane.dev/quickstart-guide) - Learn about [Plane concepts](https://plane.dev/concepts/session-backends) - See instructions for [building and developing Plane locally](https://plane.dev/developing) - Read about [production deployment](https://plane.dev/deploy-to-prod)