s1, s2, m, l, xl, 2xl, 3xl), that sleeps when you are not using it and wakes when a run needs it. It is billed through a compute plan. See Cloud machines & plans.

Settings → Machines, with a cloud machine running. Example data.
When to use which
Choose your own computer for a chat when the project is already checked out there, when it needs hardware or network access only that computer has, or when you want the work to happen next to your editor. Choose a cloud machine when you want runs to keep going while your laptop is closed, when you want to start work from the web or your phone, or when an automation has to fire at 3 a.m. on a schedule. You can have both and run different chats on different machines.What lives on the machine
Because the daemon is the thing that reads your files, several pieces of configuration belong to the machine rather than to your account:- Your project files and git history, including any workspaces.
- Memory files:
~/.reliant/reliant.mdis the one on that machine, so a cloud machine has its own, separate from your laptop’s. - MCP servers. They are started by the daemon, so a server that needs
npxoruvxneeds it installed on the machine that runs it. - Model configuration and any local models.
Which machine a chat runs on
A project is not tied to one machine. You can install the same project on several machines, for example your laptop and a cloud machine, and each has its own checkout, git history and workspaces. What decides where work happens is the chat. Each chat runs on one machine. On the new-chat screen the machine picker shows where it will run, starting from your default machine, and you can choose another machine you own, or No machine. A chat with no machine can use the web and your integrations but cannot read or change files, run a shell or reach a local MCP server. If you leave the machine unchosen, the chat runs on your default machine. You can change a chat’s machine later with Connect a machine, which is also how a no-machine chat gets one. A branched chat is the exception to choosing freely. Its workspace lives on the disk of the machine that created it, so the branch runs on that machine. A new workspace is created on the machine of the chat it is created for, and the Files tab and the file, workspace and git operations for a chat all go to that chat’s machine. A workspace you create from the new-chat screen, before the chat exists, is created on your default machine.Your default machine
Your default machine is the one new chats start on when you leave the machine unchosen, and the one a workspace created from the new-chat screen goes to. To choose it, open Settings → Machines and click Make default on the machine; a Default badge marks it. You can also hover a machine in the new-chat machine picker and click Make default. The default applies whatever state the machine is in: if it is asleep, the chat wakes it rather than going to another machine that happens to be awake. Changing the default does not move chats that already run on a machine. If you have not chosen a default, or you delete the machine that was your default, Reliant picks one for you: a machine that is connected, your own computer before a cloud machine, otherwise one that is starting or asleep. A project installed on only some of your machines always runs on one of those, so a chat never starts on a machine that does not have the project. Automations pick their own machine when you enable them, independently of your chats. That is how a scheduled job can use a cloud machine that is awake at 3 a.m. while you work interactively on your laptop. A workflow can also pin a machine itself withdaemon:. The rules are in Choosing a machine in workflows.

A cloud machine running a chat. Example data.
Related topics
- Your own computer: install, register and run a daemon.
- Cloud machines & plans: sizes, hours, waking and suspending.
- Choosing a machine in workflows: the
daemon:field and selection order. - Billing, wallet & Reliant AI