Skip to content

COMMERCIAL_LICENSE.md

Latest commit

 

History

History
219 lines (152 loc) · 5.91 KB

COMMERCIAL_LICENSE.md

File metadata and controls

219 lines (152 loc) · 5.91 KB

Commercial License Information

DevOps.JSON Viewer - Commercial Licensing

Copyright © 2025 Mohammad Hossein Dokht Esmati Contact: desmati@gmail.com

📋 Overview

This software is distributed under a dual licensing model:

  1. Open Source License: GNU Affero General Public License v3.0 (AGPL-3.0)
  2. Commercial License: Available upon request and approval

💼 When Do You Need a Commercial License?

You need a commercial license if you want to:

✗ Use in Proprietary/Closed-Source Software

  • Incorporating this code in software you don't release as open source
  • Using in internal company tools without publishing source code
  • Building commercial products without AGPL-3.0 licensing

✗ Commercial Products or Services

  • Using in SaaS (Software as a Service) platforms
  • Embedding in commercial applications
  • Selling or licensing derivative works
  • Using in paid products or services

✗ Internal Commercial Use

  • Using within a commercial entity for internal purposes
  • Corporate/enterprise internal tooling
  • Commercial consulting or development services

✗ Avoid AGPL-3.0 Obligations

  • If you cannot or do not want to:
    • Make your entire project open source under AGPL-3.0
    • Publish your source code publicly
    • Comply with copyleft requirements

✓ When Is a Commercial License NOT Required?

You can use the software under AGPL-3.0 (no commercial license needed) if:

  • ✓ Your entire project is open source under AGPL-3.0 or compatible license
  • ✓ You publish all your source code publicly
  • ✓ You comply with all AGPL-3.0 requirements
  • ✓ Personal, educational, or research use (with open source compliance)

🤝 How to Obtain a Commercial License

Step 1: Contact

Email: desmati@gmail.com

Subject: "Commercial License Request - DevOps.JSON Viewer"

Step 2: Provide Information

Please include:

  1. Your Information:

    • Name / Company name
    • Contact details
    • Country/Region

  2. Use Case:

    • How you plan to use the software
    • Type of product/service
    • Scale of deployment (users, installations, etc.)

  3. Duration:

    • One-time use
    • Temporary (specify duration)
    • Perpetual license

  4. Scope:

    • Which parts of the code you need
    • Single product or multiple products
    • Distribution plans

Step 3: Review and Negotiation

The copyright holder will review your request and may:

  • Grant permission for free (at sole discretion)
  • Grant temporary permission
  • Negotiate licensing terms
  • Request payment for commercial use rights

Step 4: Agreement

If approved, you will receive:

  • Written permission (license agreement)
  • Terms of use
  • Any applicable fees or conditions
  • License duration and scope

💰 Pricing

Commercial licensing fees are determined on a case-by-case basis considering:

  • Size of your organization
  • Scale of deployment
  • Revenue generated from the product
  • Geographic reach
  • Duration of license
  • Support requirements

Note: The copyright holder reserves the right to:

  • Grant free licenses at their discretion
  • Decline commercial license requests
  • Set pricing based on the specific use case

⚖️ License Terms

Commercial licenses typically include:

What You Get:

  • ✓ Right to use the code in proprietary software
  • ✓ No obligation to publish your source code
  • ✓ No AGPL-3.0 copyleft requirements for your project
  • ✓ Commercial distribution rights (as specified)
  • ✓ Specified duration of use

What You Don't Get (unless explicitly included):

  • ✗ Source code ownership (copyright remains with author)
  • ✗ Right to sublicense
  • ✗ Warranty or liability coverage
  • ✗ Ongoing support (unless separately negotiated)
  • ✗ Future updates (unless separately negotiated)

Standard Restrictions:

  • Must comply with agreed-upon terms
  • Cannot remove copyright notices
  • Cannot claim authorship
  • Must use only as specified in agreement

⏰ Duration Options

Commercial licenses may be granted as:

  1. Perpetual: One-time fee, use forever (within scope)
  2. Time-Limited: Annual, monthly, or custom duration
  3. Project-Specific: For a specific product/version
  4. Temporary: For evaluation or specific events

🔄 License Modifications and Updates

  • License terms can be renegotiated upon mutual agreement
  • Updates to the software may require license renewal
  • Breaking changes may affect commercial license terms
  • Consult with the copyright holder for clarifications

📞 Support and Customization

Commercial license holders may request (separately negotiated):

  • Technical support
  • Custom modifications
  • Training and documentation
  • Integration assistance
  • Priority bug fixes

These services are not included by default and require separate agreements.

⚠️ Compliance and Enforcement

Important:

  • Using the software commercially without a proper license is copyright infringement
  • The copyright holder reserves the right to audit usage
  • Violations may result in legal action
  • Retroactive licensing fees may apply for unauthorized use

If you're unsure whether you need a commercial license, please contact us for clarification.

📧 Contact Information

Mohammad Hossein Dokht Esmati Email: desmati@gmail.com

Response Time: Typically within 3-5 business days

Languages: English, [Add other languages if applicable]

🙏 Why Dual Licensing?

This dual licensing model allows:

  1. Open Source Community: Free use for open source projects, promoting collaboration and innovation
  2. Commercial Entities: Flexibility to use in proprietary products while compensating the developer
  3. Sustainable Development: Revenue from commercial licenses supports ongoing maintenance and improvements

Your support through commercial licensing helps ensure the continued development of this software.

Thank you for respecting the license terms and supporting open source development!