Your own server
Run Soba on a VPS, a cloud VM or a box in a cupboard, over SSH. One line installs the worker and one command pairs it and keeps it running.
A laptop closes its lid. A server you run yourself doesn't, so your runs keep going when
your laptop is asleep. Everything here happens over SSH. The server needs no screen and
no browser.
Install#
Terminal
curl -fsSL https://soba.so/download/install.sh | sh
This picks the right build for the machine (Linux or macOS, x64 or arm64) and puts
soba-worker in ~/.local/bin, or in /usr/local/bin when run as root. On Windows,
use the Soba app instead: there is no Windows service.
Connect it to an app#
Use the connect link the app gives you:
Terminal
soba-worker login --no-browser --install --broker https://soba.so/c/pk_soba_<connect key>
It prints a link and a code. Open the link on any device, check that the code matches,
and approve. With --install, the worker then installs itself as a service (systemd on
Linux, launchd on macOS), restarts after a reboot, and marks the machine always on.
You can install and connect in one go by passing the same flags to the installer:
Terminal
curl -fsSL https://soba.so/download/install.sh | sh -s -- --broker https://soba.so/c/pk_soba_<connect key>
On Linux, enable lingering#
A per-user service stops when you log out, which on a server is the moment you close the
SSH session. install checks and prints the command:
Terminal
sudo loginctl enable-linger $USER
Or install a system unit with soba-worker install --system.
Check on it#
Terminal
soba-worker service-status
soba-worker --status # what it offers, and whether the service is up
What it can run#
Whatever is signed in on the server:
- Claude Code or Codex, signed in to your own plan. Run
claude or codex once on
the server to sign in.
- Local models through Ollama, vLLM or anything OpenAI-compatible, or a hosted
endpoint on your own key. See Adding an endpoint; keys go in
~/.soba/service.env, never in the service definition.
Is this allowed?#
Yes. Your own server serving your own runs is the same as your own laptop serving them.
What is not allowed is one account serving many people's runs. See
Provider terms.
For how the service is set up, and what breaks it, see
Keeping it running.