open-source

What’s open source, and what isn’t.

The SDKs and security libraries you build with are open source. The engine that makes MOQOM fast, from the relays to the player, is licensed and ships as binaries under commercial terms. Here is exactly which is which.

Open source

Published at github.com/moqom-cloud. Apache-2.0 was chosen over MIT for its explicit patent grant and patent-termination terms.

RepositoryWhatLicenceStatus
moqom-goGo server-side SDK. Lets your backend administer rooms, moderation and client tokens through the MOQOM control plane API.Apache-2.0Public
moqom-rustRust server-side SDK (crate moqom-sdk) with the same scope as moqom-go. No QUIC stack in its dependency graph.Apache-2.0Public
moqom-securityThe security libraries: device-bound ML-DSA-87 tokens, device proofs, SFrame media encryption and post-quantum MLS, in Swift, Go and Rust, with shared test vectors.Apache-2.0Public
moqom-swiftMoqomKit for Apple platforms: the open SDK shell for rooms, publishing, capture, transport and the wire codec. Includes the MoqomRoom sample app.Apache-2.0Public, after the player split
moqom-web · moqom-android · moqom-desktopClient SDKs for browsers (over WebTransport), Android, and Windows/macOS/Linux. Open SDK shell; playback ships as a binary.Apache-2.0 + player binaryIn progress, coming Q4 2026
moqom-obsOBS Studio output plugin. Publish-side only.GPL-2.0-or-laterScoped, work ongoing

Licensed components

Not open source, and not source-available: these ship only as signed binaries. You don’t need their source to check MOQOM’s security. Media is end-to-end encrypted before it reaches a relay, and the cryptography that protects it lives in the open-source security libraries above.

ComponentWhatTermsDistribution
PlayerPlayback for every client platform. Signed binary, licensed for use with MOQOM Cloud or a licensed self-hosted (BYOC) relay.Proprietary EULABinary only
Relay and control planeThe MOQOM service itself. Run for you on MOQOM Cloud, or licensed to self-hosting (BYOC) customers as signed binaries. The source isn’t distributed.Proprietary, commercial licenceBinary only
Congestion controllerLinked by the client SDKs as a prebuilt binary. Apache-only builds, such as the OBS plugin, use a stock controller instead.Proprietary EULABinary only

Source-available

Free to use and modify for noncommercial purposes, but not OSI open source, and we don’t describe it as such.

RepositoryWhatLicenceStatus
six10nineA macOS menu bar app that gives every app the same ⌘ chords. You choose the menu item each chord clicks in each app, and on-device AI helps a chord mean the same thing in apps where you haven’t set it yet, without anything leaving your Mac. Playing chords earns aura, which unlocks more chord keys. Optionally, while your Mac is idle and plugged in, it lends spare CPU and GPU time to Einstein@home, the Max Planck Institute for Gravitational Physics’ volunteer search for pulsars and gravitational waves.

Free and source-available: free to use and modify for noncommercial purposes. It is not OSI open source, and it can’t be sold. Patents pending. A signed DMG and a Homebrew cask are coming, release planned October 2026, plus an MCP server for AI assistants.

github.com/elliott-wave-labs/six10nine
PolyForm Noncommercial 1.0.0Repository goes public soon

Who owns the code

Elliott — Founder of elliottwave.studio lab and Elliott Wave LLC. Elliott is the sole author.

Elliott Wave LLC, founded and solely owned by Elliott, owns all intellectual property in its projects — the open-source projects included. An open-source licence lets you use the code; it does not transfer ownership. Patents pending.

Contribute

Bug reports, fixes, examples and documentation are welcome on the open repositories.

Copyright Assignment Agreement

Outside contributors sign a Copyright Assignment Agreement, assigning copyright in their contribution to Elliott Wave LLC, with a permanent licence back to use their own work for anything. Your first pull request asks you to sign it by leaving a comment. We have contacted legal counsel to review the agreement.

Build and test

No account or network access is needed; the tests run against an in-process fake of the control plane.

# moqom-go
go test ./...

# moqom-rust
cargo test --workspace

Where to start

  • Look for the good first issue label. Documentation fixes, examples and clearer error messages are always useful.
  • Open an issue first for anything bigger than a bug fix.

Code of conduct

Be kind, be specific, assume good faith. Harassment of any kind gets you removed from the project.

Vulnerabilities

Don’t open a public issue. Email security@moqom.cloud; see/security.

Support the work

Donations fund open-source maintenance and the bug bounty.

Third-party code

Repositories that include third-party components credit them in their NOTICE files, and those components remain under their original licences.

Licences are as stated in each repository; where this page and a repository’s licence file differ, the licence file governs.