khėnsu.ñü is a free, open-source alpha. Benchmarks are real, measured in Claude Opus 5.5 test runs. Less data, less energy: nocap →

Approach

Seven rules,
no exceptions.

How the studio decides what to build, how to build it, and what to say about it.

01

Build the impossible or overlooked

We start where others have stopped: problems written off as impossible, or never looked at closely because the market settled on an answer long ago.

Both are where categories are waiting. Live video has long been sold in two halves: fast calls for a room, or broadcast for everyone, seconds behind. MOQOM does both on one standard.

02

Own the category

We don’t build a better version of what already exists. We pick problems where the incumbent framing is the obstacle, and build the thing that makes the old framing unnecessary.

That means owning the layers the outcome depends on. If latency is the product, the transport is ours. If trust is the product, the security model is ours.

03

Ship standards-based technology

New categories last when they are built on open ground. We implement open standards ourselves, from the specification, rather than forking someone else’s interpretation.

MOQOM targets the IETF’s Media over QUIC Transport draft. Standards give customers longevity and an exit; our implementation gives them the outcomes.

04

Open-source SDKs, licensed engine

The SDKs you build with are open source under permissive licences, in Swift, Go and Rust, and so are the security libraries behind our tokens, device proofs and encryption. You can read the code you integrate, and anyone can check our cryptography.

The parts that make MOQOM fast are licensed, not open source: the relays and control plane, the player and the congestion controller. They run on our cloud, or ship as signed binaries under commercial terms. elliottwave.dev lists exactly what is open and what isn’t.

05

Security first

Security is part of the architecture, not a later review. Encrypted transport everywhere, short-lived credentials, and moderation that takes effect immediately.

We publish a responsible disclosure policy and treat reports from researchers as a gift.

Our HackerOne program launches as a vulnerability disclosure program. Cash bounties are funded by donations to the open-source projects until paying customers adopt MOQOM. Until then, every valid report gets public credit and our thanks — in the hall of fame and release notes — and we’ll send you something: swag in the mail or a tip to your crypto wallet.

06

Automated and turnkey

Every company out of the lab runs itself. Customers start without a sales call or an onboarding project, and the day-to-day needs no one to approve it.

MOQOM is the first: signup, billing, top-ups, API keys and spend limits are all self-serve and automated. When you do need a person, support is there, from the people who built it.

07

Measured claims

Every number we publish comes from a run we can point to, with the conditions stated beside it. A number without a run behind it does not get published.

Lab results are labelled as lab results. Every benchmark we publish carries this note: “* Built to scale: a Rust media plane and a Go control plane, each scaling out horizontally. Measured in lab: 6,000 viewers on one 4-vCPU relay, every frame delivered. Full data at moqom.cloud/benchmarks/load-tests.md.”