Become a financial contributor.

Top financial contributors

Transparent and open finances.

Let’s get the ball rolling!

News from The Network UPS Tools project

Updates on our activities and progress.

About

• For the past quarter of a century NUT brings monitoring and management of UPS, ePDU and similar power distribution devices using various vendor protocols and media to as many OSes and platforms as possible. UPS management protocol Informational RFC 9271 published by IETF at https://www.rfc-editor.org/info/rfc9271
•  NUT aims to provide a vendor-agnostic monitoring and management of power distribution devices, their representation online under common protocol and data model. It facilitates end-users' power source monitoring, safe shutdowns of multiple power consumers during outages, uniform access to devices regardless of vendor/protocol specifics.
•  NUT's audience includes systems administrators and individual users - anyone who has an UPS and wants to benefit from its protection for one or more computers. Being the de-facto standard open-source effort in this area for decades, it is assumed to have innumerable thousands of installations both by aware users and embedded in NAS units, HomeAssistant, etc.; however just a few hundred are active in communications.
•  A goal of NUT is to build and run on all POSIX platforms issued since the turn of millennium, and especially for current versions to still work wherever older releases ran before. An effort to support Windows as a first-class citizen is also underway. The NUT CI farm ensures that every contribution does not regress support of over 300 build scenarios on different operating systems, CPU architectures, compiler and scripting toolkit implementations, etc.
•  Sponsorship would help improve the outreach of the project (e.g. visiting FOSS conferences), as well as its quality by extending the NUT CI farm build matrix for supported platforms (e.g. rent more cloud resources) and sign up for tools used to analyze the code to ensure its reliability and security. It may also help bring more contributors into orbit, especially developers to handle areas requiring particular expertise, to address the backlog and to generalize availability of features introduced as a scratch of somebody's itch in one spot, to improve tests and modern OS integration, as well as documentation writers. Finally, it can help developers and hardware meet, to reproduce setups that community members struggle with, but can not fix on their own nor via remote discussions.

Our team