Skip to content
Install

Why Volant

What Volant is, where the speed comes from, and what it promises.

Volant is for people who run Ansible playbooks against Linux hosts and want those runs to finish faster. It reads the playbooks, roles and inventories you already have, in Ansible’s own formats, and runs them over SSH. You do not convert anything, and the same files keep working with ansible-playbook.

The name is French: a volant is a steering wheel. You steer your infrastructure with it.

Terminal window
curl -fsSL https://volant.sh/install.sh | sh
volant playbook -i inventory.ini site.yml

Installation and the quickstart take it from here. You do not need Ansible installed.

For every task on every host, ansible-playbook builds a module payload, sends it over SSH, and starts a fresh Python interpreter on the host to run it. Pipelining removes the temporary file, but each task still pays for a new interpreter and a new round of imports.

Volant pays those costs once per run:

  • A small program called the agent is uploaded to each host the first time and cached there. Later runs reuse it.
  • The controller keeps one SSH connection per host open for the whole run and streams tasks over it.
  • Python modules travel to the host once, in a single archive. A Python server on the host loads the shared code once and forks a child for each task.
  • The agent answers common modules, such as apt, systemd, file and fact gathering, in Rust when a task’s arguments allow it, and hands every other case to the Python module.

ansible-playbookfor every task, on every host

  1. build the payload
  2. open ssh
  3. start Python
  4. import module_utils
  5. run the module

Volantfor every task, once the run has started

  1. send over the open connection
  2. fork the ready Python server
  3. run the module

These numbers come from two real workloads against two Ubuntu 24.04 hosts. The first applies four published Galaxy roles, geerlingguy.security, nginx, git and pip, to hosts they have already converged. The second is the official k3s-ansible playbook against an installed cluster. Each figure is the median of three passes, measured on 2026-09-27 with just bench and just bench-k3s, and both engines ended every pass on the same recap. The comparison runs ansible-core 2.19.12 with pipelining = True.

Two workloads, two converged hostsMedian of three passes, 2026-09-27. Shorter is faster.
  • ansible-core 2.19.12, pipelining
  • Volant
  • Four Galaxy roles26.435 s0.529 sFour Galaxy rolesansible-core 2.19.12, pipelining: 26.435 sVolant: 0.529 s
  • k3s-ansible50.519 s23.477 sk3s-ansibleansible-core 2.19.12, pipelining: 50.519 sVolant: 23.477 s
Show as a table
ansible-core 2.19.12, pipeliningVolant
Four Galaxy roles26.435 s0.529 s
k3s-ansible50.519 s23.477 s

A task that does real work still takes as long as that work. Most of Volant’s time on k3s goes to restarting the k3s service, running its install script and the other commands the playbook asks for, which cost the same under either engine.

Your files stay yours. Volant reads Ansible’s YAML and follows its variable precedence and its templating, so there is no new format to learn.

It stops instead of guessing. Most of what this release does not support yet is named before the first connection, so a run rarely reports success after quietly skipping something you asked for. The known gaps are the exceptions. The check is called the pre-flight check.

It targets Linux over SSH first. The controller runs on Linux or macOS and drives Linux hosts. Network devices run through ansible.netcommon’s connections. Windows comes later.

On the controller, the machine you run volant from:

  • The install script puts each release under ~/.local/share/volant and links volant and volant-playbook into ~/.local/bin.
  • The managed runtime is a private Python 3 with ansible-core, which Volant downloads the first time a run needs Python and finds no usable one. It lives in ~/.local/share/volant/runtime (~/Library/Application Support/volant/runtime on macOS) and takes about 155 MB. The managed runtime says how to skip it or remove it.
  • Caches go under ~/.cache/volant: the agents it uploads, and the bundles of Python modules it builds.

On each managed host:

  • The cached agent, one small executable of about 1.2 MB, in ~/.ansible/tmp/volant-agent-<version>-<uid>/. A task that uses become caches a second copy in the home directory of the account it escalates to.
  • A directory next to it, volant-blobs-<version>-<uid>, holds the Python modules sent to the host. It exists once a run has used a Python module.
  • ~/.ansible_async holds the status files of async tasks, when you use async.

To remove the cache on a host, delete the volant-* directories in ~/.ansible/tmp (see Go back to ansible-playbook).

Volant never sends telemetry. Apart from the calls your playbook asks for, its only network use is the one-time download of the managed runtime, when a run needs it.

Volant reproduces ansible-core 2.19. A difference from ansible-core is a bug, unless a page lists it as a deliberate choice under Differences from Ansible.

Some features are not there yet: the known gaps list them. The roadmap says what comes next.