Blog··7 min read

AGPLv3, Open Source and Commercial Editions: Understanding the Tradeoffs

DarkMoon Community is AGPL-3.0, Pro is commercial. What each side gains and gives up, where the edition boundary sits, and what the AGPL does not require.

DarkMoon research series·D. Open source & licence·Article 19 of 23·All 23 articles

Not legal advice. The LICENSE text applies. DarkMoon's LICENSING.md and its contributor agreements are drafts under review by counsel at the time of writing.

Introduction

The previous article in this series, Why DarkMoon Community Is Moving from GPLv3 to AGPLv3, described the licence change and its exact status. This one looks at the model around it: an open-source edition under the AGPL-3.0, DarkMoon Community, and a separate commercial product, DarkMoon Pro. Such models are common and also contested. We try to state plainly what each party gains and what it gives up, without presenting the model as free of cost for anyone.

Problem

Three questions come up repeatedly about AGPL-plus-commercial models:

  1. Does the AGPL push users towards the paid edition? It is sometimes described that way.
  2. What does a contributor give, and to whom? If the company can sell what the community writes, the exchange must be explicit.
  3. Where is the line between editions, and is the open edition a crippled demo?

Methodology

We answer from three public sources only: the licence texts, DarkMoon's LICENSING.md, and the code and research records of the Community edition. Where something is a draft or a plan, we say so.

What the AGPL requires, and what it does not

The AGPL-3.0 gives everyone the rights to run, study, modify and share the software. It adds obligations in two cases: when you distribute the program, and when you let users interact remotely over a network with a modified version (section 13). In both cases the obligation is the same: make the corresponding source available under the AGPL-3.0.

It does not:

  • restrict who may use the software or for what purpose, including commercial use at any scale;
  • require payment;
  • require buying DarkMoon Pro, or any other product.

A company can use DarkMoon Community indefinitely, commercially, as long as it respects the licence. DarkMoon Pro is bought for its own features and support, not as a way out of the AGPL.

Where the edition boundary sits in the code

The boundary is documented in the attack-paths research repository and visible in the public code. Both editions share the attack-path schema and engine modules; Community forces off the server-side execution ledger and withholds agent-written evidence text from the engine.

Diagram. Figure 1. Edition boundary, simplified from diagrams/05-community-vs-pro. Community scope as listed in LICENSING.md; Pro features as listed in the public README.
Figure 1. Edition boundary, simplified from diagrams/05-community-vs-pro. Community scope as listed in LICENSING.md; Pro features as listed in the public README.

A design consequence worth stating: Community never labels an attack path as evidence-backed, because it lacks the server-side records that would justify it. The open edition gives a weaker claim, not a fake one (VERIFIED, ADR-A11; real DVGA campaign on Community: 68 findings, 17 paths, 0 proven, EXP-060).

Real results: the tradeoffs, party by party

PartyGainsGives up or accepts
User running DarkMoon for itselffull source, free use, no obligation when it only runs the softwarenothing new compared with the GPL
Service operator (MSSP, consultant) with a modified DarkMoon that clients use remotelythe right to build a service on the codemust offer those clients the source of the modified version; cannot keep improvements private while serving them over the network
Service operator with an unmodified DarkMoonsame as abovekeep the licence notices; no further source obligation beyond what the program already offers
Contributorcode stays open in Community; ASC commits (in the draft CLA) that every contribution it includes in the open-source edition stays available under an open-source licenceonce the CLA is in force, grants ASC the right to also offer the code under commercial licences; this asymmetry is the core of the deal
ASC (publisher)network reciprocity from competitors who host modified forks; the option to sell commercial licences for code it holds rights tosome organisations avoid AGPL code by policy; contributions need a CLA to be reusable commercially; earlier outside contributions are excluded from commercial licences unless their authors agree (LICENSING.md)
Organisation that wants to embed DarkMoon without AGPL obligationsmay ask ASC for a commercial licence, an option, never an obligationpays for that licence; it covers only code ASC holds rights to

Two points deserve emphasis.

The CLA asymmetry is real. Under a CLA, the company can do something with contributions that contributors cannot do with the company's code: relicense it commercially. DarkMoon's draft answers with a commitment that included contributions stay available as open source. Whether that balance is acceptable is each contributor's decision. Today the question is open in practice: the CLA and the Corporate CLA are drafts and cannot be signed yet, and new contributions are accepted under the AGPL-3.0 only.

Earlier code is unaffected. Releases up to v1.6.0 and contributions made before the switch remain GPL-3.0. Nobody who relied on the GPL loses anything.

Limits

  • Not legal advice. Whether a deployment is « remote network interaction » with a modified version depends on facts. Example: a provider that runs a modified DarkMoon itself and gives clients only reports should check its situation with counsel; this article cannot decide it.
  • Drafts. LICENSING.md, the CLA and the Corporate CLA may change after legal review; no AGPL release has been tagged yet.
  • Third-party components keep their own licences. The toolbox bundles separate programs under various licences (some with their own terms for commercial use), and the OpenCode fork stays under its MIT licence. The AGPL of DarkMoon's own code does not change them.
  • Trademarks are separate. Forks and services built on the code must not present themselves as the official DarkMoon product.
  • The research repository linked here is technical context, not legal authority. It documents the edition boundary in code; it does not interpret the licence.
  • No measurement. We have no data on how the change affects contributions, adoption or forks. Any such effect is not measured.

Figures

  • Figure 1 (Mermaid): edition boundary, derived from a diagram checked against Community commit 10eaab0 in the research repository.
DarkMoon Terminal Explorer in the open-source Community edition, Workspace tab, on lab campaigns against intentionally vulnerable training apps: totals (188 findings, 115 exploited, 36 critical, 24 attack paths, 0 evidence-backed), recent campaigns and projects, an executive panel with a rated Cyber Score of E 0/100 and the first treatment actions, and a severity breakdown of the selected campaign.
Figure 2. DarkMoon Community: the open-source Terminal Explorer reads a local store and reports 24 attack paths, 0 of them evidence-backed, a weaker claim rather than a fake one. Lab data from intentionally vulnerable training apps.Captured 20 November 2026 from the Terminal Explorer (current interface).
DarkMoon Pro campaign map on an anonymised real OWASP Juice Shop campaign: the campaign header card above 30 assets grouped into Internet, Edge, Application and Data zones, wired with edges labelled contains, stack, endpoint, runs and root, with the finding count on each asset (47 on the Juice Shop application).
Figure 3. DarkMoon Pro, the commercial edition: the web dashboard with its campaign map, 30 assets in Internet, Edge, Application and Data zones with labelled edges and per-asset finding counts, a view the Community edition never shows. Anonymised real OWASP Juice Shop campaign of 26 April 2026 (demo.dark-moon.org).Captured 21 November 2026 from demo.dark-moon.org (current interface).

Sources (verified)

All pages fetched on 2026-11-20.

Research, source code & reproducibility

Related reading: Why DarkMoon Community Is Moving from GPLv3 to AGPLv3 · Building DarkMoon in the Open: Research, Benchmarks, Failures and Reproducibility · Declared vs Proven Attack Paths: A Practical Evidence Model


If a part of this model is unclear or seems unfair to you, say so in an issue on ASCIT31/Dark-Moon. For your own situation, ask your own lawyer.

Next
Run it against your own lab

Darkmoon is open source (AGPL-3.0) and self hosted. Clone it, point it at a target you own, and read every line.