# How Nevia Compute works

> Nevia’s default compute is a Firecracker microVM. Each microVM runs on a bare-metal host and is ready in milliseconds. Compute scales to zero when idle and scales up with demand.

> Nevia is in early access for selected teams. The CLI installs with `curl -fsSL https://get.nevia.cloud | sh`, and the MCP server is at https://api.nevia.cloud/mcp. A person signs in once in the browser.
> Setup, sign-in and requesting access: [SKILL.md](https://nevia.cloud/SKILL.md). When Nevia fits and when it doesn't: [why.md](https://nevia.cloud/why.md).

> For the complete documentation index, see [llms.txt](https://nevia.cloud/llms.txt). This page's HTML version: https://nevia.cloud/docs/infrastructure/compute

# How Nevia Compute works

Nevia’s default compute is a Firecracker microVM. Each microVM runs on a bare-metal host and is ready in milliseconds. Compute scales to zero when idle and scales up with demand.

Virtual machines for larger, long-running workloads are on the roadmap, with startup times measured in seconds.

| | microVMs | Virtual machines |
| :-- | :-- | :-- |
| What it is | A lightweight Firecracker virtual machine | A larger virtual machine with a fixed compute allocation |
| Best for | Apps with variable demand and workspaces that can sleep when idle | Always-on applications with steady demand |
| Startup time | Milliseconds | Seconds |
| Scale to zero | Yes | No |
| Scales with demand | Yes | No |
| Size | Up to 16 vCPUs | Up to 160 vCPUs |
| Status | Available | Roadmap |

## MicroVMs

Each workload runs in its own microVM with its own kernel, and workloads are isolated by hardware virtualisation rather than by shared-kernel containers. MicroVMs run directly on bare-metal hosts without an extra hypervisor layer. Your application runs inside the microVM and can be deployed from an OCI image.

::figure{id="compute-scaling"}

Compute is separate from storage. A machine's data lives on a replicated volume in the region, not on its compute host. This lets the machine sleep, wake and branch without moving data.

### Benefits

- **Starts in milliseconds:** Nevia allocates compute from pre-warmed pools, with startup times in the low hundreds of milliseconds.
- **Scales to zero:** Sleeping machines do not consume vCPU or RAM.
- **Isolated by default:** Each workload gets its own kernel and its own virtual hardware, with nothing to configure.

::figure{id="compute-timeline"}

### Purpose-built orchestration

Nevia's purpose-built orchestrator manages each microVM's lifecycle and enforces isolation between workloads. Every machine is isolated from its neighbours through hardware virtualisation, control traffic stays off the guest's network interface, and ingress and egress are governed by declarative rules.

## Virtual machines

Some workloads are not bursty, like always-on applications with steady demand or services you want sized once and left running. For these, we are building a virtual machine offering with a stable footprint. It runs on the same engine as microVMs, starts in seconds and supports the same branching capabilities.
