How the connection works

The tunnel listens only on the server’s loopback interface. Relay connects back through it using the SSH key you upload. Commands run as the device user you choose.

One outbound connection. A URL for every device.

Download and run the Linux agent with an enrollment code. It appears here automatically. Set a target such as https://192.168.101.99:8080; requests to its public domain keep their path, query, method, and body.

Device URLs are public. Target HTTPS certificates are not verified, so self-signed local services work. The connection to Relay always uses verified TLS.

1. Find your device

curl -u 'USERNAME:PASSWORD' https://re.eldento.com/api/devices

2. Submit a command

Returns HTTP 202 immediately, with a job ID and status URL.

{"id":"JOB_ID","status":"queued","status_url":"/api/jobs/JOB_ID"}

3. Retrieve status and output

curl -u 'USERNAME:PASSWORD' \
  https://re.eldento.com/api/jobs/JOB_ID

The response includes status, stdout, stderr, exit_code, timestamps, and any connection error. Output updates while the command runs.

Optional: set a deadline

Statuses: queued, running, succeeded, failed, timed_out, interrupted. A failed command preserves its exit code. A lost connection may leave a remote process running; Relay never automatically retries a running command.

Four jobs run concurrently. Up to 100 jobs may be queued or running. Each output stream retains its first 4 MiB; truncated indicates additional output was discarded. Deadlines close the SSH channel and do not guarantee that remote descendants terminate.