Licensing & Intellectual Property Framework

• Core Principle
• Licensing Models
• Open Source & Community Licensing Models
• Licensing vs Royalties

Core Principle

Developers retain ownership of their intellectual property unless contractually agreed otherwise.

THiNK acts as:

• Deployment platform

• Validation layer

• Commercialization ecosystem

• Pilot environment

 

Licensing Models

Community Use License

THiNK receives non-exclusive usage rights.

Commercial License

THiNK may commercially deploy the solution.

White-Label/OEM License

THiNK may rebrand and deploy the solution.

API Usage License

Solutions are monetized through API consumption.

Dual Licensing

Community + commercial licensing structure.

Exclusive Licensing

Strategic or sector-specific exclusivity.

 

Open Source & Community Licensing Models

NOODL License

A collaborative innovation licensing philosophy emphasizing:

• Shared innovation

• Ecosystem participation

• Contributor recognition

• Local adaptation

Esethu License

A collective-benefit licensing philosophy emphasizing:

• Ethical reuse

• Shared social impact

• Community ownership values

• Public-interest infrastructure

Creative Commons Stack

CC BY

Reuse with attribution.

CC BY-SA

Reuse with attribution + same-license sharing.

CC BY-NC

Non-commercial reuse only.

CC BY-NC-SA

Non-commercial + share-alike.

CC0

Public domain dedication.

Open Source Software Licenses

MIT License

Permissive commercial reuse.

Apache 2.0

Enterprise-friendly with patent protections.

GPL

Requires derivative works to remain open source.

 

Licensing vs Royalties

 License

Defines legal permission to:

• Use

• Modify

• Deploy

• Commercialize

A license does not automatically imply payment.

Royalty

A royalty is a payment mechanism attached to licensing.

Examples:

• Revenue share

• API usage fees

• Per-client licensing

• Recurring payments