Zudoku
Use Cases

Remote IDEs

Run full developer environments that scale to zero when idle and start back up exactly as you left them, in milliseconds.

Resumes in milliseconds, as you left it

Memory and disk are snapshotted when the developer stops typing, and restored on the next keystroke, processes still running.

resume in < 10 ms
A workspace that outlives the instance

The workspace state is held in persistent volumes, so scale-to-zero cycles and restarts don't lose work.

persistent volumes
Run as many as you need

One environment per developer, per branch or per review, with idle ones costing nothing.

100K+ microVMs / server
Dev image

Language toolchains, editor server, extensions

snapshot once
Template

Environment booted and warm, snapshotted once

< 10 ms each
+ volume each
workspace
vol: alice
workspace
vol: bob
workspace
vol: review-482
...idle workspaces scaled to zero, volumes kept
One image, one template, one workspace per developer, each with a volume that survives every scale-to-zero cycle.

Under the hood

The platform features this use case is built on.

Snapshot memory and volume state after the heavy initialisation stage so the environment starts in milliseconds.

Persist changes between scale-to-zero cycles, so the workspace outlives any single instance.

Restrict what the environment can reach and inject the secrets it needs.

Deploy your first remote IDE now

Sign up to Unikraft Cloud and follow the guide to deploy your first remote IDE

Last modified on