- Docs
- Studio
- Remote devices
- Server requirements
Server requirements
Linux on x86_64 or ARM64, a regular user with systemd user services, curl and a SHA-256 tool, outbound HTTPS, and git for repositories.
Where in StudioServer terminal (SSH)
Updated View as markdown
The server installer runs on Linux on x86_64 or ARM64 (aarch64). It needs no root access for Studio itself, and it sets Studio up as a background service of the user who runs it. On macOS the installer stops and points to the desktop app; any other system is refused.
Must have
| Requirement | Why |
|---|---|
| Linux, x86_64 or ARM64 | The two Linux builds Studio publishes. |
curl and tar | The installer downloads and unpacks each file. |
sha256sum or shasum | The Studio package and the Codex, Claude Code and Devin CLIs are checked against SHA-256 values pinned in the installer. Without either tool the installer refuses to install them. |
A regular user account with systemd user services (systemctl --user) | Studio runs as the user service kelrova, which starts at boot and restarts after a failure. Without systemd the installer still installs, and you start Studio yourself with kelrova headless. |
| An interactive terminal for sign-in | Signing in during the install prints a link and reads a code you paste back. Over SSH, use a session with a terminal (ssh -t); without one the installer skips sign-in and Studio starts local-only. |
| Outbound HTTPS | See Network access. |
Run the installer as the Linux user who should own the projects. If you became root with sudo su, the user service may not find its session; log in over SSH as that user instead. A direct root login works.
Strongly recommended
- git, to work with repositories. The installer prints a note when it is missing.
- Permission to keep the service running after you log out. The installer enables this with
loginctl enable-linger, usingsudoif it can do so without a password prompt. If it cannot, it prints the command to run; until then Studio stops when you log out and does not start after a reboot.
Optional: a browser for the agent
The browser tools need Google Chrome or Chromium on the server. The installer finds an existing install in the usual places. To have it install Google Chrome when none is found, add --with-chrome:
curl -fsSL https://studio.kelrova.com/install.sh | sh -s -- --with-chrome
- The automatic Chrome install uses
apt-getand Google's package repository, which serves x86_64 only. On ARM64, install Chromium with your package manager, then run the installer again. - Chromium installed as a snap package is not supported.
- When Studio runs as root, Chrome starts without its sandbox.
The browser panel covers watching the server's browser from your Mac.
Network access
The server reaches these hosts over HTTPS during the install:
| Host | For |
|---|---|
studio.kelrova.com | The installer and the Studio package |
github.com | The Codex CLI |
downloads.claude.ai | The Claude Code CLI |
static.devin.ai | The Devin CLI |
nodejs.org | Node.js 22, when no recent enough Node.js is installed |
| The npm registry | The Cursor SDK |
dl.google.com | Google Chrome, only with --with-chrome |
After the install, Studio needs outbound HTTPS to Kelrova to sync and to receive updates. It needs no open inbound port: your Mac reaches the server through your Kelrova account, not by connecting to the server directly.