[PR #771] Add Maintenant to Monitoring section. #5882

New Issue

GiteaMirror · 2026-05-02T17:16:55-05:00

GiteaMirror commented

2026-05-02 17:16:55 -05:00

📋 Pull Request Information

Original PR: https://github.com/awesome-foss/awesome-sysadmin/pull/771
Author: @btouchard
Created: 4/23/2026
Status: 🔄 Open

Base: master ← Head: master

📝 Commits (1)

226c013 Add Maintenant monitoring tool to README

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)

📄 Description

Maintenant is a self-hosted Docker monitoring tool. Single Go binary, AGPL-3.0, no cloud version, no telemetry. Targets the gap between cAdvisor (too low-level) and Datadog (SaaS/paid). ~100 GitHub stars, actively maintained.

Thank you for taking the time to work on a PR for Awesome-Sysadmin!

To ensure your PR is dealt with swiftly please check the following:

Your additions are Free software
Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts).
Submit one item per pull request. This eases reviewing and speeds up inclusion.
Format your submission as follows, where Demo and Clients are optional.
Do not add a duplicate Source code link if it is the same as the main link.
Keep the short description under 80 characters and use sentence case
for it, even if the project's webpage or readme uses another capitalisation.
Demo links should only be used for interactive demos, i.e. not video demonstrations.
- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`
Additions are inserted preserving alphabetical order.
Additions are not already listed at awesome-selfhosted
The Language tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.
You have searched the repository for any relevant issues or PRs, including closed ones.
Any category you are creating has the minimum requirement of 3 items.
Any software project you are adding to the list is actively maintained.
The pull request title is informative, unlike "Update README.md".
Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb,
"Remove aaa from bbb" for removing, "Fix license for aaa", etc.

Please take some time to answer the following questions as best you can:

Why is it awesome?

Single Go binary (20-30 MB), self-hosted only by design — no cloud tier, no SaaS fallback, no telemetry. Reads directly from the Docker socket, so zero-agent setup. SQLite embedded, Vue 3 frontend embedded in the binary via Go embed — one command to run, one process to monitor. AGPLv3 for self-hosters, commercial on-premise license for organizations that can't use AGPL. No "community edition" vs "enterprise edition" feature gating — same binary, same features.

Have you used it? For how long?

Yes, I'm the author. In production on my own infrastructure for several months before public release. Public Docker image has been pulled around 22,000 times over the past two months.

Is this in a personal or professional setup?

Both. Used across a client engagement (CTO part-time role), my own freelance activity, and a homelab. First paying customer is an operator running an AI hosting stack in production.

How many devices/users/services/... do you manage with it?

Across my own setups: dozens of containers spanning a few hosts. The first paying customer runs it over a larger AI hosting stack. Public usage: ~22k image pulls, no telemetry in the binary so exact install count is unknown.

Biggest pros/cons compared to other solutions?

Pros vs. existing options:

Lighter than Prometheus + Grafana stack (no supervisor heavier than the supervised)
Doesn't meter you by ingestion like Datadog/New Relic/Grafana Cloud
Broader than Dozzle (logs only), Uptime Kuma (uptime only) or Portainer (management, not monitoring) — one pane of glass instead of juggling three
No agent to install, reads Docker socket directly
Binary starts in milliseconds, runs under ~50 MB RAM
AGPLv3 + commercial license, not open-core funnel to a cloud tier

Cons / limitations:

Not for Kubernetes clusters at scale
Not multi-tenant observability — designed for solo operators and small teams
Single-node focus; multi-host scenarios require one instance per host
Younger codebase than Prometheus or Netdata, fewer integrations
Any other comments about your use case, things you've found excellent, limitations you've encountered... ?
The "boring by design" approach pays off: once deployed, it stays out of the way. A recurring pattern among users is -that the first 5 minutes of clicking through the UI surface things they didn't know were running — exposed ports, containers with unneeded privileges, forgotten stacks. Not magic, just the effect of having one simple view of what's actually on the machine instead of three browser tabs. Main limitation: single-host by design; if you run Docker on 10 boxes, you run 10 instances (intentional tradeoff — no central server, no agent fleet to maintain).
Any other comments about your use case, things you've found excellent, limitations you've encountered... ?

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/awesome-foss/awesome-sysadmin/pull/771 **Author:** [@btouchard](https://github.com/btouchard) **Created:** 4/23/2026 **Status:** 🔄 Open **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (1) - [`226c013`](https://github.com/awesome-foss/awesome-sysadmin/commit/226c013942887018b8828021508e60ddaa8586dd) Add Maintenant monitoring tool to README ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description Maintenant is a self-hosted Docker monitoring tool. Single Go binary, AGPL-3.0, no cloud version, no telemetry. Targets the gap between cAdvisor (too low-level) and Datadog (SaaS/paid). ~100 GitHub stars, actively maintained.   Thank you for taking the time to work on a PR for Awesome-Sysadmin! To ensure your PR is dealt with swiftly please check the following: - [x] Your additions are [Free software](https://en.wikipedia.org/wiki/Free_software) - [ ] Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts). - [x] Submit one item per pull request. This eases reviewing and speeds up inclusion. - [ ] Format your submission as follows, where `Demo` and `Clients` are optional. Do not add a duplicate `Source code` link if it is the same as the main link. Keep the short description under 80 characters and use [sentence case](https://en.wikipedia.org/wiki/Letter_case#Sentence_case) for it, even if the project's webpage or readme uses another capitalisation. `Demo` links should only be used for interactive demos, i.e. not video demonstrations. ``- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language` `` - [x] Additions are inserted preserving alphabetical order. - [x] Additions are not already listed at [awesome-selfhosted](https://awesome-selfhosted.net) - [x] The `Language` tag is the main **server-side** requirement for the software. Don't include frameworks or specific dialects. - [x] You have searched the repository for any relevant [issues](https://github.com/awesome-foss/awesome-sysadmin/issues) or [PRs](https://github.com/awesome-foss/awesome-sysadmin/pulls), including closed ones. - [ ] Any category you are creating has the minimum requirement of 3 items. - [x] Any software project you are adding to the list is actively maintained. - [x] The pull request title is informative, unlike "Update README.md". Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb, "Remove aaa from bbb" for removing, "Fix license for aaa", etc. -------------- Please take some time to answer the following questions as best you can:  - **Why is it awesome?** Single Go binary (20-30 MB), self-hosted only by design — no cloud tier, no SaaS fallback, no telemetry. Reads directly from the Docker socket, so zero-agent setup. SQLite embedded, Vue 3 frontend embedded in the binary via Go embed — one command to run, one process to monitor. AGPLv3 for self-hosters, commercial on-premise license for organizations that can't use AGPL. No "community edition" vs "enterprise edition" feature gating — same binary, same features. - **Have you used it? For how long?** Yes, I'm the author. In production on my own infrastructure for several months before public release. Public Docker image has been pulled around 22,000 times over the past two months. - **Is this in a personal or professional setup?** Both. Used across a client engagement (CTO part-time role), my own freelance activity, and a homelab. First paying customer is an operator running an AI hosting stack in production. - **How many devices/users/services/... do you manage with it?** Across my own setups: dozens of containers spanning a few hosts. The first paying customer runs it over a larger AI hosting stack. Public usage: ~22k image pulls, no telemetry in the binary so exact install count is unknown. - **Biggest pros/cons compared to other solutions?** Pros vs. existing options: - Lighter than Prometheus + Grafana stack (no supervisor heavier than the supervised) - Doesn't meter you by ingestion like Datadog/New Relic/Grafana Cloud - Broader than Dozzle (logs only), Uptime Kuma (uptime only) or Portainer (management, not monitoring) — one pane of glass instead of juggling three - No agent to install, reads Docker socket directly - Binary starts in milliseconds, runs under ~50 MB RAM - AGPLv3 + commercial license, not open-core funnel to a cloud tier Cons / limitations: - Not for Kubernetes clusters at scale - Not multi-tenant observability — designed for solo operators and small teams - Single-node focus; multi-host scenarios require one instance per host - Younger codebase than Prometheus or Netdata, fewer integrations - Any other comments about your use case, things you've found excellent, limitations you've encountered... ? - The "boring by design" approach pays off: once deployed, it stays out of the way. A recurring pattern among users is -that the first 5 minutes of clicking through the UI surface things they didn't know were running — exposed ports, containers with unneeded privileges, forgotten stacks. Not magic, just the effect of having one simple view of what's actually on the machine instead of three browser tabs. Main limitation: single-host by design; if you run Docker on 10 boxes, you run 10 instances (intentional tradeoff — no central server, no agent fleet to maintain). - **Any other comments about your use case, things you've found excellent, limitations you've encountered... ?** --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-05-02 17:16:55 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sysadmin#5882