Local nodes
Last updated:Nov 8, 2026
A local node is the computer your cloud phones run on: your Mac, or a Linux computer. Cloud nodes are not available yet, so for now every cloud phone runs on a local node. Nodes are managed by yunyoo and must stay online.
Mac
- You need Apple silicon and macOS 26 or later.
- The node service comes with the desktop app; there is nothing else to download. The first time you open the desktop app, it checks the processor, system version, hardware virtualization, memory and disk space, and sets up the local node for you if everything passes. Any check that fails tells you what to do. You can skip this for now and start again later from the Nodes page.
- macOS may say a background item was added. Keep it allowed, otherwise the node goes offline.
Linux
On the Nodes page in the desktop app, open LAN nodes and click Add Linux machine. The wizard has four steps:
- Find: install the node helper on that computer. The wizard gives you an installer and an install command. Once installed, the computer shows up in the list.
- Pair: run the command the wizard shows on that computer and enter the six-digit pairing code it prints.
- Check: the items in the table below are checked. Fixes that need root are shown to you for confirmation first.
- Install: the node service is installed and registered with yunyoo.
| Item | Requirement |
|---|---|
| System | ARM64, with systemd and apt |
| Virtualization | Hardware virtualization, with read and write access to /dev/kvm |
| Graphics | A usable render device |
| Docker | Installed, with the node user in the docker group |
| Always on | The node service keeps running after the node user logs out |
| Network | Can reach yunyoo; desktop apps on the same local network can reach this computer |
| Time | Automatic time sync is on, and the clock is within 2 minutes of the correct time |
If the docker group or always-on items are not met, the wizard can fix them for you. Later updates, restarts and removal of the node service are also done from the desktop app.
Images
The node downloads and prepares the cloud phone system image itself. The first time takes a while. Images have an expiry date. With Update automatically turned on, the node downloads a new version before the current one expires; once the new version is ready, old versions that no environment uses are removed. If an old version that environments still use is about to expire, the desktop app reminds you to deal with it. Expiry dates, download progress and what can be cleaned up are on the Images tab of the Nodes page.
How many can run at once
The Nodes page suggests how many cloud phones to run at the same time, based on this computer's memory, CPU and disk. Slots are taken per environment, whether it is running or not; the suggestion only concerns how many run at the same time. You can also set a run limit for the node. Once it is reached, further starts are refused.
When the node loses its connection
When the node cannot renew its lease, for example because the network is down, it enters a grace period: cloud phones that are already running keep running, but new ones cannot start. When the grace period ends, every cloud phone on the node shuts down normally. Once the network is back and the lease is renewed, you can carry on. Environment data stays on this computer the whole time.
Uninstall a node
- Mac: click Uninstall on the Nodes page. Every cloud phone on the node is stopped first, then the node service is removed. You can also choose to delete the node's data and credentials. If some environments have data that has not been synced to the cloud, you are warned first, because that data may be lost.
- Linux: in LAN nodes, choose Uninstall node service for the machine. Every cloud phone on it stops, and the node service is removed together with its data and credentials. The node helper stays, so you can add the machine again later.
