A self-hostable web dashboard for waking up and managing devices on your local network using Wake-on-LAN.
UpSnap is a web-based Wake-on-LAN application that allows users to remotely power on computers and other devices on their local network from a browser. It solves the problem of needing to manually send magic packets via command-line tools by providing an intuitive dashboard for device management and automation.
System administrators, homelab enthusiasts, and IT professionals who need to manage and wake devices across a local network without relying on proprietary software.
Developers choose UpSnap for its self-hostable, open-source nature, user-friendly interface, and granular permission system, offering full control over network device management without vendor lock-in.
A simple wake on lan web app written with SvelteKit, Go and PocketBase.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Offers a one-click dashboard for waking devices, replacing manual command-line tools with an intuitive UI, as shown in the screenshots and features list.
Supports cron-based timed events for automating device wake-ups, enabling hands-free management for tasks like backups or maintenance.
Provides per-device access control for multiple users, allowing admins to fine-tune who can wake, edit, or delete devices, demonstrated in the user management screenshots.
Includes 35 visual themes and internationalization for over 20 languages, enhancing accessibility and personalization across global teams.
Built with SvelteKit and Go, it runs via Docker or binaries, keeping full control local and avoiding vendor lock-in, per the philosophy and deployment options.
The README explicitly warns against exposing to the open web due to shutdown commands piping to shell as root, which could lead to unauthorized shell access if compromised.
Network discovery relies on nmap, which must be installed separately, adding setup steps and potential compatibility issues on some systems.
Wake-on-LAN only works on the local network; remote access requires a VPN setup, limiting convenience for users wanting direct internet-based management.
Shutdown commands need manual setup via the Wiki and involve custom shell commands, which can be error-prone and insecure if not properly validated.