We build the standards
the industry will build on
next
Reading a specification and implementing it in production are different activities. Most companies stop at the first one. We contribute to C2PA, Media over QUIC, CMCD, SVTA, and CTA WAVE as implementers, not observers — we were in the room where these standards were defined, and we built the first working versions of them.
That combination — being at the table and being in production — is what makes the applied work credible. When we find an edge case in a specification through production deployment, we bring it back to the working group.
That loop between what the spec says and what actually happens at scale is how standards get better. It's the reason clients bring us in before a spec is even finished.
Implementers, not just contributors
We contribute directly to the standards shaping the future of live streaming: Media over QUIC at OpenMoQ, Common Media Client Data at CTA WAVE and SVTA, and Content Provenance and Authenticity at C2PA. In each of these, we build reference implementations, publish technical analyses, and sit in the working groups where the standard itself gets shaped — with direct feedback into the technical decisions the spec ends up making.
The Common Media Library we built is now a dependency of hls.js and dash.js, two of the most widely deployed open-source players in the industry. The CMCD Validator does the same job in a different form: a tool used by thousands of developers has to be correct at the edges, not just in the happy path.
Common Media Library
Dependency of hls.js & dash.js
CMCD Validator
Used by thousands of developers
Working Groups
OpenMoQ · CTA WAVE · SVTA · C2PA
Active projects, evolving as the protocols do
MoQ transport for low-latency live
A reference implementation of the emerging Media over QUIC protocol, built in collaboration with a Tier-1 streaming platform's video infrastructure team, aimed at the next generation of low-latency live streaming.
C2PA content provenance
A reference implementation of the C2PA standard, with our findings feeding directly into technical decisions on the specification itself — not just an integration built after the fact.
Live media engineering operations
Real-time signal quality monitoring, incident response, and runbook generation for Tier-1 global broadcasters and streamers during high-viewership events.
See how we run live operations →Ongoing platform engineering
Daily work across encoding pipelines, ABR packaging, DRM integration, and player-side troubleshooting for major media and streaming platforms serving global audiences.
See how we build platforms →Being first only matters if it's right
Anyone can ship the first implementation of a spec that isn't finished yet. Getting it right is a different problem.
Before an early implementation goes anywhere near a client's production environment, it passes through our own internal working groups, and gets a layer of leadership oversight from senior architects who check it against where the standard is actually heading. That's what lets us move early without moving carelessly.
Applied R&D is how we stay sharp
We run an internal applied R&D practice focused on emerging video technologies, separate from any single client engagement. Tracking where the streaming space is moving is a core part of the job description:
How we approach R&D engagements
PoC is the beginning, not the deliverable
We take R&D work through the stages that matter: proof of concept, reference implementation, integration with real systems, production validation. The result is something a client can build on, not just something we demonstrated at a conference.
Implementation feedback improves the spec
When we find an edge case in a specification through production deployment, we bring it back to the working group. This creates a loop between what the spec says and what actually works, positioning clients to influence where the industry goes next instead of reacting to it later.
Early adoption done correctly is a durable advantage
Being first only creates advantage if the implementation is correct. We track where each spec sits in its maturity cycle, stable enough to build on, early enough for real differentiation. That window is narrow, and knowing where it is requires working from inside the standard, not reading about it from outside.
What we've built
C2PA + MoQ + DRM: the live streaming stack the industry has been waiting for
Joint reference implementation with EZDRM, Ateme, and Cloudflare — content authenticity, low-latency transport, and DRM in a single live workflow built on specifications still being finalized.
View case → Open Source · SVTACommon Media Library: adopted by hls.js and dash.js
A library that unifies metadata handling across adaptive streaming implementations — adopted as a dependency by two of the most widely deployed open-source players in the industry.
View case → NAB 2026 · C2PAVerifiable Authenticity for Streaming Video with Unified Streaming & WDR
Full C2PA pipeline from dynamic packaging to player-side authenticity verification — first public demonstration of the standard in a live streaming context.
View case → Open Source · ToolCMCD Validator: easy-to-use validation for video developers
An open-source CMCD validation library built to be correct at the edges — because a tool used in production by thousands of developers has to be.
View case → Standards · Live VideoC2PA for live video: signing and authenticating content in real time
Applying C2PA to a live video workflow — a space with no prior art in the spec. Implemented, tested, and contributed findings back to the working group.
View case → Standards · CMAFCMAF HAM: Simplifying Media Transcoding
Bridging HLS and DASH formats through the CMAF Hypothetical Application Model — simplifying media workflows and contributing tooling to the ecosystem.
View case →Exploring an emerging standard?
We can tell you where the specification actually is, what production deployment looks like, and whether the timing is right for your platform.
Talk to us