# Commercial License — Star-Magic-Program

## When you need this

The default license is **AGPL-3.0-or-later**. That's the right choice if any
of these describe your use:

- Academic research
- Non-commercial personal projects
- Any project willing to release its modifications back under AGPL-3.0
- Public services willing to make source available to their users (per the
  AGPL network-provision)

You need a **commercial license** if any of these describe your use:

- Distributing a proprietary product that incorporates this framework
- Running a closed-source SaaS or hosted service
- Embedding the framework in reactor firmware, hardware, or other proprietary
  systems
- MIT-, Apache-, or BSD-licensed projects that want to import UQFF code without
  relicensing themselves
- Any use where AGPL-3.0's copyleft or network-provision would create a
  conflict for your business model

## How to obtain a commercial license

Contact: **daniel.murphy00@enrgyone.com**

Include:
- Company / organization name
- Intended use (product, SaaS, hardware, etc.)
- Deployment scale (users, instances, regions)
- Duration (perpetual, subscription, evaluation)
- Any specific carve-outs needed

Terms are negotiated case-by-case.

## Common questions

**Q: Can I evaluate the framework commercially under AGPL first?**
A: Yes, for internal evaluation and prototyping. AGPL kicks in when you
distribute or offer as a service to third parties.

**Q: Do I need a commercial license to publish research using the framework?**
A: No. Academic publication is covered by AGPL. Cite via `CITATION.cff`.

**Q: What about hardware embedding?**
A: Hardware patent licenses are separate from software licenses. Contact
the copyright holder for hardware terms.

**Q: Is there a startup / small-business tier?**
A: Yes — reach out. Terms are flexible for early-stage commercial use.

**Q: What about internal use inside my company?**
A: If you're not distributing the modified software externally and not
running it as a service to third parties, AGPL is fine. Internal use is
generally not a distribution trigger under AGPL.

**Q: Can I fork the repository and add proprietary modifications?**
A: Under AGPL, forks must remain AGPL. Under commercial, terms are
negotiated.
