Blog
Hello, public preview (v0.3.0)
deputyOS goes public. New: drive mounting, air-gapped tier with LFM2 baked, www/api/cdn on deputyos.com.
Update, August 2026. This post describes the sites as they stood at v0.3.0.
api.deputyos.comhas since grown from a read-only build-status dashboard into the full control plane — accounts, device registration, tunnel relay, managed backup and billing — and the account console now lives atconsole.deputyos.com. The rest of this post is left as written.
We’re flipping the lights on. deputyOS now has a public domain
(deputyos.com), a build-status dashboard (api.deputyos.com), a CDN
(cdn.deputyos.com), and three concrete things you can use today.
Drive mounting
The agent can now reach files you choose, safely. Three surfaces:
- VM host-FS passthrough — share a host folder into the WSL2 / UTM /
qemu image with
deputyctl mounts addor via the desktop launcher. - Removable drives on bare-metal — udev auto-mount under
/mnt/deputyos/<label>withnosuid,nodev,noexecfor unknown filesystems. LUKS volumes are refused until you unlock them. - SMB / NFS network shares — wizard tile collects credentials into
secrets.env; the policy file never sees them.
Every mount is reviewable + revocable in one click from deputyctl mounts list, the wizard’s /mounts page, and the PWA’s “Mounts” card.
Air-gapped fat tier
make build TARGET=qemu-x86_64 PROFILE=openclaw TIER=rich AIRGAP=1
produces an image that boots with -net none and serves a working chat
against a baked LFM2 model:
| Tier | Default LLM |
|---|---|
| lean | LFM2-350M.Q4_K_M.gguf |
| standard | LFM2-1.2B.Q4_K_M.gguf |
| rich | LFM2-2.6B.Q4_K_M.gguf + Qwen-Coder-1.5B |
deputyctl model set swaps among the baked GGUFs without network. apt
points at a local mirror; nftables denies egress except RFC1918 + mDNS.
Per the airgap concept doc, the posture is reversible
via deputyctl network unlock.
Public sites
www.deputyos.com— Astro 5, content-first, SEO + AI-search optimised. Picker readscdn.deputyos.com/<channel>/manifest.jsondirectly.api.deputyos.com— at v0.3.0, a Vue 3 + Tailwind build-status dashboard over a small Rust backend, read-only by design. It has since become the control plane: magic-link and device-code auth, device registration, the WebSocket tunnel relay, managed backup, and billing. Seeconsole.deputyos.comfor the account UI.
What’s next
- Egress whitelist mode (the middle ground between today’s open and airgap).
- Opt-in cloud accounts + managed backup/restore as a viable business model. Local-first invariant remains: every flow continues to work without an account.
The roadmap with all milestones lives at
docs/11-roadmap.md.
