Before
Set up
Node goes in the rack on site. Operators sign in to REMI and see every node their tenant owns, then assign each one a task.
Node · Producer · Delivery
How it works
Hardware on site, control in the browser, the edit already running. Click through the chain — each step updates the detail panel below. LGL REMI sits above the chain rather than in it.
Selected step
Node: the hardware that stays on site
Node is one piece of hardware that takes one role at a time: scope, encoder, audio monitor, or switcher control. Rack as many as the show needs and assign each one from LGL REMI.
Open Node →One production, start to finish
Live
Show
REMI drives the on-site switcher, cameras, scopes, and audio from the browser. Node moves every frame off site while the show runs.
Minutes later
Turnaround
Producer already has the material. The team cuts and delivers without waiting for a file to travel or a card to come back.
About sync timing
The point is operational sync between remote control, capture, and output. Teams can see when a source hits the chain, and visible delay stays explicit instead of hidden.
Hardware and software model
LGL-OS is software on hardware we build and operate ourselves: Node in your rack, Producer's editing hardware where the team works, and managed services on owned servers across two sustainable datacenters in Amsterdam and Warsaw. For now, managed hosting is EU-only and aligned with GDPR data-handling guidelines.
Software layer
- Browser control of on-site hardware over WebRTC and WebSockets, with node state visible per site.
- Tenant isolation: one hub across many organizations without mixing them.
- Operational sync between control, capture, and editing, with delay context kept explicit.
- Start with one product and add the others without re-platforming.
- Consistent operator workflows across cloud, on-premise, and hybrid environments.
Hardware layer
- Node is one rack unit that takes one role at a time: switcher control, scope, audio monitor, or encoder.
- Frame-complete transport moves 100% of the stream off site, not best-effort.
- Producer runs one of two ways, chosen per deployment: on-prem on your hardware, or managed on our servers.
- On-prem keeps media and projects on your network, with SDI captured on board.
- Server takes media as a stream or a frame-complete Node feed, and editors work from anywhere.
- Managed infrastructure hosted on our own server fleet.
- Dual-location deployment footprint in Amsterdam and Warsaw.
- Sustainable datacenter operations as the default hosting baseline.
Need a deployment fit-check? We can map your current hardware estate to an LGL-OS rollout plan during a demo session.
What holds it together
Three products sold under one name only counts for something if they behave like one system. These are the properties we hold them to.
01
Frame-complete by default
Node's transport to Producer delivers every frame, not best-effort. Where delay exists, it stays visible in the operator surface rather than absorbed silently.
02
No preview/export mismatch
What you see is what you get. The preview renderer and the export pipeline use the same source of truth. Frame for frame.
03
Multi-operator
Multiple people can work across the system simultaneously, across multiple sites, without stepping on each other.
04
Deployable anywhere
On-premise hardware, cloud infrastructure, or a hybrid of both. The system adapts to your environment, not the other way around.
05
Reliability over feature count
We ship what works. We don't add features to fill a comparison chart.
Ready to get started?
Producer is in closed beta and taking new clients now. Node lands Q4 2026, REMI Q1 2027. Tell us how you work and we'll map a rollout plan against those dates.
Demo workflow and qualification form are placeholders and can be replaced with your CRM flow.