Would a self-hosted update server for desktop apps be useful?

1 points by ku9n ↗ HN
Most Electron and desktop apps today rely on GitHub Releases + Squirrel or a SaaS service for auto-updates. I’ve been working on a project called faynoSync that lets you self-host an update API instead.

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

0 comments

[ 5.0 ms ] story [ 16.5 ms ] thread

No comments yet.