Nectar runtime

The execution engine.

Compiles, snapshots, and runs your WASM workloads with hardware-level isolation. Wasmtime 40 under the hood.

Nectar runtime

Initialize once. Restore a known state.

Initialized memory becomes a snapshot. A fresh execution instance restores that state, ready for the next request.

Snapshot lifecycle example

Globals

Tables

Linear memory

Startup stateInitialize globals and memory

Ready to capture the initialized state

Runtime state

component: image-worker.wasm
phase: initialize
startup: executing
memory: initializing
request: waiting

What the snapshot contains

Linear memoryInitialized pages

Component stateGlobals & tables

Conceptual lifecycle. No timing or performance measurement is implied.

How it works

Three stages. Zero cold starts.

{ }

Compile

Your source code compiles to a WASM component via WASI 0.2. Rust, Go, Python, JS, C -- any language that targets WASM. Nectar validates the binary and extracts typed interfaces.

Snapshot

Nectar pre-initializes the module, runs startup code, then freezes the entire linear memory into a snapshot. Subsequent boots restore from this frozen image in under 800 microseconds.

Execute

Requests arrive, the snapshot restores, your handler runs in a sandboxed linear memory space with instruction-level fuel metering. Scale to zero when idle. No wasted cycles.

Performance

Numbers that matter.

<0.8msCold start from snapshot

342KBAverage module size

2MBMemory floor

0.2sCPU metering precision

Deploy to Nectar.

Sub-millisecond cold starts. Scale to zero. Pay nothing when idle.

Start free →Platform overview

Nectar runtime

The execution engine.

Compiles, snapshots, and runs your WASM workloads with hardware-level isolation. Wasmtime 40 under the hood.

Nectar runtime

Initialize once. Restore a known state.

Initialized memory becomes a snapshot. A fresh execution instance restores that state, ready for the next request.

Snapshot lifecycle example

Globals

Tables

Linear memory

Startup stateInitialize globals and memory

Ready to capture the initialized state

Runtime state

component: image-worker.wasm
phase: initialize
startup: executing
memory: initializing
request: waiting

What the snapshot contains

Linear memoryInitialized pages

Component stateGlobals & tables

Conceptual lifecycle. No timing or performance measurement is implied.

How it works

Three stages. Zero cold starts.

{ }

Compile

Your source code compiles to a WASM component via WASI 0.2. Rust, Go, Python, JS, C -- any language that targets WASM. Nectar validates the binary and extracts typed interfaces.

Snapshot

Nectar pre-initializes the module, runs startup code, then freezes the entire linear memory into a snapshot. Subsequent boots restore from this frozen image in under 800 microseconds.

Execute

Requests arrive, the snapshot restores, your handler runs in a sandboxed linear memory space with instruction-level fuel metering. Scale to zero when idle. No wasted cycles.

Performance

Numbers that matter.

<0.8msCold start from snapshot

342KBAverage module size

2MBMemory floor

0.2sCPU metering precision

Deploy to Nectar.

Sub-millisecond cold starts. Scale to zero. Pay nothing when idle.

Start free →Platform overview