Field service technician
Needs a remote expert to see exactly what is in front of them, from a phone, in a building with unreliable connectivity.
Manufacturing & field service
Send the expert's eyes, not the expert.
A specialist walking a technician through a fault needs to see the part, not guess from a blurry phone share. 4K Chat gives small field teams a browser-first room for the technician's phone, USB camera, or capture-card feed, at the resolution both ends can actually deliver.
- 21 days
- Offline licence grace period, so a bad site link never blocks a job.
- Both ends
- Resolution follows the camera, hardware, and network at the site and the expert's location; 4K or 8K is not guaranteed.
- 0
- Media servers between the plant floor and the remote expert.
- Long sessions
- Designed for extended review sessions, without an uptime or resolution guarantee.
Who this is for
Remote support engineer / OEM specialist
Wants the line camera, the inspection camera, and the technician's phone in one view rather than one shaky feed at a time.
Plant / maintenance manager
Cares that nothing about the process leaves the site and that downtime calls start in seconds, not after a licence check.
What a bad remote-support call costs
- A missed detail turns a phone call into a flight and a day of downtime.
- Plant networks are locked down, and cloud video services are often simply blocked.
- Fixed line cameras and handheld video live in entirely separate systems.
Where normal conferencing breaks
- A screen share of a camera feed can hide the small detail the specialist needs to judge.
- Compressed video hides hairline cracks, wear patterns, and small displays.
- Nothing keeps working when the site connection is intermittent or the app can't phone home.
What 4K Chat brings to it
Line and inspection cameras in the room
Capture cards and device cameras join as their own participants today; WHEP, HLS, MJPEG, and RTSP-via-local-bridge feeds are coming.
How it works →Technician on a phone
The technician joins from a phone browser today and points the device camera at the fault. Native apps are in development.
How it works →Use the uplink where detail matters
Keep the essential inspection angle prominent and test the actual received picture; performance follows the devices and networks on both ends.
Approved sources only
The host — or a delegate on site — decides which cameras are admitted, enforced at both ends of every connection.
How it works →Minimal dependence on us
Signed offline entitlements keep paid features working through connectivity gaps; only kilobytes of signaling ever reach our backend.
Recovers from bad links
ICE restarts, media watchdogs, and unbounded retries keep a session alive across network changes on a plant floor.
How it works →Setting up a session
- 1
Technician opens a room
From a phone browser today — one tap, no account needed. Native apps are in development.
- 2
Pull in the fixed cameras
Add capture-card feeds as camera participants today; RTSP bridging through a bridge that stays inside the plant network is coming.
- 3
Bring in the specialist
Send the link. They arrange the tiles they need and pin the angle that matters.
- 4
Capture the evidence on Pro or Cinema
Local recording is a Pro and Cinema feature, not a Free feature. The WebM file stays on the recording participant's device.
Gear that works
Technician phones and tablets
Join from a link as a normal participant; mobile mode caps sensibly to protect battery and data while keeping detail where it matters.
Fixed line and inspection cameras (coming)
WHEP directly, or RTSP through the local bridge, once IP camera bridging lands. Each one becomes a host-approved participant with its own tile.
Borescopes and USB microscopes
Anything the OS exposes as a camera can be added as a separate high-detail angle.
Rugged laptops and industrial panels
The PWA installs locally and runs without depending on our site, which matters on segregated OT networks.
Will this actually work for us?
Our plant network is locked down. Will it connect?
Free has no TURN relay, so hard NAT and restrictive plant networks may fail. Test the actual site network before the job, try a hotspot or wired alternative, and compare a customer-operated bring-your-own relay on a paid plan if direct connection is blocked.
What if the site has no internet at the moment of the call?
Licensing is a signed offline entitlement with a 21-day grace window, and the app is installed locally, so a same-site call between two devices works with no dependency on our infrastructure.
Can we stop random devices joining as cameras?
Yes. A camera publishes nothing until the host or an appointed delegate approves it, and revoking approval kills the feed at both the publisher and every receiver.
Is process footage stored anywhere?
Only if a Pro or Cinema participant records locally. There is no cloud recording and no media server that ever holds a frame. 4K Chat is not for emergency or life-safety use.
Questions we get
Does anything have to be installed on the plant network?
No — capture cards and device cameras work from the browser directly. When IP camera bridging lands, WHEP, HLS, and MJPEG will work from the browser too, and RTSP cameras will need a small bridge on your own network.
What if the site loses connectivity mid-call?
The call attempts recovery for as long as it's open, and signed offline entitlements mean paid features don't lapse the moment our backend is unreachable.
How many people or cameras fit, and will Free connect?
Free holds up to 4 participants, Pro up to 12, and Cinema up to 32; every extra camera counts as a participant. Free has no TURN relay, so a hard-NAT or locked plant network may fail to connect.
Keep reading
Recommended plan: Pro or Cinema
Pro suits a technician-plus-expert call with one fixed camera; Cinema covers full inspection teams with several feeds.