Add a machine
Adding a machine installs prism-service-agent on it and pairs it with your
Prism. A new cloud instance can do this itself from its start configuration
(without a terminal); an existing
machine needs one command in its terminal. You do not need root.
Before you start
Section titled “Before you start”- The model servers run as systemd units on Linux, under one account (for
example
inference). Prism recognizes units that runllama-server,vllm,ollamaorsglang, or any unit whose process answers/v1/modelson a local port. - The model machine can reach Prism’s main address. Use a tailnet address
(
http://100.64.0.10:18000, or the machine’s tailnet DNS name) or an HTTPS address. The agent refuses to pair over plainhttpto any other address, except loopback, because the pairing request carries the agent’s token once.
Add a machine without a terminal
Section titled “Add a machine without a terminal”A new cloud instance can connect itself when it first starts. Nothing secret goes into the instance: no code, key, token or account.
-
In the console open Compute providers, press Add machine, choose On another machine and stay on the When creating an instance tab.
-
Check Prism’s address. Leave Account on the machine empty to install the agent for the machine’s only regular account; enter the account that owns the model servers when the image has several.
-
Copy the text into the instance’s User data field (Nebius: Create virtual machine → User data) when you create it:
#cloud-config# Connects this machine to Prism at http://100.64.0.10:18000. It holds no key or code:# the machine appears in the Prism console and waits for your confirmation.runcmd:- [systemd-run, --unit=prism-join, --collect, sh, -c, "for i in $(seq 2880); do curl -fsSL 'http://100.64.0.10:18000/prism/pair/install.sh' -o /run/prism-join.sh && sh /run/prism-join.sh --prism 'http://100.64.0.10:18000' && exit 0; sleep 30; done"]The text is the same for every machine; keep it for the next one.
-
At first boot the machine installs the agent of your Prism’s version for that account, turns on lingering and asks Prism to connect it. It keeps asking for a day while Prism is not reachable yet, for example before the machine joins your tailnet. Progress is in
journalctl -u prism-joinon the machine. -
The machine appears in Compute providers as Asks to connect, with the address the request came from, the agent version, the model servers it found and its certificate fingerprint. Prism looks it up in your cloud accounts:
- Instance … in account …: the request address … matches — the request came from that instance’s own address;
- Not confirmed, check: … the machine reported that address itself or … the machine reported the name itself — a warning, not a match: the machine says this about itself and nothing proves it. You can still confirm, but only if the machine is yours;
- This machine is not in your cloud accounts — confirm only if you created it.
-
Press Confirm to let Prism manage it, or Reject. Prism calls nothing on the machine before you confirm. Reject removes the request, and Prism refuses that agent’s requests afterwards.
Limits: at most 8 machines can wait for confirmation at once; a request not confirmed within 24 hours is removed. Model servers that run as system services still need the one-time grant described in System services.
Pair the machine
Section titled “Pair the machine”-
In the console open Compute providers and press Add machine.
-
Check This Prism’s address (the agent on the machine connects to it). The console fills it in; this is Prism’s address, not the model machine’s. Press Create command.
-
The console shows one command with a one-time code, valid for 10 minutes:
Terminal window curl -fsSL 'http://100.64.0.10:18000/prism/pair/install.sh' | sh -s -- --prism 'http://100.64.0.10:18000' --code ABCD-EFGH-JKMNRun it on the model machine as the account that owns the model servers, not as root.
-
The script downloads the agent of the same version as your Prism into
~/.local/bin, checks its version, and runsprism-service-agent pair, which:- creates the agent token and a self-signed TLS certificate in
~/.config/prism-service-agent/(files readable only by that account); - finds the model servers of the account;
- sends the token, the certificate fingerprint and the list of servers to Prism with the code;
- installs and starts the user unit
prism-service-agent.service(port 18093 by default).
If user lingering is off,
pairturns it on withloginctl enable-lingerso the agent and the model servers keep running after logout and start at boot. If that is refused, the command prints the commands to run instead (sudo loginctl enable-linger inference, thensystemctl --user enable --now prism-service-agent.service). - creates the agent token and a self-signed TLS certificate in
-
Back in the console the machine shows Waiting for confirmation. Prism calls nothing on the machine until you press Confirm.
-
After confirmation Prism lists the model servers the agent found. Tick the ones Prism should manage. Each ticked server becomes a model service and an AI provider whose model appears in
/v1/models. Open its settings to set the start timeout and start on request.
If the agent found nothing, start a model server or check its unit, then press Find servers again.
Common problems
Section titled “Common problems”| Message | Cause | Fix |
|---|---|---|
| The command expired. Create a new one. | The code is older than 10 minutes or was used | Press Create command again |
| systemctl –user did not answer for inference. Run: sudo loginctl enable-linger inference | The account has no running user manager | Run the command shown, then Find servers again |
| Listens only on 127.0.0.1: Prism on another machine cannot reach it. | The model server binds loopback and Prism runs elsewhere | Bind the server to 0.0.0.0 or to the machine’s tailnet address |
| Choose the model: the server lists several, and Prism routes one model per service. | The server serves several models | Pick one in Model |
What is stored where
Section titled “What is stored where”- On the model machine: the agent token, TLS key and certificate, the agent
configuration and the list of allowed units, all in
~/.config/prism-service-agent/. - In Prism: the machine (host name, agent address, certificate fingerprint, discovered units) and the managed services in its state database; the agent token in Prism’s encrypted vault.
Remove a machine
Section titled “Remove a machine”Press Remove on the machine in Compute providers. Prism deletes its copy of the agent token. On the machine, run:
systemctl --user disable --now prism-service-agent.servicerm -rf ~/.config/prism-service-agentModel servers that run as system services
Section titled “Model servers that run as system services”A model server that runs as a system service (systemctl --system), possibly
under another account, needs a one-time grant on the machine. See
System services.