Zudoku
Use Cases

Serverless Functions

Deploy hardware-isolated serverless functions that boot and respond in milliseconds, and cost nothing between calls.

Real VM isolation, not containers or isolates

Most serverless platforms share a kernel or a language runtime between tenants. Every function here is a hardware-isolated microVM with its own kernel, safe enough to run code you didn't write.

own kernel per function
Start bulky runtimes in milliseconds

Bring your own runtime, however heavy. Snapshot it warm into a template: no warm pool to keep paying for.

cold start < 10 ms
Fast to start and still customizable

Templates alone would give you identical runtimes. The function's own code arrives as a ROM mounted at boot, so one warm template serves many different functions, and shipping a new one is a few KB, not an image build.

templates + ROMs, no rebuild
Runtime image

Node, Python, Go, JVM (your Dockerfile)

snapshot once
Template

Runtime booted and warm, frozen mid-flight

< 10 ms each
+ ROM per function
instance
resize-image
instance
send-email
instance
webhook-fanout
...idle functions sit at zero cost
One template for the runtime, one ROM per unit of code, so shipping a function doesn't rebuild the image.

Watch the recording to see one language runtime snapshotted once, then different handlers dropped in as ROMs, each waking to serve a request in 6 ms.


Under the hood

The platform features this use case is built on.

Snapshot bulky runtimes so they start in milliseconds, and mount the function code as a ROM so changing it doesn't require rebuilding the image.

Let the platform absorb traffic spikes across instances without a separate load balancer.

Deploy your first serverless function now

Sign up to Unikraft Cloud and follow the guide to deploy your first serverless function now

Last modified on