FissionPlane is open-source infrastructure for secure code execution

Install a FissionPlane SDK

npm install @fissionplane/sdk

pip install fissionplane

cargo add fissionplane

Three SDKs share one set of OpenAPI contracts.Read the FissionPlane documentation to connect an SDK to your installation.

// Create a sandbox and run a command.
import { FissionPlane } from '@fissionplane/sdk'

const client = new FissionPlane()
const sandbox = await client.sandboxes.create({ template: 'base' })

const result = await sandbox.commands.run('echo', {
  args: ['hello from a microVM'],
})

console.log(result.stdout)
await sandbox.delete()

• Hardware isolation. Each sandbox runs in a Firecracker microVM with its own kernel, filesystem, network namespace, and resource limits.
• Stateful sandboxes. Pause a sandbox to object storage. Resume its memory, processes, filesystem, and device state where they stopped.
• SDK-driven control. Create and manage sandboxes from TypeScript, Python, or Rust against shared OpenAPI contracts.
• Fully self-hosted. The control plane, data plane, and sandbox compute run on infrastructure that you operate—no proprietary FissionPlane service required.
• Kubernetes-native. One Helm chart installs into an existing cluster. No operator. No custom resources.
• Resilient data path. Sandboxes keep running through a control-plane outage. The control plane never proxies sandbox traffic.

• What is FissionPlane?

  FissionPlane is open-source, self-hosted infrastructure for secure code execution. It gives AI agents, code interpreters, developer tools, and CI systems isolated Firecracker microVM sandboxes—each a complete Linux environment with command, filesystem, network, and lifecycle controls.

• Is FissionPlane open source?

  Yes. FissionPlane is free and open-source software under the Apache License 2.0. The control plane, gateway, node runtime, guest programs, API contracts, and SDKs are all in one repository. You may use it in personal and commercial projects, subject to the license terms.

• How does FissionPlane isolate untrusted code?

  Each sandbox runs in a Firecracker microVM with its own kernel, filesystem, network namespace, and resource limits. Sandboxes share nothing with the host or with each other. FissionPlane treats every byte from the guest as hostile.

• Does FissionPlane require Kubernetes?

  Yes for the control plane install path documented today: one Helm chart deploys into an existing Kubernetes cluster. It needs no operator, no custom resources, and no cluster-wide changes.

• Which SDKs does FissionPlane provide?

  TypeScript, Python, and Rust. Lifecycle and data-plane APIs use OpenAPI contracts, so clients can follow the same contracts in other languages.

• What can you do inside a FissionPlane sandbox?

  Create a sandbox from an immutable template; run commands and stream stdin, stdout, and stderr; open PTY sessions and send signals; read, write, upload, download, and watch files; expose a guest port through a private or public HTTPS URL; build templates from OCI images; and pause, resume, extend, or delete the sandbox through an SDK or REST API.

• Can FissionPlane sandboxes be paused and resumed?

  Yes. You can pause a sandbox to object storage and resume its memory, processes, filesystem, and device state where they stopped.

• Who operates the FissionPlane infrastructure?

  You do. FissionPlane requires no proprietary FissionPlane cloud service. The control plane, data plane, and sandbox compute stay in infrastructure that you operate. Running sandboxes continue through a control-plane outage because the control plane does not proxy sandbox traffic.