automating web application deployments

Release v1.13.0.

batou is a BSD licensed utility, written in Python, to configure development and production environments for web applications.

Deployments are hard and complicated. Tools like Docker, Puppet, chef, and others exist that try to solve this problem once and for all. However, they usually need you to change your workflow or toolchain massively while still missing important steps.

batou makes deployments more bearable without requiring developers to change their applications. It provides a “one command” approach that should never need additional wrapper scripts.

As a developer all you ever have to run after cloning or updating your project is:

$ hg clone
$ cd myproject
$ ./batou deploy dev

To run a production deployment all you should ever have to run is:

$ cd my-project
$ git pull
$ ./batou deploy prod

Writing a deployment with batou is a two step process:

Step 1: Model your application’s configuration

With our component model you write a configuration specification in Python based on a simple API. Components make configuration convergent and idempotent and using Python lets you perform any computation you need. The component model is recursive, so you can refactor complicated components into simpler ones without breaking your setup.

Here is an example application model that installs a Python package into a VirtualEnv and asks Supervisor to run it:

from batou.component import Component
from batou.lib.python import VirtualEnv, Package
from batou.lib.supervisor import Program

class MyApp(Component):

  def configure(self):
    venv = VirtualEnv('2.7')
    self += venv
    venv += Package('myapp')
    self += Program('myapp', command='bin/myapp')

Step 2: Fit your model to your environments

Your model from step 1 is abstract: it does not mention the names of the servers you deploy to.

By describing an environment you tell batou how your abstract model should actually be applied: on your local development machine, to a vagrant setup, or on servers on the network.

Here’s an environment specification that sets up an application on multiple hosts and provides an override for the publicly visible address.

host_domain =

components = nginx, haproxy, varnish

components = myapp

components = myapp

components = postgresql

server_name =


  • Run the same command to deploy locally, to Vagrant, or to remote clusters.
  • Use different versions of batou in different projects. Ensure everybody uses the same version.
  • Check before deploying whether your configuration is internally consistent and consistent with what has been deployed before.
  • Convergent, idempotent components are fast to deploy.
  • Resume partial deployments where they were aborted.
  • Store database passwords, SSH keys, SSL certificates or other secret data with on the-fly decryption. Manage access to secrets per environment and user.
  • Use Jinja2 templates to easily create dynamic configuration.
  • Dynamically connect services during deployments and track their dependencies.
  • Few run-time requirements on your servers: only Python 2.7 and SSH are needed.
  • Use pre-defined components to manage files, python environments, supervisor, cronjobs, and more.
  • Writing your own components is easy and you can use additional Python package dependencies.

User guide

This part of the documentation, begins with some background information about Requests, then focuses on step-by-step instructions for getting the most out of batou.

Command line

If you are looking for information on what commands the batou CLI provides then this is for you.

Contributor guide

If you want to contribute to the project, this part of the documentation is for you.


batou itself is released “as is”. We hang around #batou in the Freenode IRC network. You can also report bugs to our bugtracker.

Commercial support

We will be happy to give you commercial support for batou: feature implementation, bug fixing, consulting, or education.

To get in touch, send an email to and we’ll be happy to discuss your requirements.