Licensing

MVRX OSS does not use a single license for everything. Each package carries its own LICENSE file, which takes precedence over the repository root’s LICENSE.

@mvrx/mail — AGPL-3.0-only

@mvrx/mail is the AI email consumption SDK and the foundation the (future) hosted service must use. Because it’s AGPL-3.0-only, if you modify it and run it as a network service, you must make your modified source available to users of that service.

A commercial license (no AGPL obligations) is available from mvrx.group for anyone who wants to embed @mvrx/mail in a closed-source product without the AGPL’s network-copyleft requirement.

@mvrx/wbxml — MIT

@mvrx/wbxml is a standalone protocol parser with no product logic, so it’s licensed permissively to be freely embeddable — copyleft would only suppress its adoption as a general-purpose npm package. Use it in proprietary software with no obligations beyond the standard MIT attribution notice.

AECS-1 and AECS-SDK-1 — CC0 1.0 (public domain)

Both specifications — the NormalizedEmail schema, the threading algorithm, the timestamp rules, and the full SDK surface described in AECS-SDK-1 — are published under CC0 1.0. That means:

• You can implement AECS-1 in any language, for any purpose, commercial or not.
• No attribution is required (though it’s appreciated).
• No permission is required from MVRX to build a conformant, competing implementation.

This is deliberate: AECS-1 is meant to be a community standard, not a vehicle for locking implementers into MVRX’s SDK. The conformance fixture suite exists precisely so independent implementations can verify they match the spec without needing to read @mvrx/mail’s source.

Summary

Contributing

Contributions to @mvrx/mail and @mvrx/wbxml require a Signed-off-by trailer (Developer Certificate of Origin) so MVRX can continue to offer commercial licenses covering contributed code. See CONTRIBUTING.md in the source repository.