Our Mission

Open Standards

We publish specifications openly. No vendor lock-in, no secret handshakes. Every implementation can interoperate.

Interoperability

Alliance members can connect their products seamlessly. Same protocols, same security model, verified compatibility.

Shared Tools

Open-source reference implementations (librist, libsipmx_transport, SipmxCore.Nucleus) and the DeviceSDK accelerate adoption.

Member Benefits

SIPMX Compatible Badge

Display the "SIPMX Compatible" badge on your products to signal interoperability to customers.

Logo Showcase

Your company logo featured on the Alliance page, linking to your website.

Early Spec Access

Review and provide feedback on draft specifications before public release.

Technical Support

Direct access to engineering support for DeviceSDK integration and protocol questions.

Interop Events

Participate in plugfests and interoperability testing with other Alliance members.

No Membership Fees

Join the Alliance at no cost. We're building an ecosystem, not a paywall.

For Device Manufacturers: The Adoption Path

Whether you build NDI®-compatible cameras, Dante®/AES67 audio devices, SRT™-capable encoders, or IPMX devices — there's a clear path from interoperability to native NMOS support.

1

External Gateway

For end users — deploy today, zero device changes

Your devices already work. Facilities deploy SipMX Gateway to discover NDI-compatible sources via mDNS, receive AES67 streams from Dante-enabled devices, accept SRT streams from existing encoders, and bridge them all into NMOS workflows — with no firmware changes on any device. Unified routing, monitoring, and WAN contribution today.

2

Embedded Gateway

For manufacturers — ship NMOS bridging inside your appliance

Bundle SipMX Gateway (with the DeviceSDK built in) directly inside your product. Your appliance ships with NMOS bridging out of the box — your customers don't need a separate gateway. The embedded gateway handles protocol translation internally and registers as a full NMOS node. Cross-compilable C/C++ binary, runs on x86_64 and ARM64. No firmware rewrite required.

3

Native DeviceSDK

For manufacturers — deepest integration, lowest latency

Integrate the SipMX DeviceSDK directly into your firmware (~20 lines of code). Your device feeds media directly via UDP to the SDK — if it already supports any streaming protocol, it already has UDP. The SDK provides the full NMOS control plane (IS-04 discovery, IS-05 connection management, BCP-008-01 health monitoring), built-in RIST and SRT transport via libsipmx_transport — including decoder synchronization, satellite redundancy, multipath bonding, and content selection. Far lower overhead than the embedded gateway.

4

SIPMX Certification

Premium positioning in the ecosystem

Pass SIPMX compliance testing and get listed in the certified device directory. Full interoperability with all SIPMX workflows: crosspoint routing, multi-site federation, WAN transport, and enterprise security. Available for both embedded gateway and native DeviceSDK integrations.

NDI® Device Manufacturers

With gateway (stages 1–2): Your NDI transport stays — the gateway handles translation. Your cameras gain NMOS manageability: IS-04 discovery, IS-05 routing, BCP-008-01 monitoring, IS-11 capabilities. With native DeviceSDK (stage 3): NDI is out of the picture — your device feeds media directly via UDP into the NMOS ecosystem for the lowest latency and deepest integration.

Dante®/AES67 Device Manufacturers

With gateway (stages 1–2): Your AES67 audio transport stays — the gateway handles translation. Your devices gain unified video + audio management: IS-04 discovery alongside cameras, IS-08 channel mapping, IS-07 tally integration. With native DeviceSDK (stage 3): Dante/AES67 is out of the picture — your device feeds audio directly via UDP for the lowest latency.

SRT™ Device Manufacturers

With gateway (stages 1–2): Your SRT transport stays — the gateway handles full translation. Your encoders and decoders gain NMOS discovery: IS-04 visibility, IS-05 routing, BCP-008-01 monitoring, RIST WAN transport. With native DeviceSDK (stage 3): Your device feeds media directly via UDP to the SDK (if you have SRT, you have UDP). Built-in RIST and SRT transport via libsipmx_transport — including decoder synchronization, satellite redundancy, and multipath bonding — far lower overhead than the full gateway.

Alliance Members

Companies building the future of interoperable media.

Your company could be here. Join the Alliance and help shape the future of media orchestration.

Apply for Membership

Join the Alliance

Who Can Join?

  • Device Manufacturers — Building encoders, decoders, gateways, cameras, or media processing equipment — including manufacturers of NDI®-compatible, AES67-capable, and SRT™-capable devices looking to add NMOS manageability
  • Software Vendors — Developing broadcast automation, media asset management, or control systems
  • System Integrators — Deploying NMOS-based infrastructure for broadcast and corporate AV
  • Cloud Providers — Offering media services that need standards-based interoperability

How It Works

  1. Apply — Submit your interest through the contact form
  2. Review — We'll discuss your use case and integration plans
  3. Integrate — Implement SIPMX specs or use the DeviceSDK
  4. Verify — Basic interoperability check with reference implementation
  5. Welcome — Logo added to Alliance page, badge provided

Ready to Join?

No membership fees. No complicated agreements. Just a shared commitment to open, interoperable media.

Become a Member

Questions? Email us at alliance@sipmx.com

The SIPMX Alliance is managed by SipMX LLC. We champion open specifications through AMWA and VSF standardization processes, and open-source reference implementations including librist and libsipmx_transport.