> ## Content Index
> Fetch the complete content index at: https://itsfoss.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Despise Systemd? A New Init System Debuts as a Minimalist Process Supervisor for Linux
- URL: https://itsfoss.com/news/nitro-init-system/
- Published: 2025-08-26T04:51:35.000Z
- Updated: 2025-08-26T04:53:01.000Z
- Description: Nitro is a simple, tiny but flexible init system. It is under heavy development currently.
- Author: Sourav Rudra
- Tags: First Look, News, #Import 2025-11-08 21:15

A new Linux init system called Nitro [has been released](https://inbox.vuxu.org/supervision/87ect3sa27.fsf@vuxu.org/?ref=itsfoss.com). It acts as a supervisor, managing and monitoring services to ensure they start correctly and continue running reliably. Nitro is designed to be lightweight, simple, and efficient, making it suitable for small systems, embedded devices, and containerized environments.

For clarification, [init](https://en.wikipedia.org/wiki/Init?ref=itsfoss.com) systems are programs that start and manage other services on a computer, ensuring they run correctly during startup and shutdown. In this case, Nitro is a minimal and reliable alternative to heavier systems like [systemd](https://systemd.io/?ref=itsfoss.com), focusing on simplicity and predictable service management.

Let's dive in! 😄

## Nitro: What to Expect?

![the github repo for nitro is shown in this picture with many files and a folder being visible in the middle, towards the right, we can see some important details like the about, releases, contributors, and lanugages information](https://itsfoss.com/content/images/2025/08/nitro-git-hub-repo.png)

Developed by [Leah Neukirchen](https://github.com/leahneukirchen?ref=itsfoss.com), who is known for her work on [Void Linux](https://voidlinux.org/?ref=itsfoss.com), Nitro organizes services in simple folders with scripts to configure, start, stop, or log each service. It can handle one-time tasks as well as services that need to run continuously.

Nitro keeps all runtime data in memory (*RAM*), **making it suitable for systems with limited resources or read-only filesystems**. It can also run efficiently in containers, providing fast and reliable service supervision.

Unlike systemd, Nitro focuses solely on starting and supervising services, avoiding complex dependency trees or deep integration. This approach makes it easier to manage, particularly for small systems or lightweight containers.

Compared with [runit](https://smarden.org/runit/?ref=itsfoss.com), Nitro keeps runtime state in memory and allows flexible service setups. It is compact, efficient, and adheres to modern Linux standards while remaining easy to understand.

Currently, it **does not include advanced features** like readiness checks or service overrides, but it is designed to stay minimal, leaving extended policies to external tools if needed.

The source code is available on [GitHub](https://github.com/leahneukirchen/nitro?ref=itsfoss.com) and a detailed comparison with runit can be found in Leah’s [blog post](https://leahneukirchen.org/blog/archive/2025/08/comparing-nitro-to-runit.html?ref=itsfoss.com).

[Nitro](https://github.com/leahneukirchen/nitro?ref=itsfoss.com)

[leah blogs: Comparing nitro to runit![](https://itsfoss.com/content/images/icon/favicon.ico)Leah Neukirchen](https://leahneukirchen.org/blog/archive/2025/08/comparing-nitro-to-runit.html?ref=itsfoss.com)