We Are Falcon has moved its Falcon Live remote contribution system into active testing. The product is designed around a deliberately simple invitation model: instead of generating and managing a separate link for every guest, each production company receives one reusable browser address that can serve as the entry point for all contributors.
A guest opens the company-specific address, enters through a browser and waits in a lobby until the production team is ready. The control room can then bring that contributor into the live workflow at the appropriate moment. The design targets a familiar operational problem: links are often created by one person, distributed by another and then matched to guests under time pressure. A persistent entry point can remove several of those coordination steps.
We Are Falcon says the system supports both NDI and SDI inputs and outputs, along with multiple audio input options. That makes the product relevant to software-led IP productions as well as facilities that still need conventional baseband handoff. The company also says Falcon Live can run in the cloud or on a local server at the broadcaster's own facility.
The local deployment option matters for organisations that need tighter control over routing, contribution paths or data handling. A cloud instance may be faster to deploy across distributed productions, while an on-premises server can sit closer to the vision mixer, audio infrastructure and monitoring chain. Falcon Live is being positioned to cover both rather than forcing every customer into the same architecture.
The project remains in a test phase, so the announcement is not a general-availability notice. We Are Falcon is offering demonstrations while testing continues. Its public product description places Falcon Live alongside Falcon Rundown and Falcon Play as the contribution layer in a wider production chain: guests enter remotely, the show is planned in the rundown, and automation and playout are handled downstream.
