Live camera video, remote desktop, file transfer, telemetry, and a remote terminal to every robot in your fleet — over WebRTC, embedded inyour robot, your backend, and your dashboard.
Open-core (AGPL-3.0) libraries you self-host, plus a managed cloud when you'd rather not. Fjärr is Swedish for "remote".
Read the docsWhy Fjarr existsEmbed libfjarr (C++/GStreamer) into your robot software — or run the fjarr-agent daemon beside it. Hardware H.264 encode, one encoder for any number of viewers.
Deploy the fjarr-server sidecar (78 MB container) next to your existing stack — any language. Your backend mints session grants and receives webhooks. It never touches the media path.
@fjarr/core + @fjarr/react drop robot sessions into the React dashboard you already have. Headless-first components, your design system wins.
Multi-camera live streams, one encode fanned out to every viewer, adaptive bitrate.
The robot's Ubuntu desktop in your dashboard — unattended access after reboot included.
Typed telemetry with change-triggered updates and offline store-and-forward.
Resumable, backpressured transfers — a 4 GB log dump over LTE that survives reconnects.
An audited PTY in the browser, over the same session.
Versions, host metrics, error rates across the fleet.
SWUpdate-based A/B updates with rollback and streamed binary diffs.
Statuses track the public roadmap — we don't market what doesn't run.
| Free & open (AGPL-3.0) | All three libraries, the signaling sidecar, the protocol, the docs, the demos. Genuinely usable alone, self-hosted forever. |
| Fjarr Cloud | Managed signaling + TURN, fleet observability, staged OTA campaigns, SSO — metered by robots, session-minutes, and relay bandwidth. Same contract as self-hosting: switch either way, no rework. |
The whole business plan is a public document: product strategy.