Welcome to the Playdeck Cloud & Remote Productions guide. This central guide helps you transition from a local studio environment to a decentralized or cloud-hosted setup. Rather than detailing specific commercial cloud providers, this page gives you the exact blueprint to deploy Playdeck on any online server or headless machine, feed remote streams into your playlists, and configure network triggers for total remote automation.
In this article:
→ Why Choose Remote Deployment? (Production Use Cases)
→ System Requirements & Network Architecture
→ Remote Inputs
→ Remote Outputs
→ Remote Control & Automation
Why Choose Remote Deployment? (Production Use Cases)
Installing Playdeck on an online remote server or data center computer instead of a local office machine provides critical architectural advantages. Below is why professional workflows utilize remote deployments:
Scenario A: High-Pressure Corporate Events & Galas
- The Problem with Local Office Setup: Running a live event playout from an office or venue laptop exposes you to local network drops, accidental Windows update reboots, or personnel accidentally messing with the local machine.
- Why Remote PC Deployment: By moving Playdeck to a dedicated online server, you isolate the playout engine entirely. Even if your local office internet goes down completely, Playdeck continues to run safely in the data center. Its dedicated HDMI/SDI output automatically isolates the feed—guaranteeing that the operating system desktop, mouse cursors, or other running applications are never displayed on the program feed, maintaining a clean look even if a remote operator disconnects.
Scenario B: 24/7 Fixed Installations & Automated Playout
- The Problem with Local Office Setup: Office computers are vulnerable to local power outages, hardware tampering, and standard consumer network interruptions, making them highly unreliable for around-the-clock broadcasting.
- Why Remote PC Deployment: A remote data center computer offers enterprise-grade power redundancy (UPS) and climate control. You can manage a completely headless system from anywhere via RDP. Because you have full remote access, you can update, reorder, or completely replace the active playlist remotely via the web interface or API commands from any device worldwide, ensuring instant schedule adjustments on a headless system without interrupting the active stream.
Scenario C: Multi-Destination Cloud Distribution & Monitoring
- The Problem with Local Office Setup: Standard office DSL or Wi-Fi connections simply lack the upload bandwidth required to output multiple high-quality video streams simultaneously, causing massive packet loss and stuttering.
- Why Remote PC Deployment: Data center servers are hooked directly into massive internet backbones with symmetrical gigabit speeds. This allows you to output your main playout signal to a high-quality master SRT destination while simultaneously pushing multiple lower-bitrate RTMP feeds to social platforms—completely bypassing local office bandwidth bottlenecks. Furthermore, production assistants or clients can monitor the active playlist, clip countdowns, and system health status globally via the Web UI interface, ensuring zero performance impact on the primary hardware-accelerated video rendering engine.
System Requirements & Network Architecture
You can run Playdeck in the cloud or data centers on almost any modern virtualized or physical machine. This provides massive internet bandwidth for handling multiple parallel stream outputs and high-bitrate ingests compared to typical office DSL or Wi-Fi connections.
- Operating System: Any standard Windows 11 (64-bit) environment.
- Remote Management: The system can run completely “headless” (without a physical monitor attached). You can connect and manage the interface entirely via Remote Desktop Protocol (RDP).
- Hardware & GPU: While standard hardware requirements apply, a dedicated GPU (e.g., NVIDIA) is highly recommended to handle hardware decoding for common codecs like H.264.
- Base Specifications: For a detailed breakdown of recommended components, check out our Playdeck PC Build Guide.
Remote Inputs
Playdeck features an intelligent ingest engine that automatically detects your input source type. A major technical advantage: Playdeck does not constantly consume bandwidth for all streams. It initiates the stream network pull dynamically right before the clip is scheduled to air (one clip ahead in the playlist), allowing you to queue an infinite number of remote cameras or feeds without overloading your network.
- Adding a Stream: Drag and drop the Stream Icon (located between the two playlists) directly into your playlist, then enter your ingest URL.
- SRT & Live Feeds: Feed low-latency Secure Reliable Transport (SRT) or generic stream links directly into your timeline. For detailed stream configuration, see our Input Streams Guide.
- YouTube Ingest: Paste any YouTube video or livestream URL. After Playdeck scans the link, right-click the item in your playlist and navigate to Video Tracks or Audio Tracks to manually select your preferred stream quality. Learn more in our YouTube Integration Guide.
Remote Outputs
Distribute your playout signal from your cloud server or studio to any remote destination with maximum efficiency:
- Direct Cloud Streaming: Use the native streaming options to push your output directly to major cloud platforms (YouTube Live, Twitch, Facebook Live) or custom RTMP/SRT media servers.
- Low-Latency Master Control: Deliver high-quality SRT output feeds to enterprise cloud switchers or decentralized broadcast facilities.
- Virtual Monitoring: Map Playdeck’s output to virtual camera and audio drivers to route the live feed directly into video conferencing tools (Zoom, Microsoft Teams) for instant client approval or remote monitoring.
Remote Control & Automation
Playdeck offers a deep matrix of network commands, remote interfaces, and hardware trigger support divided cleanly within the settings menu.
Network > Remote Control
- Web User Interface: Access a dedicated, mobile-friendly remote layout from any smartphone, tablet, or external browser. Simply scan the QR Code displayed in this menu section to launch it instantly without manual activation steps.
- Bitfocus Companion: Control your playout from anywhere via a physical Stream Deck or virtual buttons. Review the integration steps in the Companion Documentation.
- Playdeck API: Connect via WebSockets (REST API planned) to send commands or read live playlists, playout statuses, and events. This API forms the exact foundation of our own Web UI Remote Control. Read the technical syntax in the Playdeck API Reference.
Network > Incoming
- TCP Commands: An open, versatile interface used to fully remote-control Playdeck using third-party apps, including dynamically inserting new clips or initiating streams. See the complete command list in our TCP Commands Guide.
- ATEM & vMix Integration: Map local or LAN-based ATEM Switchers (via USB/Network) and vMix instances to act as automatic CUE+PLAY triggers the exact moment a designated input goes live.
- Hardware Triggers (COM/USB): Connect older or highly customized physical hardware devices utilizing a closed-circuit setup for instant CUE+PLAY actions.
- Broadcast Standards (TSL UMD & NDI Tally): Drive automated playout via industry-standard TSL UMD (supported for versions 3.1 and 5.0, perfect for hardware mixers like ROSS) or trigger playout using NDI Tally when an assigned NDI input goes live.
Network > Outgoing
- TCP Commands: Instruct Playdeck to automatically send custom, individual strings to external third-party hardware or software whenever specific events occur (e.g., Clip/Block Start, Action Buttons, or Overlay triggers).
- TCP Events: Broadcast predefined, automated system status changes from Playdeck to keep external control systems perfectly in sync with your active playout timeline.
