arcave saves the whole live state of a running Compose project — every volume, every container filesystem, and the compose spec itself — and puts it back in one command. Get your environment to the state you want, save it, and come back to it in seconds.
It works on any Compose project, on the Docker you already have.
Alpha. arcave is at
v0.1.0-alpha.5. Commands, output and the storage format may change between alphas, with no migration path for savepoints taken by an earlier one. It is not ready for production use yet.
- Whole-project savepoints: One savepoint holds every stateful volume, every container's writable layer, and the compose spec the project was running under.
- Consistent by construction: The services are stopped before a byte is read, so nothing is captured mid-write and a database comes back without a crash-recovery pass on start.
- Reversible rollback: A rollback takes a safety snapshot of what it is about to overwrite and replays it automatically if anything fails. A failed rollback leaves you where you started.
- Sessions and branching: Independent lines of savepoints inside one project. A fork copies a whole session into a new one, and the two lines never mix.
- Incremental capture: The
cdcbackend writes only the chunks that changed since the last savepoint. Container filesystems and images are deduplicated by default, whichever volume backend you pick — the base layer every savepoint shares is stored once. - Encrypted storage: Turn on
encryption.enabledand everything arcave stores is encrypted to your age key before it leaves the host, so whoever reads the bucket sees names and sizes, not your data. - Built for agents:
arcave mcpserves savepoint create, list, remove and rollback, the session commands,status,gcand compose-file generation as MCP tools, so an agent checkpoints before it acts, rolls back when validation fails, and can fork a session of its own. - Space back on demand:
arcave gcdeletes what no remaining savepoint uses — stored data,cdcsnapshots, the image tags rollbacks left in Docker — and all but the newest safety snapshot of each compose project.--dry-runshows it first. - What is running:
arcave statusshows which savepoint a rollback deployed, from which session and when, every replica's health and ports, and the containers recreated outside arcave since. - See what it is doing: A live tree of every step on a terminal, a log line per step in CI, a JSON stream for a program. Results are text for you and JSON for a pipe.
- A compose file from a running project:
arcave tools generate-composewrites the compose file Docker's view of the project implies — for a project whose file was lost, or never written. - Plain Docker: No ZFS, no copy-on-write filesystem, no storage appliance, no Docker daemon to reconfigure — the daemon you already run, and the arcave binary.
- Any compose project: Postgres, MySQL, Kafka, Redis, MinIO, your own services. No allowlist — arcave reads what your Docker daemon is running.
- Testing destructive migrations: Run the migration against real data, again and again, until it is right. The reset is one command.
- Agent iteration loops: Give an autonomous agent a checkpoint per attempt, and a failed iteration costs a rollback instead of a rebuild.
- Environment branching: A session per feature branch, forked off a shared baseline and switched by name.
- Resetting fixtures and demos: Seed the environment once, save it, and return to that exact state for the rest of the project's life — object storage and cache included.
# 1. Install the binary
curl -fsSL https://greenmask.io/arcave/install.sh | bash
# 2. Bring your compose project up and initialise arcave in it
docker compose up -d
arcave init
export ARCAVE_COMPOSE_PROJECT_NAME=myapp # as `docker compose ls` names it
# 3. Save the state you want to come back to
arcave savepoint create before-migration
# 4. ...run the migration, the experiment, the agent...
# 5. Go back to it
arcave rollback before-migrationFor more details, visit the Documentation — start with Getting started, and read the Limitations before you build a workflow on arcave.
- Docker 25 or newer, or Podman, with the daemon reachable by the user running arcave.
- Linux or macOS. There is no Windows build.
The full list is in Requirements.
