# DSCC Commercial License

DSCC is dual-licensed:

1. **Open source track:** GNU Affero General Public License v3.0 (AGPL-3.0-only).
   See [`LICENSE`](LICENSE) for the full text. Using, modifying, or distributing
   DSCC under this track binds you to the AGPL-3.0-only terms, including the
   network-use disclosure requirement.

2. **Commercial track:** a separate, negotiated commercial license is available
   for organizations whose distribution model cannot accommodate AGPL-3.0-only.

## When you need a commercial license

You likely need the commercial track if any of the following apply to your use
of DSCC:

- You want to embed DSCC in a proprietary product you distribute to end users
  or expose as a hosted/SaaS service, without releasing your service code under
  AGPL-3.0-only.
- You want to modify DSCC internally and are unwilling or unable to offer the
  corresponding source of your modifications to your users over a network.
- Your compliance, procurement, or legal review process rejects AGPL-3.0-only
  as a dependency license.

If none of the above applies — for example, you are using DSCC personally,
evaluating it, or building an open-source project that is compatible with
AGPL-3.0-only — the open-source track is sufficient and no commercial license
is needed.

## How to request a commercial license

Commercial-license inquiries are handled through GitHub Issues on the DSCC
repository:

1. Open an issue at `https://github.com/oMygpt/dscc/issues` with the title
   `Commercial license inquiry`.
2. Include:
   - Organization name and website
   - Primary contact (name and email)
   - Brief description of the intended use (deployment model, rough scale,
     whether DSCC will be redistributed or only run internally)
   - Whether you need attribution customization, SLAs, or custom support terms
3. A maintainer will respond with next steps, including the pricing model,
   scope of the grant, and a proposed agreement.

Because the commercial terms are negotiated per-engagement, there is no public
price list and no click-through purchase flow. The GitHub Issue is the entry
point and is used to establish contact; the actual contract is executed off of
GitHub.

## What the commercial license grants (summary)

The negotiated commercial license typically grants:

- The right to use, modify, and redistribute DSCC as part of a proprietary
  product or service without the AGPL-3.0-only source-disclosure obligations.
- Optional support and security-advisory channels for the term of the license.
- Optional trademark or attribution customization, subject to mutual agreement.

The exact scope, term, and fees are defined in the executed commercial
agreement, which supersedes this document for licensees on the commercial
track.

## Contributions

Contributions to DSCC are accepted under the AGPL-3.0-only track by default.
If you want your contribution to also be available under the commercial track,
say so explicitly in your pull request so the maintainers can coordinate the
dual-grant with you before merging.
