mirror of
https://github.com/jokob-sk/NetAlertX.git
synced 2026-04-06 02:01:37 -07:00
143 lines
3.0 KiB
Markdown
143 lines
3.0 KiB
Markdown
# 📈 NetAlertX Growth Playbook
|
||
|
||
If you like NetAlertX and want to help it grow, this is how.
|
||
|
||
This isn’t about spam or "growth hacks." It’s just getting the tool in front of people who already have the problem (manual network docs, blind spots, messy networks).
|
||
|
||
---
|
||
|
||
## 🎯 Who this is for
|
||
|
||
* **Homelabbers** → Proxmox, Unraid, Raspberry Pi setups
|
||
* **Self-hosters** → moving away from cloud / want local-first
|
||
* **Sysadmins / MSPs** → need visibility + fast onboarding
|
||
|
||
---
|
||
|
||
## 💬 Where to post (and how)
|
||
|
||
### Reddit (main channel)
|
||
|
||
Reddit works *if* you don’t sound like marketing.
|
||
|
||
**Subreddits**
|
||
|
||
* r/homelab
|
||
* r/selfhosted
|
||
* r/sysadmin
|
||
* r/networking
|
||
|
||
**What works**
|
||
|
||
* "Show r/homelab" / "I built this"
|
||
* Problem → solution
|
||
* Real screenshots or short GIFs
|
||
|
||
**Example**
|
||
|
||
> Tired of keeping network diagrams up to date?
|
||
> I deployed something that does it automatically.
|
||
|
||
**Avoid**
|
||
|
||
* Over-explaining
|
||
* Buzzwords
|
||
* "Check out my project!!!" energy
|
||
|
||
**Timing (rough guide)**
|
||
|
||
* Tue–Thu mornings (US time)
|
||
|
||
---
|
||
|
||
### Hacker News (Show HN)
|
||
|
||
Good fit because NetAlertX is:
|
||
|
||
* local-first
|
||
* privacy-focused
|
||
* actually useful
|
||
|
||
**Title**
|
||
|
||
> Show HN: NetAlertX – network documentation that updates itself
|
||
|
||
Be ready to answer:
|
||
|
||
* stack (Python / PHP / JS)
|
||
* how discovery works
|
||
* privacy / local scanning
|
||
|
||
---
|
||
|
||
### Awesome Lists
|
||
|
||
Low effort, long-term visibility.
|
||
|
||
Target:
|
||
|
||
* awesome-selfhosted
|
||
* awesome-homelab
|
||
|
||
Keep it simple:
|
||
|
||
> NetAlertX – automated network discovery and documentation with alerting
|
||
|
||
---
|
||
|
||
## 🎥 Content / creators
|
||
|
||
If you or someone else makes videos, these angles work:
|
||
|
||
* **First 5 minutes** → "it already found everything"
|
||
* **Before vs after** → manual vs NetAlertX
|
||
* **Docker setup** → show how easy it is
|
||
|
||
No need for overproduction—real usage > polished demos.
|
||
|
||
---
|
||
|
||
## ⚖️ Positioning (keep it simple)
|
||
|
||
When explaining NetAlertX, this is the mental model:
|
||
|
||
| | Manual Docs | Basic Scanners | NetAlertX |
|
||
| ------- | ----------------- | -------------- | ------------------------- |
|
||
| Updates | Manual / outdated | On demand | **Automatic** |
|
||
| Alerts | None | Limited | **New / unknown devices** |
|
||
| History | None | None | **Device timeline** |
|
||
| Effort | High | Medium | **Set & forget** |
|
||
|
||
---
|
||
|
||
## 🧑💻 MSP / professional angle
|
||
|
||
If you’re using it in real environments:
|
||
|
||
* Faster client onboarding
|
||
* Better visibility
|
||
* Less "what changed?" guessing
|
||
|
||
That’s the value—keep it grounded. And share your experience 🙏
|
||
|
||
---
|
||
|
||
## 🛠 Easy ways to help
|
||
|
||
* Star the repo
|
||
* Post a screenshot of your network
|
||
* Mention it when someone asks "how do you track devices?" or "how do you detect presence?"
|
||
* Write a quick "how I use it" post
|
||
|
||
---
|
||
|
||
## Final note
|
||
|
||
Authenticity matters more than reach.
|
||
|
||
If it feels like marketing, people ignore it.
|
||
If it feels like "this solved my problem," people pay attention.
|
||
|
||
Thanks a lot in advance!
|
||
- jokob
|