Edge Runner
Connects outward only. Keeps printing when disconnected. Catches up without duplicates when reconnected.
The dashboard shows all runner groups, their sync status, and print volume. A runner going offline shows a calm amber indicator — no red alarm until something actually fails.
Your plant floor keeps running.
When the network drops (and it will), the Runner keeps printing from its local queue. When the link comes back, it reconciles with idempotency keys — no label prints twice, no label gets lost.
- No firewall rule needed — runners connect outward only
- Offline printing continues without interruption
- Catch-up on reconnect with zero duplicates
- N-2 version policy: you are never forced onto the latest release
One line to install. CSR enrollment. Signed binaries.
# Linux (amd64/arm64) curl -sL https://get.openlabelengine.com/runner | sh -s -- \ --url https://your-center:8090 --group production # Windows (amd64) ole runner join --url https://your-center:8090 --group production
A runner row exists only because a real runner enrolled via CSR. There are no pre-created entries — every runner in the Center was placed there by an actual enrollment event.
| Mechanism | How it works |
|---|---|
| Desired State + Reconcile | Runners pull their configuration; the Center does not push imperative commands except job dispatch, cancel and lease renewal. |
| Idempotency keys | Every print job carries a unique key. On reconnect, each buffered job ID is checked against the archive before reprinting. |
| CSR enrollment | The runner generates a certificate signing request on first connect. The Center issues a client certificate — mutual TLS thereafter. |
| Lease mechanism | Runners hold a time-limited lease. If the lease expires without renewal, the runner is marked offline but its queue persists locally. |
Runner detail: per-printer queue, live log with lease renewal..
Catch-up: 214/312 buffered jobs being processed. Every job ID is checked against the archive — zero duplicates.
The Center controls. The Runner delivers.
The Center controls design and deployment. The Runner holds everything local: queue, buffer, deduplication. Orange = jobs going out. Green = confirmations coming back.