Installing and configuring Helmo Middleware

Helmo Middleware is a lightweight desktop app that bridges Helmo Live in the cloud with software running on your local network.

When do you need Helmo Middleware?

You need it when your production software can only be reached over the local network:

• OBS Studio on a remote machine (not the same computer running the browser).
• vMix on a remote machine.
• CasparCG (always requires middleware, because of its TCP/AMCP protocol).
• Meld Studio on a remote machine.

If your software is on the same machine as your browser, you can usually connect directly without middleware.

Downloading Helmo Middleware

1. Go to Connect → Middlewares in your Helmo workspace.
2. Click + New Middleware to create a middleware record.
3. Download the installer for your OS: - Windows: .exe installer - macOS: .dmg installer

Installation

Windows

1. Run the downloaded .exe installer.
2. Follow the installation wizard.
3. The app launches automatically after installation.

macOS

1. Open the .dmg file.
2. Drag Helmo Middleware to your Applications folder.
3. Launch the app from Applications.

Configuring Helmo Middleware

1. On first launch, the app will ask for your Middleware ID and API Key.
2. In Helmo, go to your middleware's detail page and copy the ID.
3. Generate an API Key from the API Key tab on the middleware detail page.
4. Paste both into the Helmo Middleware app and click Connect.
5. The app should show a green status indicator when connected.

How it works

Helmo Middleware connects to Helmo via Supabase Realtime (WebSocket). When you press a button in Helmo Control, the command flows like this:

Browser → Supabase Realtime → Helmo Middleware → Local Software (OBS, vMix, CasparCG, Meld Studio)

Helmo Middleware sends a heartbeat every 30 seconds so Helmo knows it's online. If the heartbeat stops, the middleware shows as offline in the Integrations Hub.