Commit

4c91c74

How do you handle licensing for paid Composer packages? I want a **single license to work on only one system** — either local or production server, not both. One license = One active installation. What's the best way to enforce this without API calls from the package itself?

Jérôme Tamarelle @GromNaN14h48c1ada

Private Packagist is made for that.

For Vendors

Unique Composer repository URL and authentication token per customer
Grant customers access to individual packages
Restrict package access by version constraint or timeframe to match your licensing model
Granular per-customer version specific install statistics
You can opt out of the core features for everyone if you require exclusively the vendor features. Additional users are then free, and you only pay the base plan plus your customers.

https://packagist.com/pricing

Er Amit Gupta @eramitgupta12h

how do you handle licensing for the paid Inertia UI package? Is one license restricted to a single installation or can it be used on both local and production environments?

12:24 · Nov 13, 2026commit 4c91c74