design
Every Roomler documentation page tagged “design”.
Architecture
How Roomler is put together — one control plane, three data planes, one agent per machine, and a server that coordinates without ever carrying your traffic.
ArchitectureSystem overview
The pieces of a Roomler deployment — agent, CLI, server and browser — and how a remote session travels through them without the server carrying it.
ArchitectureThe agent
What roomlerd actually is, why it is a single process rather than several, how it runs on each OS, and how it keeps itself updated safely.
ArchitectureThe connection cascade
How two machines choose a path — measured rather than guessed, never ratcheting down, and with a floor over TLS 443 that always connects.
ArchitectureWhat the server sees
Precisely what the Roomler control plane can and cannot observe — including the one feature that is deliberately an exception to the rule.
ArchitectureSecurity model
What is encrypted, what the server can see, where trust sits, and which properties are structural rather than promised.
Security & access control