Hardware
Where to run deputyOS.
Same image, same wizard, same assistant. Start on the machine in front of you and move it to dedicated hardware when you're ready — the profile transfers unchanged.
Single-board computers
Cheap, quiet, low power. The classic always-on option.
-
deputyOS on Raspberry Pi 4
Run deputyOS on a Raspberry Pi 4. Works on the lean tier with cloud model providers; local inference is out of reach.
~20 min · easy · ~$45 one-off
-
deputyOS on Raspberry Pi 5
Run a personal AI assistant on a Raspberry Pi 5. Flash, boot, and finish the wizard in about 15 minutes — no SSH, no terminal.
~15 min · easy · ~$80 one-off
Mini-PCs
The best price-to-capability ratio, and the only dedicated option that runs local models well.
Cloud
No hardware to buy. A few pounds a month, running somewhere else.
-
deputyOS on Hetzner Cloud
Run deputyOS on a Hetzner VPS for a few euros a month. Paste a cloud-init recipe and it builds itself — no image upload needed.
~10 min · easy · ~€4/mo
-
deputyOS on DigitalOcean
Run deputyOS on a DigitalOcean droplet from a snapshot built by Packer, or from a cloud-init recipe.
~10 min · easy · ~$6/mo
Your existing machine
Try it on the laptop you already have. Not always-on, but nothing to buy.
-
deputyOS on macOS
Run deputyOS on a Mac through UTM or OrbStack. Apple Silicon gets hardware acceleration; Intel Macs fall back to slower emulation.
~10 min · easy · free
-
deputyOS on Windows with WSL2
Run deputyOS on Windows through WSL2. Import a tarball and it runs as a distribution — no VM manager, no dual boot.
~10 min · easy · free
Hypervisors
Run it as a guest on infrastructure you already operate.
The full matrix — every target, format, build kind and CI status — is in the hardware matrix . To download a signed image, use the picker.