Machineuse questions, answered

Machineuse is an open-source, distributed container manager for browser automation at scale, built by dotcommoners in Python. A control plane schedules isolated browser instances onto worker nodes by capability and live load; workers coordinate over a brokerless NNG mesh; each browser runs in a dedicated systemd-nspawn container; and idle instances are snapshotted to dormancy and revived on demand. It is MIT-licensed and self-hostable.

Yes. Machineuse is released under the MIT license and developed in the open by dotcommoners. You can read, run, modify, and self-host it freely. The source is on GitHub at github.com/dotcommoners/machineuse.

Machineuse is free and open source, with no SaaS offering and no per-session billing. You run it on your own infrastructure, so there is no vendor lock-in and no usage bill.

Each browser instance runs inside its own systemd-nspawn container with a dedicated filesystem and resource envelope. This keeps every session isolated from the others on the same node — cookies, storage, and untrusted pages stay contained.

systemd-nspawn is a lightweight, OS-level container manager built into systemd. Machineuse uses it to give each browser a clean, reproducible, isolated environment on a Linux host without the overhead of a full virtual machine.

Snapshot dormancy is how Machineuse reclaims resources from idle browsers. When an instance goes idle, its state is captured to a filesystem snapshot and its live CPU/memory are freed. When the session is needed again, the snapshot is revived on demand, restoring state without a cold rebuild. This lets a cluster hold far more logical sessions than it can keep simultaneously live.

Machineuse nodes communicate over NNG (nanomsg-next-generation) in a brokerless mesh — there is no external message broker such as RabbitMQ, Kafka, or Redis. Removing the central broker removes a common bottleneck and single point of failure, and shrinks the operational surface you have to run.

Machineuse manages real browser instances running in isolated containers, which you drive with your own automation tooling. It focuses on orchestrating the fleet — scheduling, isolation, and lifecycle — rather than replacing your automation library. See the documentation for the supported drivers and connection details.

Yes. Machineuse targets browser-automation-at-scale use cases including AI agents and computer-use workloads, and the project includes MCP-oriented tooling so agent frameworks can request, drive, and release isolated browsers programmatically.

Start on a single Linux host (with systemd-nspawn support) using Docker Compose. To scale out, run additional worker agents and point them at the control plane over NNG; the control plane schedules new work onto them automatically by capability and live load. See the docs for full installation and configuration.

A Linux host with systemd-nspawn support. A single node is enough to start; a production fleet is a control plane plus one or more worker nodes.

Managed browser clouds run automation on the provider’s platform for a per-session fee, with traffic egressing to them. Machineuse is self-hosted and MIT-licensed: it runs inside your own network with no lock-in, gives each browser a dedicated systemd-nspawn container, schedules by live load over a brokerless mesh, and uses snapshot dormancy to keep idle sessions cheap. The tradeoff is that you operate the cluster yourself. See the full comparison for details.