> ## Documentation Index
> Fetch the complete documentation index at: https://fissionplane.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# FissionPlane: Secure Sandboxes on Your Own Infrastructure

> Run AI agent sandboxes and serverless functions in isolated Firecracker microVMs on Kubernetes clusters you control. No cloud lock-in.

FissionPlane is a self-hosted compute platform for running untrusted code securely. Deploy it on your Kubernetes cluster with a single Helm chart, then create isolated Linux sandboxes for AI agents, code interpreters, CI jobs, and serverless functions — all running in Firecracker microVMs on hardware you operate.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/docs/quickstart">
    Create your first sandbox and run a command in minutes.
  </Card>

  <Card title="Installation" icon="server" href="/docs/installation">
    Deploy FissionPlane on your Kubernetes cluster with Helm.
  </Card>

  <Card title="TypeScript SDK" icon="js" href="/docs/sdks/typescript">
    Manage sandboxes from Node.js applications.
  </Card>

  <Card title="API Reference" icon="code" href="/docs/api/overview">
    Explore the full control plane and data plane APIs.
  </Card>
</CardGroup>

## What FissionPlane does

FissionPlane gives every workload its own Firecracker microVM with a dedicated kernel, filesystem, and network namespace. You control exactly how long it runs, what ports it exposes, and whether its state is preserved.

<CardGroup cols={2}>
  <Card title="Sandboxes" icon="box" href="/docs/concepts/sandboxes">
    Stateful, interactive Linux environments you create, pause, and delete on demand.
  </Card>

  <Card title="Templates" icon="layer-group" href="/docs/concepts/templates">
    Immutable pre-booted artifacts built from any OCI image. The starting point for every sandbox.
  </Card>

  <Card title="Functions" icon="bolt" href="/docs/concepts/functions">
    Deploy versioned functions that start from warm snapshots and scale to zero between invocations.
  </Card>

  <Card title="Security model" icon="shield-halved" href="/docs/concepts/security">
    Hardware isolation, capability tokens, and a data path that stays alive through control-plane outages.
  </Card>
</CardGroup>

## Get up and running

<Steps>
  <Step title="Deploy FissionPlane on Kubernetes">
    Install the Helm chart on any Kubernetes cluster — EKS, GKE, AKS, k3s, or bare metal.
    See [Installation](/docs/installation) for cluster requirements and Helm values.
  </Step>

  <Step title="Install an SDK">
    Pick TypeScript, Python, or Rust. All three SDKs share the same OpenAPI contract.

    ```bash theme={null}
    npm install @fissionplane/sdk
    ```
  </Step>

  <Step title="Configure your client">
    Point the SDK at your control plane and supply an API key.

    ```bash theme={null}
    export FISSIONPLANE_API_URL="https://api.sandbox.example.com"
    export FISSIONPLANE_API_KEY="your-api-key"
    ```
  </Step>

  <Step title="Create your first sandbox">
    Spin up an isolated microVM and run a command inside it.

    ```typescript theme={null}
    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 FissionPlane'] })
    console.log(result.stdout)
    await sandbox.delete()
    ```
  </Step>
</Steps>

## Why self-hosted?

Hosted sandbox platforms run your code on their infrastructure. FissionPlane gives you the same fast microVM sandboxes, snapshots, and SDKs — but every byte stays on hardware you operate. There is no metered billing, no data leaves your network, and air-gapped installs work.