Key capabilities
Hardware isolation
Each workload runs in a Firecracker microVM with its own kernel, filesystem, and network namespace. FissionPlane treats every byte from the guest as hostile.
Pause and resume
Pause a sandbox to object storage and resume its memory, processes, and files exactly where they stopped — on any node.
SDK-driven control
Manage sandboxes and functions from TypeScript, Python, or Rust against shared, fully typed OpenAPI contracts.
Fully self-hosted
The control plane, data plane, and compute run on your infrastructure. No data leaves your network, and air-gapped installs work out of the box.
Kubernetes-native
One Helm chart installs into any existing cluster — EKS, GKE, AKS, k3s, bare metal, or air-gapped. No cluster-wide changes required.
Resilient data path
Running workloads continue through a control-plane outage. The control plane never proxies workload traffic.
What you can build
AI agents
Give each agent a full Linux workspace with its own kernel. Run tool calls, write files, and expose services — in complete isolation.
Code interpreters
Execute model-generated code safely. Return files, charts, logs, and exit codes to the caller without risk to your host.
Serverless APIs
Deploy functions behind HTTPS endpoints that start from warm snapshots and scale to zero between requests.
CI and build jobs
Run each job in a clean microVM. Destroy it when the job ends. No state leaks between runs.
Data analysis
Analyze untrusted datasets in isolation, co-located with your data. Nothing escapes the microVM boundary.
Scheduled jobs
Invoke functions on a cron schedule on your own hardware. No third-party scheduler service required.
Start here
Quickstart
Install the SDK, connect to your control plane, and run a command inside a Firecracker microVM in minutes.
Sandboxes
Learn how sandboxes are created, paused, resumed, and deleted, and how the lifecycle state machine works.
Functions
Understand how to deploy, invoke, version, and roll back serverless functions on FissionPlane.
Architecture
Explore the four planes — control, gateway, node runtime, and guest — and how they interact.
SDKs
TypeScript SDK
Use
@fissionplane/sdk in Node.js 20+ applications. Supports ESM, CommonJS, full types, and streaming.Python SDK
Use
fissionplane in Python 3.10+ applications. Both synchronous and asyncio-based clients included.Rust SDK
Use the
fissionplane crate in Tokio-based applications. Async-first with typed errors and tracing support.