See what they see, without paying per minute.

A field technician opens a link and starts their phone camera. An expert watches live, and the session survives a dropped signal. One Go binary you run on your own server — no per-minute vendor sitting in your media path.

Open the live demo → Run the camera-free self-test

No account, no signup and no card to try it. Deploy files for systemd, Caddy and docker-compose ship with the source.

Remote support still runs on phone calls and screenshots

Someone describes a fault down a phone line while a specialist guesses. The tools that fix this — SightCall, Blitzz, Help Lightning and the general-purpose video APIs — bill per participant-minute and sit inside your media path. At low volume that is a rounding error. At a few hundred sessions a month it is a line item, and when it breaks you are debugging a black box you do not control.

What is actually hard here is not the video. It is the phone that changes network mid-session, the technician behind a carrier NAT that no peer-to-peer candidate can reach, and a server on a cloud VM whose real public address nobody told it about. Those are the failures this kit was built and hardened around — not demoed around.

Each of those four failure modes is written up symptom first in the field-assist networking guide.

Three steps, one binary

What is in the box

• Signaling + SFU — Go (Pion v4), a single binary with in-memory room state. No Redis, no database, no Kubernetes.
• Publisher — browser camera and screen share over a shareable link; plain ES modules, no bundler.
• Viewer — autoplay handling, auto-reconnect (ICE restart first, full rejoin as fallback, jittered backoff), freeze detection.
• Diagnostics — connection and ICE state, bitrate in/out, resolution, FPS, packets lost, jitter, jitter buffer, round-trip time, freeze count, the selected candidate path, and plain-English hints.
• NAT traversal — coturn configuration and -turn flags, for symmetric NAT and phones on cellular.
• Deploy — systemd unit, Caddyfile, Dockerfile and docker-compose.
• Docs — docs/pitfalls.md: nine real traps, symptom to cause to fix.
• Proof — a camera-free self-test page and a public relay test page.
• Delivery — source code, one-time payment, no per-minute fee.

What you are not buying

Source code and documentation. Not remote installation, not production operations or on-call support, not custom development. No RTSP camera ingestion, no recording or retention, no transcoding or broadcast, no native mobile app. If you need any of those, they belong in a separate paid agreement — say so and we will scope it.

Built for teams that ship this into a client project

• Software agencies building custom WebRTC, video, IoT or field-service products, who would rather spend the weeks elsewhere.
• Systems integrators who need to add remote visual support to a client system without adding a per-minute vendor.
• Equipment vendors and inspection teams who want their own branded tool on their own infrastructure.

Try it before you pay anything

• /viewer/ — the operator side of a live session, no account.
• /publisher/ — the camera / screen-share side.
• /test/v2/ — the full canvas-to-playback path, no camera required.
• /test/turn/ — proves the TURN relay actually allocates on the public server.

Buy the source once. Run it as long as you want.

One-time payment, no per-minute fee, no seat in your media path. Same three tiers as the base kit — the source is the same, the positioning is what differs.

7-day refund, no questions asked. Payment, tax and invoicing are handled by our merchant of record, and the source archive downloads immediately after payment.

Source license only. Deployment, environment debugging and custom development are not included.

Questions

Is this a hosted service?
No. You get source code and deploy docs, and you run it on your own server. Nothing of yours passes through us after the download.

Will you deploy it for me?
No. Deployment, environment debugging and custom development are not part of the purchase. The deploy docs and docs/pitfalls.md make it a self-serve job for one developer.

Does it work on a phone over cellular?
Yes, when TURN is configured. The kit ships the coturn config and the -turn flags, and the relay test page proves the relay allocates on our own server so you can prove the same on yours.

What happens when the signal drops?
The viewer tries an ICE restart first, then a full rejoin, with jittered backoff. The diagnostics panel shows which stage it is in.

Can two experts watch at once?
Not in this release. Multiple viewers per room work; inviting a second expert as a first-class flow is roadmap.

Can I white-label it?
The licence allows commercial use and the pages are plain HTML/CSS/JS you can restyle. A built-in white-label entry flow (logo, colours, domain, copy) is roadmap, not shipped.

What is it not good for?
Long-lived monitoring walls, recording and retention, RTSP camera ingest, and broadcast-scale distribution. It forwards; it does not mix or record.

Source code, one binary, no per-minute bill.

Open the live demo, run the self-test, read the pitfalls doc — all free and without an account. If it fits a project on your desk, the source is one payment away.

Open the live demo → See pricing

Questions before you buy? Email support@lowlatencykit.com — I answer every one, usually within a day.