Licensing

PAM, PAM Native, the first-party Composer packages, examples, and publication metadata are licensed under the Apache License 2.0. PAM Desktop keeps the license declared by its own repository.

The complete LICENSE, NOTICE, and third-party notice files shipped by each repository and release control. This page is a practical summary, not legal advice.

What Apache 2.0 permits

Subject to the license terms, you may:

• use PAM for personal, internal, commercial, or public applications;
• build and sell proprietary software with PAM;
• modify and redistribute PAM;
• create plugins, components, integrations, hosting, support, and training;
• fork the project; and
• include PAM in a larger product or service.

There is no PAM revenue share, application royalty, company-size limit, or seat limit in Apache 2.0.

Your obligations

When you redistribute PAM or a derivative containing PAM code, preserve the license and required notices, mark significant modifications, and follow the Apache 2.0 patent and attribution terms. Third-party dependencies retain their own licenses.

Application code authored against PAM’s public APIs belongs to its author and may use different terms. Generated starter code should retain any notices that the generated files or their source package explicitly require.

Older releases

Licenses are granted per released copy. A later license change does not revoke terms already received with an older release. Consult the LICENSE distributed with the exact version you use.

For unusual redistribution, trademark, or patent questions, rely on the controlling license text and obtain qualified legal advice.