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 Yamiru
The Vorqul hosting panel stays small because of three decisions. It ships as one self-contained binary, it stores its data in an embedded database, and it refuses to run background work nobody asked for.
One binary, one process
Most panels arrive as a whole constellation: a web server, an application runtime, a database, a message queue and a handful of workers. Each piece wants configuration, updates and memory. Vorqul compiles everything into one deployable file. To install it you copy a file and start a service, and to update it you replace that file.
Embedded storage
A panel's data is small and mostly read: users, servers, schedules, audit logs. An embedded database handles that with zero administration and no extra process. Backups become a file copy. There is no database server to patch, tune or expose to the network by accident.
No idle work
Monitoring polls only what a dashboard is actually watching. Scheduled jobs wake up, run, and go back to sleep. The panel ends up idling at a fraction of the memory the usual suspects use, and that matters when the same machine also runs the game servers you bought it for.
The trade-offs
This design aims at single-node and small-fleet deployments, which covers most real-world setups. Run hundreds of nodes with a dedicated infrastructure team and a heavier distributed panel will probably serve you better. That is fine. I build for the setup most people actually have.