introduction
Overview
Fystash is a multi-agent sandbox fabric: Firecracker microVMs, a shared POSIX drive, and fabric messaging. Not an LLM.
Fystash gives coding agents isolated compute they can coordinate. Each agent runs in its own Firecracker sandbox. Agents in the same room share a governed drive and a native message fabric.
Production topology is GCP nested KVM (topology=nested). Latency and create/resume claims are for this path — not bare metal.
What you get
- Rooms — run-scoped containers for sandboxes, fabric, and drive
- Sandboxes — isolated microVMs from templates (
default,browser,desktop,docker) - Fabric — directed messages, request/reply, fan-out, barriers
- Drive — shared POSIX artifacts that outlive sandbox destroy
- MCP + SDK + REST — drive everything from your agent or code
What Fystash is not
Not an agent framework. Not a model API. Not “the software factory.” You bring any agent SDK or model provider; Fystash supplies the room.
Prefer MCP
Most users configure `fystash-mcp` and let Cursor / Claude / Codex operate rooms. The webapp is a prompt hub — create and exec stay in MCP.
Next
- Quickstart — Sign up, get a key, run your first room.
- Connect your agent — Install MCP and paste credentials.
- Core model — Org → Room → Sandboxes + Fabric + Drive.
- API reference — REST against api.fystash.ai.