Eyevinn Strom

Eyevinn Strom is an open-source, web-based GStreamer media pipeline and vision-mixer engine with a visual node editor. Build and run real-time media pipelines in the browser: switch program and preview (PGM/PVW), add a downstream keyer (DSK) and picture-in-picture (PiP), apply transitions, and composite live sources, all without writing code.

Key features

• Browser-based visual node editor for real-time GStreamer media pipelines
• Vision-mixer workflow: program/preview (PGM/PVW), downstream keyer (DSK), picture-in-picture (PiP), transitions and live compositing
• Ingest and output over common transports (RTSP, SRT, NDI, WHIP) via GStreamer
• REST API with Swagger UI (/swagger-ui) and a stored library of flows and blocks
• Runs the official, unmodified eyevinntechnology/strom container
• CPU-friendly: the base image uses a software GL path (llvmpipe) and software video conversion, so the full web vision-mixer UI runs on a standard VM with no GPU

CPU vs GPU posture This appliance ships the BASE Strom image and runs entirely on CPU (software rendering / software video conversion), which is ideal for control, orchestration, and light compositing on any NetActuate location. GPU/EGL-accelerated shader effects and CEF-based HTML-source rendering are provided by the separate strom-full image and benefit from a GPU/VPU-capable location; deploy this base appliance where you want the vision-mixer UI and pipeline engine without dedicated GPU hardware.

Use cases

• A browser-driven live vision mixer / switcher for remote production
• Compositing and keying (DSK, PiP, lower-thirds) in front of a stream or origin
• A GStreamer pipeline orchestration surface for ingest/transform/output workflows

Why run it on the NetActuate edge Running Strom in a PoP near your contributors and sources shortens the ingest and control path for live production and keeps your pipelines and compositions on infrastructure you control.

Deployed from the NetActuate marketplace, Strom boots pre-configured from your seeded values: authentication is enabled with your admin username and password (the password is generated into your secret list if not provided and hashed in-guest with bcrypt) plus an API key for bearer access. Sign in at the web UI on HTTP port 80; the REST API and Swagger UI (/swagger-ui) share the same port. Media ingest/egress (RTSP, SRT, NDI, WHIP) benefits from additional port exposure or host networking (a documented follow-up); put TLS termination in front before exposing the instance publicly.