Commercial Licenses

Commercial licenses let buyers redistribute your package inside their own products.

For Package Authors

To offer commercial licensing, create a pricing plan with the Commercial License flag enabled in Package Settings > Distribution > Monetization.

If any of your pricing plans have commercial licensing enabled, buyers of that plan can bundle your package. If none do, bundling is not available.

For Redistributors

If you want to include a paid LPM package inside your own package:

1. Purchase the commercial license plan from the package author
2. Add the package to both dependencies and bundledDependencies:

{
  "dependencies": {
    "@lpm.dev/acme.ui-kit": "^1.0.0"
  },
  "bundledDependencies": ["@lpm.dev/acme.ui-kit"]
}

The dependency gets physically included in your package tarball. Your users receive it automatically without needing their own license.

Same-owner exception: if you own both the parent package and the dependency (or they belong to the same organization), you do not need a separate commercial license.

Alternative: Peer Dependencies

If you do not want to bundle (or no commercial license is available), list the dependency as a peerDependency:

{
  "peerDependencies": {
    "@lpm.dev/acme.ui-kit": "^1.0.0"
  }
}

Each end user purchases their own license and installs the dependency separately.

License File Template

Marketplace packages should include a LICENSE file with commercial terms. Open-source licenses (MIT, ISC, Apache) allow free redistribution, which conflicts with per-seat pricing.

Below is a ready-to-use template. Copy it into your package's LICENSE file and fill in the placeholders.

LPM Commercial License

Copyright (c) [YEAR] [AUTHOR OR COMPANY NAME]

This software is licensed, not sold. By purchasing a license through
lpm.dev, you receive the rights described below.

1. GRANT OF LICENSE

   (a) Per the license type purchased (Individual or Organization),
       the licensee may install and use this software in any number
       of projects, subject to the seat or organization limits of
       the purchased plan.

   (b) The software may be used in commercial and non-commercial
       projects.

2. RESTRICTIONS

   (a) You may NOT redistribute, sublicense, resell, or share this
       software (in source or compiled form) with anyone who has not
       purchased their own license, unless you hold a Commercial
       License plan that explicitly grants redistribution rights.

   (b) You may NOT publish this software to any public package
       registry (npm, other registries) or make it freely available
       for download.

   (c) You may NOT remove or alter this license notice from any
       copies of the software.

3. COMMERCIAL REDISTRIBUTION

   If you purchased a plan with Commercial License rights enabled,
   you may bundle this software inside your own products using
   bundledDependencies. End users of your product do not need a
   separate license.

4. UPDATES

   License holders receive updates for the duration of their
   subscription (if subscription-based) or for the major version
   at the time of purchase (if one-time).

5. NO WARRANTY

   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
   EXPRESS OR IMPLIED. THE AUTHOR SHALL NOT BE LIABLE FOR ANY CLAIM,
   DAMAGES, OR OTHER LIABILITY ARISING FROM THE USE OF THE SOFTWARE.

6. TERMINATION

   This license terminates automatically if you violate any of its
   terms. Upon termination, you must stop using and delete all
   copies of the software.

Dual Licensing (Open Source + Commercial)

If you want to keep your code open-source on GitHub while selling on the Marketplace, you can dual-license:

• GitHub: MIT, Apache 2.0, or your preferred open-source license (free for community use)
• LPM Marketplace: Commercial license (for teams wanting support, guarantees, or redistribution rights)

Add a note to your README explaining that the LPM version includes commercial license terms, priority support, or other benefits that justify the purchase.