Network Rendering
Indigo supports distributed rendering over a TCP/IP network. One Indigo process is started as a network master. Mutiple Indigo processes (usually on other boxes) are then started as network slaves. The network slaves work on their own local version of the render, and periodically upload their buffer to the network master, where they are combined into the master render and saved to disk in the 'renders' directory as per usual.
The steps to run a network render are as follows:

Choose a scene to render, eg. somescene.xml.
Start the network master process like this:
indigo.exe somescene.xml -n m

The -n m switch tells the process to run as a network master
On another box, start a network slave process like this:
indigo.exe somescene.xml -n s -h lust:7777

The -n s switch runs indigo in network slave mode.

The -h lust:7777 switch tells the slave to connect to the network master running on the host 'lust' on port 7777 (the indigo port)

You should of course substitute the host name running the network master for 'lust'.