Astronomical imaging and instrument control software for observatories, remote setups and backyard telescopes.
New INDIGO 3 is now available! Download now »
INDIGO is astronomical imaging and instrument control software for both professional observatories and amateur astronomers. It controls cameras, mounts, focusers, filter wheels, domes and the rest of the equipment, and it takes care of the imaging, guiding, focusing and plate solving on its own.
It is built around a distributed architecture. Device drivers, automation agents and client applications are all connected to a software bus, which can live inside a single application or span several machines over a network. A camera attached to a small computer at the telescope is controlled the same way as a camera plugged into your desktop.
Robustness is the point of the whole exercise. INDIGO is designed with stability as the first priority, because a night of imaging that is interrupted by the software is a night lost. That is also why INDIGO is used for the automation of professional telescopes and remote observatories, not only for astrophotography at home.
INDIGO is a software bus, not a chain of pipes. Drivers, agents and clients can run in a single process, where a property change is a function call instead of a round trip through a socket — in the best case up to 1000 times faster than systems that run each driver as a separate process. Less CPU and less memory also mean longer battery life in the field.
Stability comes before features. The framework is written in ANSI C, the wire protocol is versioned and stays backward compatible, and the project is managed conservatively to protect the work of everybody who integrates with it. Drivers are tested against the real hardware whenever it is available.
Every part of a setup runs where it makes sense: the server on a small computer next to the mount, the client on your desktop, laptop or tablet. Services announce themselves on the network, so clients discover them without any configuration. Bigger setups are not limited to a single server either: one INDIGO server can attach the bus of another, so a mount controlled by one computer and cameras attached to another appear as a single setup, and a client can be connected to several servers at the same time. The very same drivers can also be linked directly into an application when no network is involved.
Servers and drivers run on Linux and macOS, and the Windows server is on its way — most drivers are already ported to it. Client applications run on Linux, macOS, Windows, iOS and iPadOS. The same code scales from a Raspberry Pi to a workstation.
INDIGO Server needs no display. Start it on a headless machine and control it from any INDIGO application on your desktop, laptop or tablet — or from the built-in web panel, when a browser is all you have at hand. Imaging sequences, guiding, focusing, mount control and plate solving are carried out by INDIGO agents running on the server itself, so once started they keep running on their own, with no client connected at all. You can close the application, put the laptop to sleep or lose the WiFi, and connect again later to check how the night is going.
Over 130 device drivers and 10 agents are distributed with INDIGO 3.0, covering cameras, mounts, focusers, filter wheels, domes, rotators, adaptive optics, GPS and auxiliary devices. Legacy INDI style drivers can be used as well, and the ALPACA agent exposes INDIGO devices to ASCOM clients. See the full list »
Whole observing sequences can be written as scripts and executed by the scripting agent on the server, and any property can be manipulated straight from the command line with indigo_prop_tool — handy for cron jobs, remote observatories and roll-off roof setups.
INDIGO is open source under the INDIGO Astronomy open-source license, a BSD style, business friendly license. No GPL, so hardware vendors and commercial applications can build on INDIGO and ship it, including through application stores.
Install INDIGO from the Downloads page, check that your equipment is supported in the list of device drivers and pick an application from the compatible software page. If you are a developer or a hardware vendor, the For Developers and For Vendors pages are the place to start.
—