
One panel, four versions: every router NetPulse connects adds one more community that can post
What it is A home network monitoring dashboard you run on your own machine. Status from multiple routers is summarized on one screen, and it automatically draws a whole-home network topology. No cloud, single file, open source.
Why it blew up In late October the author added MikroTik, Asuswrt, UniFi and OPNsense support, then posted "now with X support" in each hardware brand's own Reddit community. It gave people mixing gear the "UniFi-style screen" they'd wanted, and stars doubled in two days, from 122 to 246.
BHow you could ride it Don't copy it head-on. Copy the structure: a core plus vendor plugins, with a post in each vendor's community as each one ships. Apply it to mixed-hardware circles like NAS or smart home, or build a Chinese version for soft-router users.
- Data (updated daily) · Repo created 2026-07-31 · 420 stars · 7 days +299
GitHub · stars Data 2026-10-27 → 2026-11-20 (25 days, 24 observations). Points before 10-28 come from deeply / archive backfill, not every day has one
A Spanish IT veteran built a monitoring dashboard for his four OpenWrt routers, and after three months it had 120 stars. In late October he added MikroTik, UniFi, Asuswrt and OPNsense support, reposted the same thread under a new title in each brand's Reddit community, and stars doubled in two days. The product is real, but what drove the growth is a repeatable distribution structure: every vendor you support gives you a legitimate place to post.
Four home routers, one screen you can't see all of
On the evening of Aug 22, 2026, a Spanish developer on GitHub named gnacho posted in the official OpenWrt forum looking for testers. He started with his own setup: a GL.iNet Flint 2 as the main router and three used Xiaomi AX6 units as APs, all running OpenWrt. He wanted to know which AP each client was on, how each AP was doing, and whether phones roamed smoothly between them. He'd found no tool that did this: "Everything that can do this is the vendor's own product, locked to their closed system."
So he built one. The next morning a user named dekarl tried it on three switches and reported that the topology didn't render, plus seven small issues. The author replied: "Thanks a lot (my first user, yay)." The thread went on to 1,529 views and 28 replies on the OpenWrt forum.
The next three months were slow growth. By Oct 27 the repo had 100 stars, and by Nov 13 it had 121. Over those 17 days it gained 21 stars in total. Then:
| Date | star | Added that day |
|---|---|---|
| 11-13 | 121 | +2 |
| 11-14 | 158 | +37 |
| 11-15 | 246 | +88 |
GitHub daily star count; live figures afterward were 269 stars and 18 forks. The week before, it gained only 9 stars; this week it gained 131.
What it is
A self-hosted home network monitoring dashboard. Opening it shows an automatically drawn whole-house network map: gateway, each AP, switches, wired and wireless devices, VMs on Proxmox, WireGuard tunnels, all grouped by room. The topology is inferred from the switch MAC address tables, and devices with LLDP show their names. Other pages cover each router's CPU, memory, temperature, WAN traffic and latency, with a health score from 0 to 100; each device's type, band and signal strength; Wi-Fi roaming history and channel congestion; and AdGuard Home blocking stats. When something breaks it pushes alerts to the browser, ntfy or Telegram, and it can connect to Home Assistant.
Setup is simple: a single Go binary with the frontend bundled in, data in SQLite, no Docker, just run it under systemd. It is read-only by default and pulls data from the routers over SSH, so it can't touch your config. For live Wi-Fi events you can install a small agent on the router that uses 12 MB of RAM. No cloud, no account, no telemetry, open source under AGPL-3.0. The website has a read-only demo you can open without signing up to see the topology map.
It sits in a spot nobody has properly filled:
- LibreNMS, Zabbix, OpenWISP are full-featured but heavy, and their interfaces aren't designed for home use.
- NetAlertX, WatchYourLAN (each with over 7 thousand stars) find devices by scanning the LAN, and can't read roaming or temperature data from inside the router.
- Scanopy (around 6 thousand stars) also draws network maps automatically, using scanning, and is the most direct rival on topology.
- UniFi's own console has the best experience, but it only works with Ubiquiti hardware.
- OpenWrt's built-in LuCI pages show one router at a time.
Searching GitHub for "openwrt dashboard" or "openwrt monitor", NetPulse now ranks first. Second is a 201-star option that requires building your own Grafana setup, and everything below that has single-digit stars. It's first in a narrow category, with several large projects at five or six thousand stars above it.
Why Nov 13
From Oct 26 to 30, over those five days, the author added MikroTik RouterOS, Asuswrt and UniFi in a separate integrations repo, then OPNsense (still beta). RouterOS is a closed system that can't run an agent, so he wrote an external push program that reads data from the router's API on another machine.
Then around Nov 13, the same post appeared in r/mikrotik, r/Ubiquiti and r/opnsense, with only the last word of the title changed: "NetPulse: self-hosted network monitoring, now with MikroTik RouterOS / Unifi / OpnSense support." Each post had the same three parts: a large whole-house topology image, a feature list, and links to the demo, website and repo. The body ended with "122 stars, 14 forks, around 950 issues" and the line "boring bugs appears when someone else runs the thing on untested hardware."
None of these three communities used to be OpenWrt territory, and each one discusses a single brand. To those users NetPulse was new; to the moderators, "we now support your devices" is a legitimate product update, not spam. The post had 122 stars when it went up and 246 two days later.
The top positive reply under the r/mikrotik post praised exactly the point it sells: "My network mixes MikroTik and UniFi, and this gives me a single pane of glass!" Another person said "I can totally see us using it at work" and asked whether the topology map could be edited by hand. In another community someone said they had tried it on 16 devices and it worked well.
The thread argument was about AI
The first comment was: "How much of the dev work was done by AI agents?" A dozen replies followed. One said "every app Claude writes is these four colors," and another wrote "I wish someone had made a project called Zabbix," meaning the wheel you built already exists.
This isn't the first time. In Oct 21, when the author posted on r/selfhosted, someone went through the repo commit by commit: 75 commits under agent identities, about 250K lines of code written in 89 days, and up to 53 commits in a single day. The pace checks out too: about 145 releases in the 107 days since the repo was created, with issue and PR numbers already at 2041.
The author's reply in r/mikrotik: "AI helps me write code, but the technical decisions aren't its. I've worked in IT for 25 years, I've kept updating since it went public in August, I run it at home and at work, and I'll keep maintaining it."
The speed AI brings has kept people around. Bugs users report are often fixed and released the same day, release notes name each person who reported an issue, and one outside contributor has already made 24 commits. The latest release's attached download was fetched 523 times, and the last 100 releases total 8,602 downloads (GitHub, November). The server updates itself, so most of those downloads are likely existing users upgrading. Extrapolating, that suggests a few hundred active installs (inference), which matches the author's own "a few hundred users."
The routes it didn't take
It wasn't posted to Hacker News, no one on X shared the repo link, no media covered it, and it didn't make GitHub trending. All of the traffic came from the author's own posts in the OpenWrt forum and seven or eight Reddit communities.
The name is a problem too. "NetPulse" is taken by many things: EGYM's fitness app, a Swedish ISP platform, several Windows utilities, and a Docker version of "NetPulse" from a German blog that has nothing to do with this project. Someone under the r/mikrotik post said: "The MikroTik monitor I wrote for my ISP two years ago was also called netPulse." Being unsearchable works against building up stars over time.
If it were you
B. Worth trying: the playbook can be copied and nobody has copied it yet, but this category has a low ceiling, and self-hosting communities are increasingly unforgiving toward AI-written projects. NetPulse already holds the top spot for "multi-router dashboard for OpenWrt" and ships releases every day, so building the same thing head-on makes no sense. What's worth taking is its distribution structure.
Who it suits: developers with a mixed-hardware setup at home or work who actually have this pain point. Anyone who knows a hardware or self-hosting community well (OpenWrt, MikroTik, NAS, Proxmox, Home Assistant) and is willing to keep replying on forums and Reddit over the long run.
Who it doesn't suit: anyone aiming for a thousand stars in a month. NetPulse took three months to reach 120 stars, and its biggest burst added just over a hundred. Anyone who can't explain how much AI was involved or doesn't plan to maintain the project long-term will get torn apart in communities like r/selfhosted.
How to do it: three approaches, from most to least certain:
- Change the community, keep the same structure. One core, plus a plugin per vendor, with each plugin tied to a community that discusses only that brand. NAS (Synology, QNAP, TrueNAS, Unraid), UPS units, smart home gateways and cameras all fit this pattern: every brand has users, the vendor's own dashboard only covers its own gear, and people running mixed setups lack a unified screen.
- Localize for Chinese-speaking users. Many people in the Chinese soft-router community run OpenWrt (iStoreOS, ImmortalWrt), often alongside iKuai or RouterOS. NetPulse only has Spanish and English interfaces. A similarly timed OpenWrt traffic-identification project that launched on V2EX picked up 74 stars, which shows the community will star projects, but no one has yet combined multi-router aggregation with automatic topology.
- Fill the gaps it leaves. The most requested features in the threads are a topology map you can edit by hand, switch-to-switch links drawn as real links (the author admits they currently hang off the gateway), and more interface languages.
How to get users: first post on the official forum of your target hardware, saying "this is my setup, I'm looking for testers," and build an initial group of people who will report bugs for you. Each time you add a vendor, post "now with X support" in that vendor's community, with a real topology image, a no-signup demo, and one checkable number. Say openly in the post where AI was used and what the human did, so people don't have to dig it out. Search the name before you ship and avoid another collision.
When to move: no rush, since nobody is copying this category yet. But if a large project like Scanopy adds the ability to read router internals, the middle tier disappears. Having the first plugins and community posts ready before the first half of 2027 is the safer timing.
Signs you've misread it: ① after NetPulse's burst, growth returns to a few stars a week, meaning "post again with each vendor" only works once and the community won't buy it twice; ② the posts in your first hardware community are full of arguments about AI and almost nobody actually tries it, meaning anti-AI sentiment has outweighed demand; ③ Scanopy or NetAlertX adds router API support and a project with several thousand stars covers your position.
Research notes: competitor table, acquisition evidence, full research report
- Competitors
Name Where Launched Scale How it differs from this one UniFi Network app (topology, clients) Big-company features Years All Ubiquiti users The experience sets the standard but only covers their own hardware; NetPulse offers a UniFi-like single pane for OpenWrt and mixed networks GL.iNet GoodCloud Big-company features Years GL.iNet users Vendor cloud management; NetPulse has no cloud and no account LuCI status pages / luci-app-statistics / nlbwmon Open source Years Ships with OpenWrt Covers a single router only, with no multi-device rollup or topology OpenWISP(controller / monitoring) Open source 2016 / 2020 798 / 245 star Full enterprise Django stack, too heavy for home use benisai/Openwrt-Monitoring Open source 2022-04 201 star Prometheus+Grafana requires you to build it yourself, with no topology or device view Scanopy (formerly NetVisor) Open source 2025-09 5,961 star Draws network maps automatically via scanning, can't read router-internal Wi-Fi, roaming or temperature data NetAlertX Open source 2021-12 7,413 star ARP scans find devices and alert on new ones, but they don't cover router health or topology WatchYourLAN Open source 2022-08 7,666 star Lightweight IP scanner, narrow feature set LibreNMS / Zabbix Open source 2013 / 2014 5,009 / 6,574 star Proper SNMP network management, full-featured but heavy, with a poor home-use experience unpoller Open source 2018 2,744 star Exports UniFi data into Grafana, UniFi only netqmon / openwrt-pulse / luci-theme-carbon Open source 2026-09 to 11 74 / 0 / 114 star Similar small projects that only cover one slice: traffic detection, a traffic dashboard, or a theme dashboard. None of them has gained traction in the English community - Where users come from
- Verified OpenWrt official forum: 2026-08-22 posted looking for beta testers, 1,529 views, 28 replies (Discourse JSON)
- Verified Reddit niche subreddits (author self-posted): r/openwrt (around September), r/foss, r/selfhosted (10-21, which sparked AI-written-content accusations)
- Verified Reddit vendor subreddits (same post distributed after adding integrations): around 11-13, posted to r/mikrotik, r/Ubiquiti, and r/opnsense as "now with X support", with the body citing 122 stars. Over the next two days, stars went from 121 to 246
- Verified No-signup online demo + features page: every post links to demo.netpulse.cloudless.club and /features
- Inferred HN / X / media: the hackernews library and x live search returned no results
- Inferred Discussion heat from the controversy: AI-written-content accusations filled much of the comments on the r/selfhosted and r/mikrotik posts. Whether that pushed the posts up in ranking is speculation
gnacho/netpulse (NetPulse): why it took off
Data as of 2026-11-15 (our GitHub library) and the live GitHub API at time of research. Unless noted, all star counts come from our GitHub library repo_day.
Bottom line
NetPulse is a self-hosted home network monitoring dashboard built by a Spanish indie developer (GitHub: gnacho, Reddit: bender_fut) who has worked in IT for 25 years. It started out serving only the OpenWrt crowd and slowly gathered about 120 stars over three months. In late October it added integrations for MikroTik, Asuswrt, UniFi, and OPNsense. The author then posted nearly identical "now with X support" posts to r/mikrotik, r/Ubiquiti, and r/opnsense around 11-13. When the posts went up, the project had 122 stars. Two days later it was at 246 (live GitHub count at research time: 267).
Each new vendor supported means another subreddit you can post in. That's the direct reason it took off this time. The product also has real substance: one dashboard shows the status of multiple routers and automatically draws the network topology. It's OpenWrt-native, doesn't require the cloud, and installs as a single binary. In the home-network tier, no one else had combined these things.
1. What it is
- A single Go server binary with the React 19 frontend bundled in, data stored in SQLite, no Docker needed, run under systemd. On the router, you install an agent using about 12 MB of memory (.ipk / .apk, with a LuCI page), or you can pull data read-only over SSH alone.
- Features: health status across multiple routers (CPU, memory, temperature, uptime, WAN traffic and latency), plus a 0–100 health score. The topology map is built automatically from switch MAC address tables (bridge FDB), LLDP, and SNMP. Also includes client classification, Wi-Fi roaming and channel analysis, WireGuard, AdGuard Home, speed tests, and alerts (Web Push / ntfy / Telegram / webhook). It also connects to Home Assistant (MQTT) and has a read-only MCP service. The UI is an installable PWA with multi-user support, in Spanish and English.
- Vendor integrations live separately in the
netpulse-integrationsrepo: RouterOS (10-26), Asuswrt (10-27), UniFi (10-30), and OPNsense (beta, added later). Sources: README, netpulse-integrations commit history. - License: AGPL-3.0. The official site netpulse.cloudless.club sits under the author's Spanish-language "Cloudless self-hosted free software club" (cloudless.club). There's also a no-signup, read-only online demo (demo.netpulse.cloudless.club).
2. Competitors
| Product | Where | Launched | Scale | How NetPulse differs |
|---|---|---|---|---|
| UniFi Network app (topology, client list) | Big-company features | Years | All Ubiquiti gear | The benchmark experience, but only for Ubiquiti hardware. NetPulse gives OpenWrt and mixed-vendor networks a "UniFi-like single dashboard". Someone in the r/mikrotik thread was literally asking for "MikroTik + UniFi on one screen" |
| GL.iNet GoodCloud | Big-company features | Years | GL.iNet users | Vendor cloud management. NetPulse's selling point is the opposite: no cloud, no account |
| LuCI's built-in status page / luci-app-statistics / nlbwmon | Open source (bundled with OpenWrt) | Years | All OpenWrt devices | Only shows one router at a time. No multi-router rollup, no topology |
| OpenWISP(controller / monitoring) | Open source | 2016 / 2020 | 798 / 245 star | Enterprise-grade bulk OpenWrt management, a full Django stack, too heavy for home use |
| benisai/Openwrt-Monitoring | Open source | 2022-04 | 201 star | Prometheus + Grafana setup, which you have to build yourself. No topology or device view |
| Scanopy (formerly NetVisor) | Open source | 2025-09 | 5,961 star | A "network map that updates itself", inferring topology through scanning. It doesn't read router-internal Wi-Fi, roaming, or temperature data. Topology is NetPulse's biggest direct competitor |
| NetAlertX (formerly Pi.Alert) | Open source | 2021-12 | 7,413 star | Finds devices via ARP scans and alerts on new ones, but doesn't cover router health or topology |
| WatchYourLAN | Open source | 2022-08 | 7,666 star | Lightweight IP scanner, narrow feature set |
| LibreNMS / Zabbix / Checkmk | Open source | 2013–2019 | 5,009 / 6,574 / 2,646 star | Proper SNMP network management, full-featured but heavy and ugly. A commenter in the r/mikrotik thread said "I wish someone would build a project like zabbix / librenms" |
| unpoller | Open source | 2018 | 2,744 star | Exports UniFi data into Grafana, UniFi only |
| ntopng / Netdata | Open source | 2015 / 2013 | 8,347 / 81,418 star | One focuses on traffic analysis, the other on host metrics. Neither does home-network topology or multi-router rollup |
| Similar small projects: jarvis2f/netqmon (OpenWrt app traffic detection, V2EX launch), baffox888/openwrt-pulse (traffic topology dashboard), mrjoechen/luci-theme-carbon (LuCI theme with a dashboard), WrtPulse (Android app for managing OpenWrt over SSH) | Open source / Android | 2026-09 to 11 | 74 / 0 / 114 stars / small | Each covers only one slice, and none has gained traction in the English community |
Bottom line: among projects specifically building an "OpenWrt multi-router rollup dashboard", NetPulse (267 stars) already ranks first on GitHub. Searching GitHub for openwrt monitor / openwrt dashboard, the second place is a Grafana setup with 201 stars, and the rest are single digits. Widen the scope to "home network monitoring / topology" and older projects like Scanopy, NetAlertX, and WatchYourLAN sit above it with 5–8k stars. So its position is first in a narrow niche.
3. Growth data
- Our GitHub library: 10-27 has 100 stars, up 21 over the 11-13 to 121,17 day window (about 1.2 per day on average). 11-14 to 158 (+37), 11-15 to 246 (+88). gain_7d 131, versus only 9 the previous week. Live GitHub API at research time showed 267 stars and 18 forks.
- The first 100 stars accumulated between 7-31, when the library was created, and 10-27. GitHub's stargazer timestamp API wasn't available this time (401/403), so the day-by-day breakdown couldn't be pulled.
- Indirect evidence of installs: the latest release v2.52.0 (published 11-11) has 523 attachment downloads, including 174 for the server linux_amd64 build and 34 for arm64. Across the last 100 releases, attachments total 8,602 downloads (GitHub releases API). The server checks for and applies updates itself, so most of these numbers are likely existing users upgrading. Estimated active installs are in the hundreds, which matches the author's claim in an r/foss post that "we already have several hundred users" (unverified).
- Development pace: about 145 releases in 107 days (current v2.52.0), issue/PR numbers have reached 2041, and the author has made 1,221 commits. External contributor Bann-DEV has 24 commits, and users such as gnulan, mgrupenhoff, and LemurTech have reported bugs (GitHub contributors API, v2.52.0 release notes, #2041).
4. Where users came from (growth tactics)
All of it is self-posted by the author. No media, KOLs, X, or HN traffic was observed.
| Timeline | Channel | Item | Results |
|---|---|---|---|
| 2026-08-22 | OpenWrt official forum, Community Builds section | Long "looking for beta testers" post describing pain points across the author's four OpenWrt routers at home | 1,529 views, 28 replies, 9 participants (Discourse JSON). Recruited early testers, including feedback like LLDP not working |
| About 2026-09 | r/openwrt | "NetPulse, a 100% free and opensource NOC for OpenWRT" | Score not retrieved (Reddit blocked scraping) |
| 2026-09 to 10 | r/foss | "Your router belongs to you, and so does your network", playing the data sovereignty card | The post claims "several hundred users" |
| 2026-10-21 | r/selfhosted (tagged Release (No AI)) | "NetPulse watches (and controls) everything…" | Sparked an AI-written-content controversy: someone listed line-by-line traces of the opencode agent, including 75 commits under agent identities, about 250k lines over 89 days, and up to 53 commits in a single day. The post originally had no link; the author added one later. Our library only has data from 10-27 onward, so how many stars this post brought in is unclear |
| About 2026-11-13 | r/mikrotik, r/Ubiquiti, r/opnsense (possibly other versions too) | The same article with a new title: "NetPulse: self-hosted network monitoring, now with MikroTik RouterOS / Unifi / OpnSense support", with a large topology diagram. The body cites "122 stars, 14 forks, around 950 issues" | The star surge started here: 122 → 246, doubling in two days. Real users in the comments were trying it ("tried it on 16 devices, works great"), alongside AI accusations ("every Claude-built app uses these four colors") and complaints about it being posted to the OPNsense subreddit |
Other channels:
- HN: our hackernews library returned no results when searching by repo name, domain, or keyword.
- X: live X searches for
github.com/gnacho/netpulse,netpulse openwrt, andnetpulse selfhostedeach returned 0 results. - Media and blogs: none. The only write-up is a post on the contributor's own blog as215855.net about adding MCP to NetPulse, plus an automatic DeepWiki entry.
- The German blog buschehome.de 10-28 wrote "NetPulse installieren" about a different product with the same name: a Docker / Portainer deployment, and this project explicitly doesn't use Docker. It can't be counted as exposure for this project.
5. Why it took off
- The more vendor integrations, the more communities you can post in. From 10-26 to 10-30 in five days it added the RouterOS, Asuswrt and UniFi external pushers, then OPNsense. Each one gave a reason to post "now with X support" in that vendor's subreddit. r/mikrotik, r/Ubiquiti and r/opnsense are single-vendor communities that were never part of the OpenWrt project's turf, and posting in all of them together is what doubled 11-14/15.
- It hit the "non-UniFi users want that UniFi dashboard" itch. The screenshots show an auto-drawn whole-home topology and a health score at a glance, which is exactly what UniFi users have and OpenWrt / MikroTik / mixed-network users don't. The most common replies were "single pane of glass" and "I want this at work too."
- Almost no trial friction. A no-signup read-only demo plus a feature checklist page, attached to every post. Installing is just a 24 MB binary, no Docker, about 20 MB of RAM.
- AI-accelerated iteration speed and responsive replies. About 145 releases in 107 days, with 2000+ issues/PRs. User bugs get fixed and shipped the same day, and the release notes name each reporter in thanks. That keeps early users around and turns them into contributors. The cost is that every post gets someone asking "vibe coded?" Those arguments themselves generate comments that bump the posts (speculation).
- Values-driven narrative. "Your router belongs to you," no cloud, no telemetry, AGPL, and it sits under a "Cloudless Club" banner. That plays well in communities like r/selfhosted and r/foss.
6. What's the differentiation, and is it why it broke out?
- Differentiation: OpenWrt-native (agent package + LuCI page + read-only SSH) + multi-router aggregation + auto topology + home-network details like Wi-Fi roaming, all in a single file. Heavy network managers (LibreNMS, Zabbix, OpenWISP) don't do home-friendly UX; light scanners (NetAlertX, WatchYourLAN) can't read router internals; Scanopy only draws diagrams. NetPulse sits in the gap between them.
- Is that the cause? The differentiation earned about 120 stars over the first three months. But it has a low ceiling in the OpenWrt circle: the official forum post got only 1,529 views. The real surge came from copying the differentiation to other vendors, i.e. the external-pusher architecture plus distribution through new subreddits. So the answer: differentiation is the foundation, multi-vendor expansion plus targeted posting is what switched on the growth.
7. Visibility and copycats
- Visibility: it's circulating in small circles. Discussion only in a few networking and self-hosting subreddits and on the OpenWrt forum. No HN, no X, no media, and it hasn't made GitHub trending (only 107 days old, and trending only admits repos about 60 days old, which it met but still didn't make it). Open source and free, so no revenue.
- Copycats: no obvious imitators.
- yburylov/NetPulse (Russian, created 10-05, 1 stars) shares the name and also does OpenWrt monitoring, but as Windows / Android / iOS clients. It looks more like a name collision.
- On GitHub, samex, borky, juflo, dutchmillbytes, Bann-DEV and others are straight forks.
- The name "NetPulse" itself collides badly: EGYM's fitness app, the Swedish ISP platform netpulse.se, the Docker-based NetPulse in the German blog, plus several Windows tools. That hurts search and SEO.
8. What others can learn
- Split the product into "core + vendor plugins," and post "now with X support" in each vendor's community as each integration lands. Re-titling the same article lets you work through several vertical subreddits in batches, and each batch has new content, so it doesn't read as spam.
- Every post uses the same three pieces: a real large topology screenshot, a no-signup demo link, and a feature checklist page. The body cites verifiable numbers like "122 stars, ~950 issues," which makes the project look alive.
- Recruit beta testers on the official forum first to build a seed user base, then move into the big communities.
- Use AI to keep the pace at "fixed today, shipped today," and name reporters in the release notes to turn users into contributors. But be ready to be asked how much AI was used; it's better to state it in the post up front. The r/selfhosted episode got called out because the wording was vague.
9. Still unclear
- Per-post scores and comment counts on the Reddit posts, and the specific reaction in the r/Ubiquiti thread. Reddit blocks scraping, so I couldn't get them.
- Whether the 11-13 round also went to r/selfhosted, r/homelab, r/HomeNetworking and others wasn't fully checked.
- The split of the first 100 stars between the August forum post, the September r/openwrt post, and 10-21 r/selfhosted can't be separated without stargazer timestamps.
- Real install base: only release download counts and the author's own "a few hundred users" claim. The project's anonymous counter (issue #822) is still just a proposal.
- Whether the surge lasts: the reputational risk of AI-written code and the sustainability of maintenance are still open questions.
Sources
- Repo and README: github.com/gnacho/netpulse; integrations repo: github.com/gnacho/netpulse-integrations
- OpenWrt forum post (2026-08-22): forum.openwrt.org/t/netpulse-self-hosted-monitoring-for-open…
- r/selfhosted(2026-10-21):www.reddit.com/r/selfhosted/comments/1xh1t4f/
- r/mikrotik (about 11-13): www.reddit.com/r/mikrotik/comments/1xvbqnw/
- r/opnsense (about 11-13): www.reddit.com/r/opnsense/comments/1xvf1ng/
- r/Ubiquiti (about 11-13): www.reddit.com/r/Ubiquiti/comments/1xvbxys/
- r/foss:www.reddit.com/r/foss/comments/1wr1afo/ ;r/openwrt:www.reddit.com/r/openwrt/comments/1wbibe7/
- Anonymous counter proposal: github.com/gnacho/netpulse/issues/822
- Cloudless Club: cloudless.club/; contributor blog: as215855.net/posts?tag=netpulse
- Competitor star counts: GitHub API (at time of research)
- Star curves: our github repo_day (10-27 to 11-15); HN: hackernews table; X: x-radar
x live