Self-hosting
Keep your code, the engine, the signer and the runners on your own machine; land's cloud keeps only accounts, billing and metadata.
Download
One bundle holds everything a plane runs: land's server build (the data plane, queue, runner and signer), sem, the recorder, and the runner bundle (the guest kernel, its init and the base disk). Each land release publishes a new one.
V=$(curl -fsS https://useland.dev/releases/plane/latest) curl -fsSLO https://useland.dev/releases/plane/$V/land-plane-$V-x86_64-linux.tar.gz curl -fsSL https://useland.dev/releases/plane/$V/SHA256SUMS | sha256sum -c - tar -xzf land-plane-$V-x86_64-linux.tar.gz sudo ./land-plane-$V/install.sh # /opt/land: the engine, sem, the recorder, land-flow; /opt/land-runner: the runner bundle
What runs where
A team whose code must never leave its own machines keeps everything that touches code on a machine of its own, the data plane. land's cloud, the control plane, keeps only accounts, billing and metadata. It knows who you are and where your plane is; it cannot read, merge or sign anything of yours.
your machine: the data plane the repository (git pushes and fetches) the engine: merge, plan, verdicts the signer and its private key your queue and runners (the checks) the repository's secrets │ │ dials out over HTTPS (nothing dials in) ▼ land's cloud: the control plane accounts, sign-in, API keys, billing the plane's token (as a hash), its address, its public keys the metadata the plane sends up (names, counts, seconds)
Requirements
- Linux x86_64 with glibc 2.39 or later (Ubuntu 24.04 works; Debian 12 doesn't), git, and root.
- For the runners: KVM (on a cloud VM, nested virtualization), cgroup v2 and iptables. Each check runs in its own microVM.
- The plane reachable by your developers and agents over HTTPS at its public address, and able to reach api.useland.dev over HTTPS. Nothing needs to reach it from land's cloud.
- A land account, signed in on the dashboard with GitHub.
Set it up
- Make three system users, one each for the plane, the engine and the signer, and make the plane token with
land plane create --token-file /etc/land/plane-token: it prints a link and a code, the account's owner approves it in the browser, and the token is written to the file (never shown, never overwritten). Or make it on the dashboard: Self-hosted, then Make a plane token.
land plane create --token-file /etc/land/plane-token # prints a link and a code; approve it, the token lands in the file useradd --system --shell /usr/sbin/nologin land-plane # the data plane process useradd --system --shell /usr/sbin/nologin land-engine # the engine, git and hooks useradd --system --shell /usr/sbin/nologin land-signer # holds the signing key install -d -m 711 /etc/land chgrp land-plane /etc/land/plane-token && chmod 640 /etc/land/plane-token
- Make the signer's key. It never leaves the machine; the plane sends only the public half up.
land server signer keygen --out /etc/land/signer.key > /etc/land/keys.json chown land-signer /etc/land/signer.key # as land-signer: land server signer --key /etc/land/signer.key --socket /run/land/signer.sock
- Start the data plane. It says hello to land's cloud, then serves git and the engine for your repositories.
# as land-plane, with TLS in front of --listen: LAND_HOME=/var/lib/land LAND_KEYSET_PATH=/etc/land/keys.json \ LAND_SIGNER_SOCK=/run/land/signer.sock LAND_ENGINE_USER=land-engine \ LAND_RS_BIN=/opt/land/land-flow LAND_SEM=/opt/land/sem LAND_UCHECK=/opt/land/ucheck \ land server data-plane --control https://api.useland.dev \ --token-file /etc/land/plane-token --listen 127.0.0.1:9419 \ --public-url https://git.example.com
- Start your queue and runners on the same machine. The runners hold passes from your queue, not land's.
# as land-engine, on the same machine land server queue --spool /var/lib/land/remote-spool --listen 127.0.0.1:9423 --token-file /etc/land-queue/secret land server scale --mint rack-1-install --repo $H --role install --token-file /etc/land-queue/secret > install.pass land server scale --mint rack-1-check --repo $H --role check --token-file /etc/land-queue/secret > check.pass # then one runner of each role per repository (land server runner --queue http://127.0.0.1:9423 ...)
- Put each repository on your plane with its first add, from the CLI or the dashboard (Self-hosted, then Put on plane). Every land merge, push and GitHub App job for it then goes to your plane.
land plane list # your planes and their ids land add --plane pl3f9c… # from a checkout: on your plane first, then the add goes there
- Pin your plane's key. Whoever trusts your main verifies it against your plane's keys, not land's.
curl -fsS https://api.useland.dev/v1/land/repos/OWNER/REPO/keys -o land-keys.json land verify HEAD --pubkey land-keys.json --repo OWNER/REPO
To take a repository off its plane, land plane rm --repo OWNER/NAME; to delete a plane, land plane rm ID.
Secrets and runner passes are served by your plane too: land secret set follows land's redirect to it, and the value never reaches land's cloud.
What land's cloud stores
- Stored in land's cloud
- Ids and tree ids, branch and test names, the names of changed files and functions, counts and seconds, verdict and refusal classes (conflict, tests, env, timeout, oom), the agent that pushed a branch, and the signing key's id.
- Never sent to land's cloud
- File contents, diffs, conflict regions, a failing test's output, a test's command, your signing key and your secrets.