Licensing
PAM 0.1.1, PAM Native, PAM Mobile UI, and the first-party server packages are source-available under the Business Source License 1.1 (BUSL-1.1).
The complete LICENSE file in each repository controls. This page is an explanatory summary and is not legal advice.
Applications built with PAM
Section titled “Applications built with PAM”The Additional Use Grant permits production use for purposes other than a competing use.
You may use PAM without a PAM commercial license to:
- build, operate, market, and sell proprietary or open applications;
- run internal systems and commercial SaaS products;
- distribute mobile, desktop, and web applications built with PAM;
- provide paid development, consulting, hosting, support, and training; and
- create plugins, components, integrations, and tools that work with PAM without replacing it.
There is no stated revenue, company-size, seat, or application royalty limit.
Application code authored against PAM’s public interfaces belongs to its author and may use other terms. The same application-output grant covers code emitted by PAM generators and application files copied from pam/skeleton.
That grant does not apply to copied or modified portions of PAM’s runtime, framework, developer platform, or UI engine.
Competing use
Section titled “Competing use”A commercial license is required for production use in a product or service whose primary purpose is to substitute for PAM as an application development framework, developer platform, runtime environment, or UI engine.
A rebranded or repackaged standalone PAM distribution is included in this restriction.
The BSL base terms still permit copying, modification, derivative works, redistribution, and non-production use, subject to the controlling license.
Change license
Section titled “Change license”For PAM 0.1.1, the published Change Date is July 23, 2030. On the Change Date—or the fourth anniversary of the first public distribution of a specific version if earlier—that version changes to Apache License 2.0.
The BSL applies separately to each version, so future releases must publish their own applicable Change Date.
PAM Desktop
Section titled “PAM Desktop”PAM Desktop and its pam/desktop Composer package are currently MIT licensed.
Servo and every other third-party dependency retain their own license terms and notices.
Existing releases
Section titled “Existing releases”A later licensing change does not retroactively revoke rights already received for a copy released under another license.
Before public release
Section titled “Before public release”The project documentation itself notes that Pushin should have the licensor identity, copyright ownership, contributor agreements, Additional Use Grant, trademark policy, and bundled third-party notices reviewed by qualified counsel before public release.
For a use case near the competing-use boundary, rely on the controlling license and obtain legal advice or a commercial license clarification from Pushin.