Skip to content
Monoid // Machine
Monoid Machine // One image · desk or cloud

A computer for your agents. On your desk, or in your own cloud.

Run coding agents, their workspace and a Kubernetes cluster for what they ship—each isolated in its own VM on an seL4-based hypervisor. Accounts and TLS keys stay on your machine, reachable at your own domain.

  • HypervisorL4H / FL4 (seL4)
  • AttestationTPM 2.0 + PCR
  • IngressSNI passthrough
  • ReleasesSigstore + A/B
Fig. 01 · Monoid Machine M–1 Rev A
FRONT SIDE 4.3″ LCD 800×480 USB-C YUBIKEY POWER 120 260 MM 240 MONOID // M-1 AGENTS 3 /4 WORKING CPU MEM DISK monoid M–1
Front / side 120 × 240 × 260 mm
[01] Products

One image, two ways to run it.

[A] Hardware First batch · 10–20 units

Monoid Machine M–1

An anodized aluminum desk computer built to run agents all day, with a 4.3″ status screen and an internal Android board over USB.

Compute
AMD Ryzen 7 7745HX · 8 cores, 16 threads
Memory & disk
32 GB DDR5 (1 slot free) · 2 TB NVMe
Android
ROCK 5C (RK3588S2, 8 GB) inside
Interface
4.3″ touch LCD · 2.5 GbE · front USB-C
Trust
AMD fTPM · LUKS2 unlocked by YubiKey
[B] Your Google Cloud Public image · GCE

Monoid Machine Cloud

The same signed Monoid image on Compute Engine in your own GCP project—your billing, your region and your VPC.

Start an instance
gcloud compute instances create monoid-1 \
  --machine-type=n2-standard-8 \
  --image-project=cue-infra \
  --image-family=monoid-stable \
  --boot-disk-size=200GB \
  --shielded-vtpm
ttyS0 · monoid-ctl: waiting to be claimed enroll: K7QM-3XRA at console.monoid.computer/claim
Instances
Compute Engine N2, C3 and later (x86_64)
Image
Public · cue-infra / monoid-stable, monoid-beta
Sandboxes
/dev/kvm with nested virtualization
Network
gVNIC or virtio-net · no external IP needed
Trust
Shielded VM vTPM · getShieldedInstanceIdentity
[02] Compare

The same software image, in two places.

Both boot the same signed release and pair to the same console; only the underlying hardware boundary differs.

Aspect Monoid Machine M–1 Monoid Machine Cloud
Where it runsM–1On your desk or in your officeCloudIn your own GCP project, any region
ProvisioningM–1Plug into power and EthernetCloudgcloud compute instances create or Terraform
First-boot claimM–18-character code on the 4.3″ screenCloud8-character code on the serial port, or monoid-seed
Root of trustM–1AMD fTPM (EK certificate from AMD)CloudShielded VM vTPM (EK from the Compute API)
Data at restM–1LUKS2, unlocked by your YubiKey at the front USB-CCloudGoogle's persistent-disk encryption
Physical AndroidM–1ROCK 5C board inside, power-cycled and flashed over USBCloudNo internal Android board
Agent sandboxesM–1/dev/kvm via hardware AMD-VCloud/dev/kvm with GCE nested virtualization
Shared on both
  • Signed L4H / FL4 image
  • Workspace & k3s on the machine
  • Your domain via SNI passthrough
  • A/B updates with rollback
[03] Inside

Every part in its own VM.

L4H isolates every role in its own virtual machine. Even dom0 cannot read guest memory, so a compromised agent or public app cannot reach workspace accounts, TLS keys or hardware controls.

[01] ClientTLS 1.3
station.your-org.dev

Browser, CLI or webhook

[02] SNI relayPassthrough
pops.monoid.computer

Routes TCP 443 by SNI over iroh; holds no keys

[03] edge VMVerified
Outbound tunnel · NAT

Relayed only while TPM attestation passes

[04] Guest VMsOn-machine TLS
cloud · station · apps

ACME certificates issue and terminate here

Fig. 02 · Guest VMs & host TCB 6 VMs
  • stationAgents

    Runs coding agents, Git, toolchains, rootless containers and Chromium. Administers apps; reaches cloud only through its public API.

  • cloudWorkspace

    Your machine's own control plane, accounts and workspace data—stored on its own volume, never on Monoid's servers.

  • appsKubernetes

    Single-node k3s with Traefik ingress and a local container registry for services your agents build and expose.

  • edgeNetwork

    DHCP, DNS, nftables firewall, SNI router and the iroh gateway link. Keeps internet-facing code out of every other VM.

  • dom0Supervisor

    Starts VMs from dm-verity images, balances memory between station and apps, and applies updates—without access to guest memory.

  • hwM–1 only

    Drives the 4.3″ screen, switches and flashes the Android board, and reads YubiKey unlock responses; exposes only ADB over USB/IP.

Host TCB
  • L4H hypervisor
  • FL4 kernel (seL4 in Rust, Lean 4 proofs)
  • IOMMU driver isolation
  • dm-verity + kernel lockdown
  • TPM 2.0
One role per VM · no shared memory L4H
[04] Security

Don't take our word for what it runs.

01 · Attested

Verified before it's reachable

The console proves the TPM is real with TPM2_ActivateCredential, against AMD's certificate or Google's Compute API, then checks the host's PCRs and each VM's signed launch measurement. Until they pass, the gateway does not relay it.

PCR 4·8·9 + COSE_Sign1
02 · Zero-plaintext

TLS keys stay on the machine

The machine gets its own certificates with TLS-ALPN-01. Monoid's gateway only passes the encrypted stream through by SNI: it holds no private keys and never sees plaintext. Bring your own domain if you like.

TLS-ALPN-01 · SNI passthrough
03 · Transparent

Signed releases & dm-verity

Every release is signed with Sigstore's keyless signing and recorded in public transparency logs. Each VM's system volume is checked block by block with dm-verity under kernel lockdown, and A/B slots roll a failed update back.

Sigstore · dm-verity · A/B slots
04 · Proven

Isolated on seL4

L4H runs on FL4, the seL4 kernel written in Rust with Lean 4 proofs. Device drivers sit behind the IOMMU, and dom0 cannot read guest memory or registers.

FL4 · seL4 in Rust · Lean 4
[05] Get started

Nothing to configure on the machine.

  1. Step 01 / Boot

    Plug it in, or start the instance.

    An M–1 needs power and Ethernet; Monoid Machine Cloud needs one gcloud command.

  2. Step 02 / Claim

    Enter its code at console.monoid.computer/claim.

    The 8-character code shows on the M–1's screen or the instance's serial port; fleets pass a monoid-seed token instead.

  3. Step 03 / Ship

    Open your station and put agents to work.

    What they build runs on the machine's own k3s, at your own domain.