a real machine breathing on the enclave's own CPU — you just hold the console
This deployment requires an API key (the config's api_key).
This machine's CPU runs inside the enclave, the way a server-hosted emulator would — not in your browser.
The enclave pulls the kernel and root filesystem from an S3 bucket, boots them on a vendored pure-Rust
RISC-V system emulator, and streams the serial console here; your keystrokes go back into the guest. Save disk
writes the guest's changes back to the bucket. The guest has a virtio-net NIC on an in-app user-mode
network: the deployment's tcp:2222 port forwards to guest port 22, so an image with sshd accepts
ssh -p 2222 straight into the machine.
machine
idle
S3 credentials — needed unless the bucket allows public reads (held in enclave RAM only)
display
simple-framebuffer 800×600 — lights up when the guest kernel drives /dev/fb0 (fbcon, Xorg)