Why this becomes a problem
Many QEMU web UI searches come from operators who have outgrown SSH scripts but do not want a full cluster platform. The danger is replacing a transparent command with a dashboard that accepts arbitrary shell input or stores powerful credentials without a clear trust model.
How VMBook approaches it
Every VMBook service exposes its machine model over TLS 1.3 on port 3333. The browser uses defined operations, bearer or session authentication and a pinned host certificate. The remote computer composes its own command; callers cannot submit an arbitrary QEMU command for execution.
Recommended workflow
- Run the service under a dedicated account.
- Verify the certificate fingerprint out of band.
- Restrict port 3333 to a management network or VPN.
- Test token rotation, browser logout and behavior during a disconnected site.
Limits and checks
Version 0.1 does not claim enterprise SSO, delegated roles or high-availability control-plane behavior. Those requirements may justify an established cluster management product.
Primary documentation
Frequently asked questions
What problem does this guide solve?
A useful QEMU web interface must do more than start a process: it should identify the host, expose machine state, protect lifecycle actions, show the command source and remain safe when the browser closes.
How does VMBook help?
Every VMBook service exposes its machine model over TLS 1.3 on port 3333. The browser uses defined operations, bearer or session authentication and a pinned host certificate. The remote computer composes its own command; callers cannot submit an arbitrary QEMU command for execution.
What should I verify before using it?
Version 0.1 does not claim enterprise SSO, delegated roles or high-availability control-plane behavior. Those requirements may justify an established cluster management product.

