Hosting Hermes

Run Hermes inside a Sandbox0 sandbox when you want sessions, memory, skills, and gateway state behind Sandbox0 lifecycle and network controls. The builtin hermes template keeps its writable state on the sandbox rootfs.

Create The Sandbox#

Claim the builtin template:

bash
SANDBOX_ID="$(
    s0 -o json sandbox create --template hermes \
        | jq -r '.ID // .id'
)"

s0 sandbox get "$SANDBOX_ID"

Use the Sandbox Services API or an SDK claim configuration to expose the Hermes API as a cmd service. Enable auto_resume on the sandbox and resume: true on its route when incoming traffic should wake a paused runtime.

Persistence#

Hermes workspace and configuration files live on the writable rootfs. A pause checkpoints them to encrypted object storage and resume restores them before Hermes is started again. Deleting the sandbox deletes that rootfs identity.

Create a named rootfs snapshot before deletion when you need to preserve or fan out an initialized Hermes workspace. A new sandbox can be claimed with the snapshot ID, or the current sandbox can be restored after it is paused.

Running processes, memory, and sockets are intentionally not preserved across pause/resume.

Next Steps#