Zumbyte Remote
Zumbyte Remote is a remote-access system that controls Windows, Mac, and Linux computers using a fixed nine-digit ID and one-time password, with an optional…
Platform availability
Available on 3 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
47/100 Fair
- Maintained
- 72last commit 9 days ago
- Popular
- 00 GitHub stars
- Easy to install
- 553 install platforms, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
- GitHub stars
- 0
- Open issues
- 0
- Last commit
- 2026-11-12
- License
- MIT
- Activity
- rising
Checked 9 days ago - source: GitHub (ZUMBYTE-AppSolution/zumbyte-remote-release)
Resources & Compatibility
Requirements not published yet.
Checked 9 days ago - source: Docker Hub image tags and published docs
First-install notes
- HTTPS, proxy & port (alpha) Before starting the server, point a dedicated HTTPS domain at it through a reverse proxy that supports WebSocket; the internal target port is HTTP 8787. Deploy on Unraid or the Mac and, because it is an alpha (0.3.0-alpha.1), update the server first and then the desktop apps and Windows services. source
- Connecting devices Enter the target computer's fixed nine-digit ID and one-time password, then approve the requested access on that computer. source
Fetched yesterday - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Do I need a reverse proxy before starting the server?
Yes, you should set up your own HTTPS domain with a reverse proxy and WebSocket support before starting the server. The internal target port is HTTP 8787.
Where are the server accounts and registered computers stored?
Accounts and devices are kept in the Appdata folder.
Do signed application updates require GitHub credentials?
No, signed application updates require neither a GitHub-API nor a GitHub-Token. Update the server first, then the desktop apps and Windows services.
Which access controls can I configure for a specific computer?
For each device you choose whether someone on site must confirm, the central login is sufficient, or an additional device password is required.
Answers sourced from github.com
Community
No community discussions collected yet.