Roadmap

On the roadmap

• HA add-on: automatic failover.Planned as its own add-on (~$200/yr) rather than folded into base licensing: a standby gateway that continuously tracks the live primary's routing setup and mirrors it, ready to take over the moment the primary goes down — and, because it's tracking the primary rather than independently routing the same feeds live, it won't count against your licensed source/destination usage the way running two fully independent instances does today. Not started. Today, a single gateway is a single point of failure for the gateway process itself (routes and presets survive a restart and everything reconnects automatically once it's back, but nothing fails over to a second machine while it's down) — the only way to get redundancy right now is the manual method below.
• Manual redundancy, available today.Unlimited-install licensing means you can already run a second OmniBridge instance on a secondary machine or network path with no separate per-install license to buy — see Compare. This is manual, though: you configure the standby's sources/destinations yourself, it doesn't track the primary's live routing changes, and — since usage is summed across every install checked in under one key — if both instances mirror the same sources/destinations live at once, that's counted on both, so plan for authorized capacity covering the combined total. The planned HA add-on above is what removes both the manual setup and that usage double-count.
• SDI capture & playout (attached hardware).Every source and destination today is IP-based — no path in or out for baseband SDI. Bringing it in means a capture card physically installed in the machine running the gateway (Blackmagic DeckLink is the obvious first target) and the vendor's own SDK, the same shape of work NDI support already went through. Scoped as capture first, then playout.
• WebRTC.Sub-second-latency browser-based contribution and playback, alongside SRT/RTMP/RIST/NDI — no dedicated encoder needed on the sending side, just a browser tab. Not started; would follow the same add-on licensing shape as RTMP/RIST/NDI once built.
• Time-sync (SMPTE timecode / PTP).Carrying a source's embedded timecode through the gateway, and disciplining the gateway's own clock via PTP so timestamps mean the same thing facility-wide. Neither exists today — every stream is relayed as an opaque payload. Worth being upfront about the ceiling here too: even once built, this identifies which frame a source is on, it doesn't deliver true frame-accurate genlock across independently-encoded network sources the way a shared reference generator does for SDI.
• Peplink InControl diagnostics integration.Pull WAN/cellular status (connection type, signal strength, data usage, uptime) from Peplink's InControl2 API and correlate it with SRT connection events on the Diagnostics page — so a dropped stream shows *why* (e.g. cellular signal loss), not just the SRT-side symptom. Needs InControl API credentials before implementation starts.
• Epiphan API remote control.Remote control of Epiphan capture/streaming hardware (e.g. Pearl) via their device API — start/stop, encoder settings, reboot. Early idea, not yet scoped.
• Custom install ISO / appliance image.A pre-built Linux image with OmniBridge already installed and ready to go — flash a drive, boot it, and you're at the dashboard, no manual Debian/Ubuntu setup first. Useful for any new install, and especially for standing up a hot-standby node quickly (see the redundancy item above). Not started.
• Topology / signal-flow view.A real interactive diagram of source → gateway → destination routing, instead of reading it off the Operate/Diagnostics tables. Being considered, not built yet.
• Persistent event logging.The Events tab is currently a live, in-memory session log only — it doesn't survive a gateway restart. Persisting it to disk is planned, not started.
• OBS SRT Toolkit's own dedicated encoder.The shipped OBS SRT Toolkit plugin's SRT Output currently reuses whichever encoder OBS's own Streaming or Recording output already has configured, rather than creating a dedicated one — so Stream or Record needs to have been started at least once first. A version with its own independent encoder is planned as a follow-up.

Deliberately not planned

Tracked for visibility, not committed to any release.

• Single-feed destination diagnostics.RTMP/RIST/UDP-TS connectivity tracking in the Diagnostics view — a real, acknowledged gap, but a bigger lift than a quick add-on to the existing view.
• Per-destination preset scoping.No current plan — presets stay all-or-nothing across the whole matrix.