← Back to protocols.foundation

Licensing

Open standards, open implementations, clear boundaries. The protocol spec is Apache 2.0 — use it freely. Reference implementations are AGPL 3.0 — contribute back or get a commercial license.

Contents

1. Overview

Everything splits into two layers, separated by the Matrix wire protocol.

Layer 1 — Open Protocol (Apache 2.0) foundation-protocols-events/ 188 event type definitions — JSON schemas, Kotlin data classes Use freely. No copyleft. No attribution in code required. Implement on ANY Matrix homeserver. ——— Matrix wire protocol (JSON / HTTPS) = license boundary ——— Layer 2 — Open Implementation (AGPL 3.0) Bridges Messenger Claude Bridge (Kotlin) openearth-messenger (Kotlin) Hopsworks Bridge (Python) foundation-protocols-views/ Legal-MCP Bridge (Python) Client messengers (white-label) AGPL 3.0 — VakeWorks AB © AGPL 3.0 — forced by Trixnity Commercial licensing available (connect2x GmbH dependency) All released on Codeberg: codeberg.org/openearth
Key principle: The protocol spec (Layer 1) and the implementations (Layer 2) are separated by the Matrix wire protocol. Your software does not need to be AGPL to send or receive foundation.protocols.* events. The JSON data crossing the wire carries no license.

2. The Wire Protocol Boundary

Matrix events are JSON transmitted over HTTPS. This is a license boundary recognised by all major open-source licenses (AGPL, GPL, Apache, MIT).

Your Client —JSON/HTTPS—> Matrix Homeserver <—JSON/HTTPS— AGPL Bridge Any license Any license AGPL 3.0 (Apache, MIT, proprietary) (tuwunel: Apache, Synapse: AGPL) (VakeWorks AB)

This means:

Only compile-time linking triggers AGPL. Network communication (HTTP, WebSocket, stdio) does not.

3. Protocol Spec — Apache 2.0

The event definitions are the protocol spec. Use them freely in any project, commercial or otherwise.

ComponentLicenseCodeberg
foundation-protocols-events/ Apache 2.0 foundationprotocols

188 event types: 4 data + 17 AI governance + 42 Claude + 15 observation + 15 gryph + 5 hooks + 4 certification + 8 IAS + 37 Hopsworks + 11 Ansvar + 1 cost + 11 EUDR + 18 legal. Kotlin @Serializable data classes. JSON schemas. No MSC required — custom namespaced events are a blessed Matrix extension mechanism.

EU public procurement: Apache 2.0 is OSI-approved and meets EU open-source requirements. No vendor lock-in — any organisation can implement the spec on their own Matrix homeserver without licence fees or agreements.

4. Bridges — AGPL 3.0

Transparent proxies recording AI, ML, and legal interactions as Matrix events. AGPL 3.0, VakeWorks AB copyright. Commercial licensing available.

BridgeStackEventsCodeberg
Claude Bridge Kotlin, Trixnity 4.22.7, Ktor 42 ai.claude.* + 15 ai.observation.* + 4 ai.certification.* openearth-ai-bridge (coming soon)
Hopsworks Bridge Python, matrix-nio 37 ai.hopsworks.* openearth-hopsworks-bridge (coming soon)
Ansvar Bridge Python, matrix-nio, MCP proxy 11 ai.ansvar.* openearth-ansvar-bridge (coming soon)

AGPL 3.0 — VakeWorks AB copyright. Dual-licensing available for organisations that need proprietary embedding or modification without sharing.

EU public procurement: AGPL 3.0 is OSI-approved. Bridge source code is publicly auditable on Codeberg. No runtime dependencies on proprietary services. Bridges communicate over Matrix wire protocol (JSON/HTTPS) — no licence obligations propagate to your homeserver or clients.

5. Messenger — AGPL 3.0

Compose Multiplatform Matrix client with 116 custom views across 6 domains. AGPL 3.0 (forced by Trixnity dependency).

ComponentLicenseWhyCodeberg
OpenEarth Messenger AGPL 3.0 Links to trixnity-messenger (AGPL, connect2x GmbH) openearth-messenger (coming soon)
foundation-protocols-views/ AGPL 3.0 Links to trixnity-messenger (AGPL) Included in openearth-messenger
Reference legal-MCP Messenger AGPL 3.0 White-label — legal + AI modules reference legal-MCP messenger (coming soon)
Reference EUDR Messenger AGPL 3.0 White-label — EUDR + AI modules reference EUDR messenger (coming soon)
Admin Console Apache 2.0 Browser-only JS — no AGPL dependencies openearth-admin-console (coming soon)
EU public procurement: AGPL 3.0 is OSI-approved. Source publicly auditable. No proprietary components required to use the messenger. White-label configurations allow per-organisation branding under the same AGPL terms.

6. Dependency Chain

Full transparency on what the reference implementations depend on.

Application Dependencies

DependencyLicenseUsed ByLink Type
Trixnity SDK 5.x AGPL 3.0 / Commercial Messenger Compile-time (forces AGPL)
trixnity-messenger AGPL 3.0 Messenger, Views Compile-time (forces AGPL)
Trixnity SDK 4.x Apache 2.0 Claude Bridge Compile-time (no AGPL force)
matrix-nio Apache 2.0 Python bridges Import (no AGPL force)
Kotlin / Compose Multiplatform Apache 2.0 Messenger, Claude Bridge Compile-time
Ktor Apache 2.0 Claude Bridge Compile-time

Trixnity SDK and trixnity-messenger are developed by connect2x GmbH (Germany). Trixnity SDK 5.x is dual-licensed: AGPL 3.0 for open-source use, commercial licence for proprietary use. Trixnity SDK 4.x (used by the Claude Bridge) was released under Apache 2.0.

Infrastructure Dependencies

ComponentLicenseMaintainerNotes
tuwunel Apache 2.0 Community (Conduit fork) Rust homeserver, single binary
continuwuity Apache 2.0 Community (Conduit fork) Rust homeserver, community-maintained
Synapse AGPL 3.0 Element / Matrix.org Foundation Python homeserver, feature-complete
Element Web Apache 2.0 Element Web client (alternative to OpenEarth Messenger)

Infrastructure dependencies are third-party software, not developed or maintained by VakeWorks or The Protocols Foundation. All are open source. Your choice of homeserver does not affect the licence of your client or bridges.

7. EU Public Procurement Compliance

The entire stack is designed for EU public sector and regulated industry deployment.

RequirementHow Satisfied
Open-source code Protocol spec (Apache 2.0), messenger (AGPL 3.0), bridges (AGPL 3.0) — all on Codeberg
Publicly auditable Source code public. Builds reproducible. No hidden proprietary components required for operation.
OSI-approved licences Apache 2.0 and AGPL 3.0 are both OSI-approved. No "source available" or non-standard licences.
No vendor lock-in Matrix is an open protocol. Data exportable. Any compliant client or homeserver works. Standard HTTPS APIs.
Data sovereignty Homeserver in your jurisdiction. EU infrastructure (Hetzner, OVH). No US cloud dependency. E2EE by default.
Supply chain transparency Full dependency chain documented above. All dependencies are open source with known licence holders.
Interoperability Matrix federation protocol. foundation.protocols.* events are standard custom events — no server modifications needed.

Organisations procure the managed service (deployment, support, SLA), not the code. The code itself is freely available. Commercial licensing is available for organisations that need non-AGPL terms.

8. Source & Downloads

Protocol Spec

Apache 2.0 — The Protocols Foundation

Source Code

AGPL 3.0 — VakeWorks AB

Downloads

Multiplatform messenger apps

  • OpenEarth Messenger (coming soon)
  • Linux, macOS, Windows — Kotlin/Compose Multiplatform
  • Releases via Codeberg Releases

9. Frequently Asked Questions

Can I implement the protocol spec in my own client?

Yes. The event definitions are Apache 2.0. Build your own client, bridge, or integration in any language, under any licence. No permission needed.

Can I use the bridges in my product?

Yes, under AGPL 3.0. If you modify the bridge and offer it as a service, you must publish your modifications. For proprietary use, contact VakeWorks for commercial licensing.

Can I use the messenger for my organisation?

Yes, under AGPL 3.0. Deploy it, brand it, add modules. Source must remain available. White-label configurations (custom branding, module selection) are available as a managed service.

Can I build a proprietary client that reads these events?

Yes. The Matrix wire protocol (JSON/HTTPS) is a licence boundary. Your client communicates over the network — it does not link to AGPL code. Your client is your licence.

Can I fork the bridges and keep changes private?

Not under AGPL 3.0. If you modify the bridges and deploy them (even internally as a network service), you must make the source available to users. Contact VakeWorks for commercial licensing if AGPL does not suit your needs.

Does using the messenger require a licence from connect2x?

Not for AGPL usage. The AGPL licence grants full rights to use, modify, and distribute — as long as source remains available. A commercial licence from connect2x is only needed if you require proprietary (non-AGPL) terms for the Trixnity dependency.