Skip to content

COMMERCIAL-LICENSING.md

Latest commit

 

History

History
78 lines (51 loc) · 3.68 KB

COMMERCIAL-LICENSING.md

File metadata and controls

78 lines (51 loc) · 3.68 KB

WiSpec — Commercial Licensing

Overview

WiSpec is released under a source-available noncommercial license (see LICENSE.md). Commercial use requires a separate paid license.

What Counts as Commercial Use?

Any use that is primarily intended for or directed toward commercial advantage or monetary compensation. Examples include:

  • Integrating WiSpec code, methods, or trained models into a commercial product or service
  • Using WiSpec for paid consulting, analytics, or sensing services
  • Internal use at a for-profit company where WiSpec contributes to revenue-generating operations
  • Reselling or sublicensing WiSpec or derivative works
  • Using WiSpec outputs (e.g., trained classifiers, processed datasets) in commercial offerings
  • Government or defense contractors using WiSpec in contract-funded work (case-by-case; contact Author)

What Is NOT Commercial Use?

  • Academic research at universities or nonprofit institutions
  • Student projects, theses, and coursework
  • Personal learning and experimentation
  • Publishing research papers that cite WiSpec
  • Noncommercial open-source projects that maintain the same license

Commercial License Options

Option A: Per-Project License

A one-time fee for a specific, defined commercial use case. Covers a single product, service, or project. Scope, term, and deliverables negotiated individually.

Option B: Enterprise License

An annual license for unlimited internal use within a single organization. Covers all employees and projects. Includes priority support and consultation.

Option C: OEM / Embedded License

For companies embedding WiSpec methods or code into a product shipped to end users. Royalty-based or flat-fee structure negotiated individually.

Pricing

Pricing is negotiated on a case-by-case basis. Factors include:

  • Scope of use (single project vs. enterprise-wide)
  • Revenue scale of the commercial application
  • Whether the license includes support, consultation, or custom development
  • Duration of the license

For academic spinoffs and early-stage startups, reduced rates or deferred-payment arrangements may be available.

How to Obtain a Commercial License

  1. Email chatgpt@asu.edu with:
    • Your name and organization
    • A brief description of the intended commercial use
    • Approximate timeline and scope
  2. I will respond with a proposed license structure and pricing.
  3. A formal license agreement will be drafted and signed before any commercial use begins.

Revenue Share / Royalties

Some commercial licenses may include a revenue-share or royalty component. Note the following:

  • Revenue-share terms must be specified in a signed contract (not just a repo license file).
  • Repo-level license files are not generally sufficient to create enforceable royalty obligations. A separate contract is needed.
  • Enforcement of royalty clauses requires monitoring and audit rights, which must be defined in the contract.
  • This is an area where you should consult a lawyer before finalizing terms. I am not a lawyer; the license and terms in this repository are a good-faith starting point, not a substitute for legal counsel.

Important Disclaimers

  • This document describes the Author's licensing intentions and is provided for informational purposes.
  • The binding legal terms are in LICENSE.md and any separately executed commercial license agreement.
  • Nothing in this document constitutes legal advice. If you have questions about whether your use qualifies as commercial, contact the Author.
  • The Author reserves the right to modify commercial licensing terms at any time. Existing signed agreements are not affected by such changes.

Contact: Abhinav Ranish — chatgpt@asu.edu