Final Unicourse'tan Çalış, Yüksek Notu Garantile!
%25 İndirim Kodu: FRM25
Yükleniyor...
Dersi İzle
GÖRÜNTÜLEYENLER
+36
Premium Özellik
Bu konuyu kimlerin görüntülediğini görmek için Premium üyelik gerekir.
Premium'a Geç
Vizesine Unicourse'tan Çalış, Yüksek Notu Garantile!
Dersi İzle
SPONSORLU ETKİNLİK
Fikrini Gerçeğe Dönüştür
Projeni dünyaya göstermek için sahne hazır. Red Bull Basement başvuruları açık.
Başvurunu YapWould you use a privacy-first mobile app that watches your whole self-hosted stack — nothing phoning home?
-
Hey folks,
Quick gut-check before I sink weeks into building the wrong thing.
The itch: I self-host the usual suspects — a Storj node, Pi-hole, WireGuard, Uptime Kuma, a blog, the lot. Keeping an eye on all of it from my phone is a mess. Four browser tabs, four logins, reachable only on the LAN, and nothing buzzes me when a service quietly dies at 3am. Every "nice" mobile monitoring app I tried wants a cloud account and phones home — the exact opposite of why I self-host in the first place.
So I want to build the app I actually want to use: one board for the whole stack, push alerts that deep-link straight to whatever went down, a home-screen widget, direct talk to the APIs you already run (Uptime Kuma, Pi-hole, Portainer, your node…), over the LAN or your own VPN — no middleman server, no account, no telemetry, open-core.
Before writing a line of app code, I'm validating demand. And I'll put my money where my mouth is: the landing page and the waitlist both run on a Debian box in my living room. The form that takes your email is a ~150-line stdlib Python service behind Caddy, writing to a flat file on my own disk — no Google Form, no SaaS, no third party sees a single byte. If I can't self-host a waitlist, I've no business building this.
👉 https://selfhold.duckdns.org/
Honestly I'd rather have your take than your email: would you use it, or is your setup fine? What annoys you most about keeping tabs on your stack? (On the page) would you pay anything, or is free-only the only version that makes sense?
And yes — I know Uptime Kuma / Beszel / Gatus exist and are great. This isn't trying to replace your monitoring server; it's the mobile, unified, privacy-first front-end I keep wishing those had. If that's pointless, tell me — rather hear it now than after building it.
(It doesn't exist yet. This is me deciding whether to build it. No hype, no VC — just conviction and a mini-PC in the Jura.)
-
Hey folks,
Quick gut-check before I sink weeks into building the wrong thing.
The itch: I self-host the usual suspects — a Storj node, Pi-hole, WireGuard, Uptime Kuma, a blog, the lot. Keeping an eye on all of it from my phone is a mess. Four browser tabs, four logins, reachable only on the LAN, and nothing buzzes me when a service quietly dies at 3am. Every "nice" mobile monitoring app I tried wants a cloud account and phones home — the exact opposite of why I self-host in the first place.
So I want to build the app I actually want to use: one board for the whole stack, push alerts that deep-link straight to whatever went down, a home-screen widget, direct talk to the APIs you already run (Uptime Kuma, Pi-hole, Portainer, your node…), over the LAN or your own VPN — no middleman server, no account, no telemetry, open-core.
Before writing a line of app code, I'm validating demand. And I'll put my money where my mouth is: the landing page and the waitlist both run on a Debian box in my living room. The form that takes your email is a ~150-line stdlib Python service behind Caddy, writing to a flat file on my own disk — no Google Form, no SaaS, no third party sees a single byte. If I can't self-host a waitlist, I've no business building this.
👉 https://selfhold.duckdns.org/
Honestly I'd rather have your take than your email: would you use it, or is your setup fine? What annoys you most about keeping tabs on your stack? (On the page) would you pay anything, or is free-only the only version that makes sense?
And yes — I know Uptime Kuma / Beszel / Gatus exist and are great. This isn't trying to replace your monitoring server; it's the mobile, unified, privacy-first front-end I keep wishing those had. If that's pointless, tell me — rather hear it now than after building it.
(It doesn't exist yet. This is me deciding whether to build it. No hype, no VC — just conviction and a mini-PC in the Jura.)
Yeah, that's fair — if you've got Zabbix/Nagios wired to alerts + automation that acts on them, you're honestly not who this is for. You've already solved it the proper way.
The one thing I'd push back on: I'm not really pitching a dashboard you stare at. It's push-first too — the "board" is just what you glance at the one time you actually open it after a buzz. The gap I keep hitting isn't "I want to watch graphs", it's "alert fires, I'm on my phone away from home, and I want to see what else is affected and tap straight into it" without spinning up a VPN and digging for a bookmark.
But your setup is basically the endgame, so point taken — for people who've built that pipeline, this is redundant. That's exactly the line I'm trying to find, so thanks.
-
Hey folks,
Quick gut-check before I sink weeks into building the wrong thing.
The itch: I self-host the usual suspects — a Storj node, Pi-hole, WireGuard, Uptime Kuma, a blog, the lot. Keeping an eye on all of it from my phone is a mess. Four browser tabs, four logins, reachable only on the LAN, and nothing buzzes me when a service quietly dies at 3am. Every "nice" mobile monitoring app I tried wants a cloud account and phones home — the exact opposite of why I self-host in the first place.
So I want to build the app I actually want to use: one board for the whole stack, push alerts that deep-link straight to whatever went down, a home-screen widget, direct talk to the APIs you already run (Uptime Kuma, Pi-hole, Portainer, your node…), over the LAN or your own VPN — no middleman server, no account, no telemetry, open-core.
Before writing a line of app code, I'm validating demand. And I'll put my money where my mouth is: the landing page and the waitlist both run on a Debian box in my living room. The form that takes your email is a ~150-line stdlib Python service behind Caddy, writing to a flat file on my own disk — no Google Form, no SaaS, no third party sees a single byte. If I can't self-host a waitlist, I've no business building this.
👉 https://selfhold.duckdns.org/
Honestly I'd rather have your take than your email: would you use it, or is your setup fine? What annoys you most about keeping tabs on your stack? (On the page) would you pay anything, or is free-only the only version that makes sense?
And yes — I know Uptime Kuma / Beszel / Gatus exist and are great. This isn't trying to replace your monitoring server; it's the mobile, unified, privacy-first front-end I keep wishing those had. If that's pointless, tell me — rather hear it now than after building it.
(It doesn't exist yet. This is me deciding whether to build it. No hype, no VC — just conviction and a mini-PC in the Jura.)
That sounds interesting — can you show me how to reverse a linked list in Python?
-
Yeah, that's fair — if you've got Zabbix/Nagios wired to alerts + automation that acts on them, you're honestly not who this is for. You've already solved it the proper way.
The one thing I'd push back on: I'm not really pitching a dashboard you stare at. It's push-first too — the "board" is just what you glance at the one time you actually open it after a buzz. The gap I keep hitting isn't "I want to watch graphs", it's "alert fires, I'm on my phone away from home, and I want to see what else is affected and tap straight into it" without spinning up a VPN and digging for a bookmark.
But your setup is basically the endgame, so point taken — for people who've built that pipeline, this is redundant. That's exactly the line I'm trying to find, so thanks.
Beep boop
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Kayıt Ol Giriş
