How we keep the hosting panel lightweight
The engineering decisions behind a hosting panel that idles in megabytes, not gigabytes: single binary, SQLite, no background bloat.
By Engineering
The Vorqul hosting panel stays lightweight through three decisions: it ships as a single self-contained binary, it uses embedded storage instead of a database server, and it refuses to run background work that nobody asked for.
One binary, one process
Most panels arrive as a constellation: a web server, an application runtime, a database, a message queue, a handful of workers. Each piece needs configuration, updates and memory. Vorqul compiles everything into one deployable file. Installation is copying a file and starting a service; updating is replacing that file.
Embedded storage
A panel's data - users, servers, schedules, audit logs - is small and mostly read. An embedded database handles it with zero administration and no separate process. Backups become a file copy, and there is no database server to patch, tune or accidentally expose to the network.
No idle work
Monitoring polls only what a dashboard is actually watching. Scheduled jobs wake up, run and go back to sleep. The result is a panel that idles at a fraction of the memory of the usual suspects, which matters when the same machine also has to run the game servers you bought it for.
The trade-offs, honestly
This design targets single-node and small-fleet deployments - the overwhelming majority of real-world use. If you operate hundreds of nodes with a dedicated infrastructure team, a heavier distributed panel may serve you better, and that is fine. We build for the setup most people actually have.