Skip to main content
Amulet is built for file-oriented agent and batch workloads. It supports common Linux file operations, but it is not a fully POSIX-compliant filesystem.

​
Supported environments

  • Linux on x86_64 or aarch64
  • A host, VM, container, or sandbox with FUSE access
  • An empty or missing local mount directory
  • Network access to the Amulet control plane and storage service
The CLI installer does not support macOS or Windows because mounting requires the Linux FUSE client.

​
Filesystem behavior

  • Volumes and branches are writable unless mounted with --ro.
  • Snapshots are immutable and always mounted read-only.
  • The mount process runs in the foreground until unmounted.
  • Files remain durable after a clean unmount and can be mounted from another machine with access to the same organization.
  • The local mount path must be empty before mounting.

​
Workload fit

Amulet works well for corpora, agent workspaces, generated artifacts, checkpoints, logs, evaluation data, and batch inputs or outputs. Do not use Amulet as a database data directory or for software that requires complete file locking semantics. Avoid concurrent writes to the same file from multiple clients. Use a separate branch for each independent writer. When an environment is shutting down, run amulet unmount and wait for the mount process to exit before terminating the host.