Would a Self-Hosted Update Server for Desktop Apps Be Useful?
Key topics
Some features it supports right now:
Channel-based releases (stable, nightly, beta)
Platform/architecture-aware updates
Critical update enforcement
Basic telemetry aggregation
Intermediate build support
Team-based management and authorization
Support for multiple updaters (Squirrel, Electron Builder, etc.)
Public and private apps
I know this is a pretty niche problem — not every project needs it. But I’m curious what you think:
Would you stick with SaaS/GitHub Releases, or actually self-host an updater?
What pain points do you see in the standard flow that something like this could solve?
Repo if you want to take a look: https://github.com/ku9nov/faynoSync
Would love to hear your perspective
The author is seeking feedback on their project, faynoSync, which allows for self-hosted update APIs for desktop apps, and is wondering if it's a useful solution.
Snapshot generated from the HN discussion
Discussion Activity
No activity data yet
We're still syncing comments from Hacker News.
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
Discussion hasn't started yet.