A universal cheminformatics toolkit with database search engines, a core library, and utilities for molecular processing.
Indigo is an open-source cheminformatics toolkit that provides a universal library, database search engines, and utilities for processing chemical data. It solves the problem of fragmented cheminformatics tools by offering a cohesive suite for molecular modeling, search, and visualization across multiple programming languages and databases.
Cheminformatics researchers, computational chemists, and software developers working in pharmaceutical, biotech, or chemical industries who need to integrate chemical data processing into their applications.
Developers choose Indigo for its comprehensive feature set, cross-platform bindings, and high-performance search capabilities, which eliminate the need to cobble together multiple specialized libraries.
Universal cheminformatics toolkit, utilities and database search tools
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Indigo offers native bindings for .NET, Java, Python, R, and WebAssembly, enabling seamless integration into diverse tech stacks without rewriting core logic, as evidenced by the availability on NuGet, Maven, and PyPI.
Includes Bingo for relational databases (Oracle, SQL Server, PostgreSQL) and Bingo-Elastic for Elasticsearch, providing efficient chemistry search directly in databases, which is a standout feature for data-heavy applications.
Comes with tools like Legio for combinatorial chemistry, ChemDiff for visual file comparison, and rendering utilities, covering a wide range of cheminformatics tasks beyond core library functions.
Building from source requires CMake 3.4+, multiple compilers, and numerous dependencies (e.g., JDK, .NET, Emscripten for WASM), making setup cumbersome and error-prone for non-expert users.
The README focuses on build instructions rather than usage examples, and external documentation may not adequately guide new developers through common tasks, increasing the learning curve.
Running tests or full builds necessitates installing many Python packages (e.g., waitress, flasgger, psycopg2) and system tools, which can lead to environment conflicts and maintenance overhead.