Architecture
Last updated:Nov 8, 2026
yunyoo has four parts: the yunyoo platform, the desktop app and web console, local nodes, and cloud phone images.
The yunyoo platform
Accounts, billing, licensing and image distribution live on the platform, and it also manages environments, profiles, backups and migration. Every environment is registered on the platform, whichever node it runs on; an environment's name, tags, star and group are stored only there. The desktop app and the web console both connect to the platform, always over HTTPS.
Desktop app and web console
Both use the same interface. The desktop app adds direct LAN viewing, batch view, device tools, and installing and checking local nodes. The desktop app also needs to stay online; if it can't reach the platform, it locks and asks you to go online.
Local nodes
A local node is the computer your cloud phones run on. Cloud nodes are not available yet.
- Mac: only Macs with Apple silicon and macOS 26 or later. The node service comes with the desktop app, and cloud phones run on the Mac's hardware virtualization.
- Linux: an ARM64 computer, paired and set up with the wizard in the desktop app; cloud phones run in Docker containers.
A cloud phone is a virtual phone running on the node, not a physical phone in a data center. Nodes must stay online and renew their lease with the platform regularly. If renewal fails, the node enters a grace period; when it ends, every cloud phone on the node shuts down normally. Once the node is back online and renews, you can carry on.
Images
Cloud phone system images are downloaded from the platform as encrypted release packages. The node converts them into a copy that only that node can use; copied to another computer, it won't start. Images have an expiry date, and with automatic updates on, the node downloads a new version before it arrives.
Remote viewing
When you view an environment on a local node from the desktop app, with Default node in the top bar set to your local node, and the app is paired with the node and can reach it, the screen goes straight from the node to the desktop app over the LAN; each time you open it, the app still gets a short-lived ticket from the platform first. In every other case, such as viewing in the web console or when the node isn't paired or reachable, the cloud path is used and the platform sets up the connection.
Automation
For desktop automation tasks, the command-line tool, MCP and machine tokens, see Automation overview.
