Welcome to Nivio’s documentation!

Nivio is a tool for application landscape management targeted at teams (developers, operators, managers). It follows a no-op approach, i.e. there is no interface for manual data maintenance. Instead, Nivio pulls all its information from data sources, like files and web APIs (e.g. monitoring items) or allows pushing information via its API.

Rendered graph
  • It is easy to install and to maintain. Runs dockerized on a single server with moderate to low hardware requirements. It stores the items, so it can be discarded at any time and be refilled with the next start.
  • No-op usage Besides its initial configuration, it is designed to gather the application landscape information from configurable items, preferably code repositories.
  • Renders the landscapes as a graph See above.
  • Multiple configuration sources While Nivio has its proprietary format, you can also use docker-compose files, or use them as basis and enrich them using further files
  • PULL: Single seed Basic indexing of landscapes driven by a configuration file.
  • PUSH: incremental data aggregation Send configuration files and other formats to build a landscape.
  • Aggregation of item state Using sources, like Prometheus, and marking items accordingly.