JailOps vs Bastille
Bastille is the best-known jail manager for FreeBSD: a command line tool written in shell, in the ports tree, with templates for repeatable setups. JailOps is a daemon with an API, projects and a console. Both manage jails on ZFS. They suit different people.
Side by side
| JailOps | Bastille | |
|---|---|---|
| Shape | A daemon with an HTTP API, a CLI and a web console | A command line tool with many sub-commands |
| Written in | Go, static binaries | Shell |
| License | BSD 2-Clause | BSD 3-Clause |
| Jail types | FreeBSD jails, Alpine and Debian jails | Thin, thick, clone and empty jails; Linux and OCI jails are marked experimental |
| Networking | Routed: the host hands out addresses and keeps jails apart, no bridge, no DHCP | VNET, bridge, passthrough, VLAN, NAT and loopback options |
| Reuse a setup | Fleets as files in git, an app catalog | Templates |
| Storage | ZFS, with volumes as objects shared between jails | ZFS, including a dataset given to a jail |
| Platform | FreeBSD 15.1 and later | FreeBSD |
Facts about Bastille come from its own site and repository. Check them there for the latest.
Where Bastille is stronger
- Maturity and reach. Bastille is in the ports tree and installs with
pkg, and it has been developed since 2018. JailOps is newer. - A shell script. It is written in shell with no extra dependencies, so you can read it in an afternoon.
- Many networking styles. Bridge, VLAN, passthrough and loopback are all there. If you need a shape that JailOps does not offer, Bastille probably has it.
- Templates. A well-known way to share a jail setup.
Where JailOps is stronger
- An API and a console. Everything in the CLI is in the HTTP API too, and there is a web console, so a team can work without a shell on the host.
- Projects. Jails, networks, quotas and firewall belong to a project, and another project is treated as an outside host. See projects are boundaries.
- The host owns the network. JailOps gives each jail an address and a routed link of its own, so jails are kept apart by the host. There is no bridge to set up and no DHCP server to run. The cost: no layer 2 between jails, so multicast, mDNS and VRRP do not pass from one jail to another.
- Firewall you can test. Policies are checked, and
jailops firewall testand a simulator show what a rule list does before traffic does it. See testing the firewall. - Volumes and backups. A volume is an object of its own that jails attach, and backups take each volume once.
Which to pick
Pick Bastille if you want a small, familiar tool, you like templates, you need a networking style that JailOps does not have, or you cannot run FreeBSD 15.1 or later, which JailOps needs.
Pick JailOps if you want an API and a console, several teams or customers on one host, one clear network model, and backups that include the data.
The two can live on different hosts. Nothing stops you from trying JailOps on one machine and keeping the rest as they are.
See it on your own host.
Look at the console on demo data, or install on a clean FreeBSD 15.1 machine.