Advanced options

This page is the honest leftover for people who want the assistant on infrastructure they own, not on the laptop they shut at night. None of these remote hatch paths is a 0.1 product SKU. Do not run a command you found in an old vendor doc and expect Aevum to provision a VM.

The shipped path is Local hosting: signed AppImage or deb, native process, hatch on this machine.

What is not in 0.1

• cadence hatch --remote gcp as a supported Aevum flow.
• A managed AWS or GCP image we operate for you.
• A Mac Mini “home server” product. Apple is last, and we have no house Mac sit.
• Cadence Cloud as the “easy” alternative. See Cloud hosting.

What exists in the tree

Docker volumes and a containerized assistant are in the open-source tree for people who already run that stack. That is a power-user path, not the 0.1 download. The AppImage/deb sit is native. If you go Docker, you own IAM, networking, backups, and uptime.

The remote tradeoff (when it exists later)

• You gain: 24/7 availability, schedules that fire while the laptop sleeps, isolation from your daily session.
• You lose: direct host files and host_bash on the machine in your lap, unless you tunnel back while you are present.

Until that product exists, the practical 24/7 option is: leave a Linux box on, run the packed app there, and talk to it over the channels you connected. See Scheduling.

Comparison