|
| 1 | +# Licensing |
| 2 | + |
| 3 | +CodeFRAME is released under the [GNU Affero General Public License v3.0 |
| 4 | +(AGPL-3.0)](LICENSE). This page explains, in plain language, what that means for |
| 5 | +you — and what to do if the AGPL doesn't fit your situation. |
| 6 | + |
| 7 | +> This is a practical summary, not legal advice. The [LICENSE](LICENSE) file is |
| 8 | +> the binding text. When in doubt, consult a lawyer. |
| 9 | +
|
| 10 | +## Why AGPL-3.0 |
| 11 | + |
| 12 | +CodeFRAME is **open core**: the project is fully open source, and we intend to |
| 13 | +keep the core that way. The AGPL is a deliberate choice. It guarantees that |
| 14 | +CodeFRAME — and improvements to it — stay open, including when the software is |
| 15 | +offered to others as a network service. This protects the community from a |
| 16 | +closed fork being run as a competing hosted product without giving anything |
| 17 | +back. |
| 18 | + |
| 19 | +## What it means for you |
| 20 | + |
| 21 | +### Individuals and teams using CodeFRAME |
| 22 | + |
| 23 | +You can **use, run, modify, and self-host** CodeFRAME for any purpose, including |
| 24 | +commercial work, at no cost. If you run it for yourself or your team and don't |
| 25 | +distribute it or offer it to outside users as a service, the AGPL asks nothing |
| 26 | +further of you. Use it freely. |
| 27 | + |
| 28 | +### Companies using it internally |
| 29 | + |
| 30 | +The same applies to internal company use. Running CodeFRAME on your own |
| 31 | +infrastructure to deliver software for your own organization is fine and creates |
| 32 | +no source-disclosure obligation, even if you modify it — as long as those |
| 33 | +modified versions are not conveyed to outside parties or exposed to outside |
| 34 | +users over a network. |
| 35 | + |
| 36 | +### Companies offering it to others (the AGPL trigger) |
| 37 | + |
| 38 | +The AGPL's defining clause is **Section 13**: if you run a modified version of |
| 39 | +CodeFRAME and let users interact with it **over a network** (for example, a |
| 40 | +hosted SaaS built on or embedding CodeFRAME), you must offer those users the |
| 41 | +**complete corresponding source code** of your modified version, under the |
| 42 | +AGPL. The same applies if you distribute CodeFRAME or a derivative work: the |
| 43 | +recipient gets the source under the AGPL. |
| 44 | + |
| 45 | +In short: |
| 46 | + |
| 47 | +| Your situation | AGPL obligation | |
| 48 | +| ----------------------------------------------------------- | ------------------------------------------------ | |
| 49 | +| Run it for yourself / your team, unmodified or modified | None beyond keeping the notices | |
| 50 | +| Internal company use, not exposed to outside users | None beyond keeping the notices | |
| 51 | +| Offer it (or a derivative) to outside users over a network | Publish your complete source under AGPL-3.0 | |
| 52 | +| Distribute it or embed it in software you ship | Recipients get source under AGPL-3.0 | |
| 53 | + |
| 54 | +## Commercial licensing and hosted offering (planned) |
| 55 | + |
| 56 | +If the AGPL's network-source-disclosure requirement doesn't work for your |
| 57 | +business — for example, you want to **embed CodeFRAME in a closed-source |
| 58 | +product** or offer a hosted service **without** publishing your modifications — |
| 59 | +we plan to offer: |
| 60 | + |
| 61 | +- **Commercial / OEM licenses** that release you from the AGPL's copyleft |
| 62 | + obligations for embedding and redistribution. |
| 63 | +- A **hosted CodeFRAME** offering for teams that would rather not self-host. |
| 64 | + |
| 65 | +Pricing and terms are still being finalized, but the path exists. If you have a |
| 66 | +commercial need, **tell us now** — early conversations shape what we build. |
| 67 | + |
| 68 | +## Get in touch |
| 69 | + |
| 70 | +- **Commercial licensing / OEM / hosted interest:** start a thread in the |
| 71 | + [**Commercial & Licensing** discussion](https://github.com/frankbria/codeframe/discussions) |
| 72 | + (look for the pinned *Early access & commercial interest* post) so we can |
| 73 | + follow up. This is the capture point for launch — even before pricing is |
| 74 | + published. |
| 75 | +- **Design partners & early access:** the same pinned discussion is where we |
| 76 | + collect early-access signups. Reply there to be included. |
| 77 | + |
| 78 | +We read every one. |
0 commit comments