Install on your own server

Create the environment and get a token

Hub: open hub.codai.ro/projects, create a project, then New environment → Bring your own machine. On the environment page choose Generate enrol token; the token is single-use and valid for 30 minutes, and the page shows the exact install command.

CLI: with CODAI_API_KEY set (or a key in ~/.codai/codaid.json):

codaid env create --project my-app --name dev-box
# prints the environment and:
#   curl -fsSL https://codai.ro/install-codaid.sh | CODAI_ENROLL_TOKEN=codai_env_… sh

API: POST /v1/environments with "provider": "byo", then POST /v1/environments/{id}/enroll-token — see the API page.

Install and enrol (Linux)

Run on the machine, as a user with sudo:

curl -fsSL https://github.com/codai-ro/codaid/releases/latest/download/install.sh \
  | CODAI_ENROLL_TOKEN=codai_env_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX sh

The installer downloads the binary for your architecture to /usr/local/bin/codaid (verifying the published .sha256), runs codaid enroll, and — when systemd is running — installs and starts codaid.service for the invoking user. It needs curl or wget.

Because a BYO environment carries no API key of its own, codaid enroll then starts a device-code sign-in: it prints a URL and a code, you approve it in the browser on any device, and the daemon stores the resulting key. Pass CODAI_API_KEY=codai_… to skip that step (useful for fleets).

The same script is mirrored at https://codai.ro/install-codaid.sh; the GitHub release URL is always the newest.

Or enrol by hand

codaid enroll --token codai_env_… [--api-key codai_…] [--workspace /srv/app]
codaid run            # foreground; Ctrl-C stops it
codaid status         # JSON: config (key redacted), workspace, git, listening ports, identity, locks

enroll writes ~/.codai/codaid.json (directory 0700, file 0600) with the device id, API key, environment id and relay URL. Re-enrolling keeps the same device id. The key is never printed — status shows only its prefix and length.

On Windows, download codaid-windows-x86_64.exe, then run codaid enroll --token … and codaid run in a terminal. Shell commands execute in PowerShell. There is no Windows service yet.

Run as a service

# unit for your own user (what the installer does)
codaid install-service --user "$USER" | sudo tee /etc/systemd/system/codaid.service
sudo systemctl daemon-reload && sudo systemctl enable --now codaid

# system unit (root): per-member Linux accounts, shared repos, per-repo build lock
sudo codaid install-service --system [--identity per-user|shared] [--user codai] [--home /var/lib/codai]

--system must run as root on Linux with systemd; it creates the service user and, in per-user mode, the codai-dev group plus /srv/codai/repos and /var/lib/codai/locks. If the machine is not enrolled yet it prints the sudo CODAI_HOME=/var/lib/codai/.codai codaid enroll … command to run next. The unit restarts on failure every 5 s.

Check it is online

codaid env status dev-box      # online=true, daemon version, ports, git branch

The hub shows Daemon connected, and the desktop Environments view shows a green dot. The daemon sends a heartbeat every 15 s and reconnects with back-off (1 s → 30 s) whenever the socket drops; the relay closes every WebSocket after one hour and the daemon reconnects immediately.