Skip to content

Publish commercial licensing terms and permission status - #2180

Merged
asim merged 5 commits into
mainfrom
commercial-licensing-terms
Nov 17, 2026
Merged

asim merged 5 commits into
mainfrom
commercial-licensing-terms

Conversation

@asim

@asim asim commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

Publish US$10,000/month commercial terms separately from US$1,000/month support, including a versioned customer agreement and contributor permission status. The proposed source-available runtime licence remains inactive until the necessary rights are confirmed; current AGPL and Apache licences remain authoritative.

Per maintainer instruction, external legal review is not a merge prerequisite. No such review is claimed. The existing merged CLA and contribution process are preserved. Dev9269's scoped permission is recorded; other historical permissions remain pending.

Validation: documentation link checks, git diff --check and the existing proto licence-notice test passed. Documentation only; no runtime or effective licence change. Maintainer explicitly directed merging; no personal CLA acceptance has been fabricated.

asim commented Nov 17, 2026

Copy link
Copy Markdown
Member Author

@kramlipi — thank you for your contribution to Mu. We're requesting your explicit permission to relicense your SQLite test-teardown contribution credited in commit 8300b24 (whose message references #1456; that PR is currently unavailable through GitHub), including the portions retained or modified in later Mu versions.

The proposal is in #2180: future Mu runtime releases would be source-available, free for personal/internal use, with a paid licence required for commercial resale or hosting. Micro would also offer separate proprietary commercial licences. MUCP and the SDKs remain permissively licensed. Existing AGPL grants would remain valid.

If you agree, please reply with the following confirmation (identifying the rights-holding entity if you are acting for one):

I hold the relevant rights, or am authorised by the rights holder, in my contribution identified above. I grant Micro XYZ Ltd a worldwide, perpetual, irrevocable, non-exclusive, royalty-free copyright licence to use, reproduce, modify, distribute and sublicense that contribution and derivative works as part of Mu under the proposed Mu Runtime Licence and under separate proprietary commercial licences, including granting customers rights to modify, redistribute and provide hosted services. This is an additional permission; it does not revoke existing AGPL grants or transfer my copyright.

This request concerns only the identified contribution, not future contributions. Attribution will be preserved. If any portion belongs to an employer, co-author or another party and you cannot grant permission for it, please identify that limitation instead. If you would prefer a separate agreement or do not agree, please say so; silence will not be treated as consent.

For reference, the current draft is Mu Runtime Licence draft 1.0.

@asim
asim marked this pull request as ready for review November 17, 2026 14:35
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-17T14:36:07.019570Z 0f8a00d Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@asim asim changed the title Define Mu commercial licensing and draft runtime terms Publish commercial licensing terms and permission status Nov 17, 2026
@asim
asim merged commit 013177b into main Nov 17, 2026
1 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant