Skip to content
Pricing
PlaygroundPaste a payload and download native PPTX, DOCX, XLSX, or PDF.PricingFree lite engines plus Pro, All Formats, and Enterprise plans.Free vs ProFeature-by-feature comparison across all four formats.
BenchmarksStructural validation results, raw artifacts, and public caveats.DocumentationSDK references, API docs, and integration guides.BlogTechnical deep-dives, comparisons, and product updates.
Sign in

Legal

Open-Source and Commercial License Policy

How PaperJSX open-source and commercial components may be used.

Summary

PaperJSX has open-source components and commercial components. Open-source components are governed by their stated open-source license. Commercial components require an active paid entitlement and may not be redistributed, sublicensed, copied into competing products, or used after the entitlement expires. Outputs you generate with PaperJSX are yours.

This summary is not legally binding. The full policy below controls.

1. Scope

This Policy supplements the Terms of Service. If this Policy conflicts with the Terms about Commercial Components, this Policy controls. If an open-source license conflicts with this Policy for an open-source component, the open-source license controls for that component.

2. Definitions

Open-Source Components are PaperJSX packages, repositories, files, examples, or tools that expressly state they are licensed under Apache-2.0 or another open-source license.

Commercial Components are PaperJSX packages, plugins, renderers, templates, private package artifacts, license certificates, commercial CLIs, APIs, documentation, examples, enterprise features, or other materials that are not expressly released under an open-source license.

Outputs are documents, presentations, PDFs, PPTX files, images, HTML, reports, templates generated for your own application, or other artifacts generated through your permitted use of PaperJSX.

3. Open-source license boundary

Open-Source Components are licensed under the open-source license stated in the applicable repository, package, file, or notice. For components released under Apache-2.0, your rights come from Apache-2.0.

These Terms do not restrict your open-source license rights. For example, if a component is expressly released under Apache-2.0, you may use, reproduce, modify, and distribute that component as permitted by Apache-2.0, subject to its conditions.

Commercial Components are not open source merely because they interoperate with, import, extend, or sit next to Open-Source Components.

4. Commercial license grant

During an active paid entitlement, trial, or enterprise term, we grant you a limited, non-exclusive, non-transferable, non-sublicensable, worldwide license to install and use the Commercial Components for your permitted projects under the applicable plan, pricing page, Order Form, or entitlement.

Unless your Order Form says otherwise, permitted use includes:

  • installing Commercial Components in private development, test, build, CI/CD, staging, and production environments;
  • using Commercial Components to generate Outputs for your own products, internal systems, public websites, documentation, reports, customer deliverables, and client projects;
  • allowing your employees and contractors to use Commercial Components for your permitted projects;
  • shipping Outputs generated with Commercial Components to your customers or users;
  • keeping and using Outputs generated during a valid license term after the term ends.

5. Restrictions

Unless your Order Form expressly permits it, you may not:

  • publish, share, sell, resell, sublicense, lease, rent, redistribute, mirror, or make Commercial Components available as source code, object code, package files, package-registry artifacts, templates, private registry mirrors, or downloadable assets;
  • include Commercial Components in an open-source repository or public package registry;
  • expose Commercial Components through a hosted service, SDK, package, library, code-generation platform, template system, document-generation API, or similar tool in a way that gives unrelated third parties direct or substantially equivalent access to the Commercial Components themselves;
  • create, train, benchmark, or commercialize a competing product using Commercial Components, non-public documentation, private package access, or license-system behavior;
  • reverse engineer, decompile, disassemble, copy, scrape, or create derivative works from Commercial Components except to the extent applicable law expressly permits despite this restriction;
  • remove, obscure, alter, or bypass proprietary notices, license checks, usage gates, entitlement checks, or technical restrictions;
  • share license keys, private package tokens, or license certificates outside your organization;
  • use Commercial Components after your subscription, trial, or entitlement expires, except to preserve and use Outputs already generated during a valid term;
  • use Commercial Components in violation of export-control, sanctions, privacy, intellectual-property, or other applicable law.

6. Outputs

You own your Outputs, subject to any rights you or third parties already have in the materials you provide. We do not claim ownership of your Outputs. You may use Outputs commercially, privately, internally, publicly, or for clients.

PaperJSX does not grant you rights to third-party content, fonts, logos, trademarks, datasets, media, templates, or source materials that you include in Outputs. You are responsible for having the rights needed to use and distribute your Outputs.

7. License keys and certificates

Commercial Components may use license keys, signed license certificates, package tokens, or entitlement metadata. License certificates may be validated locally using public-key verification or checked through a PaperJSX license service.

You must protect license keys and private package tokens from unauthorized use. Do not commit them to public repositories or expose them in client-side code where unauthorized parties can reuse them.

We may revoke, rotate, suspend, or replace a license key or entitlement if we reasonably believe it is leaked, compromised, fraudulently obtained, subject to chargeback, used outside the licensed scope, or used in breach of the Terms or this Policy.

8. Expiration and termination

When a commercial entitlement expires or is terminated, you must stop using Commercial Components and delete or stop accessing private package artifacts except as needed to maintain historical build records or comply with legal obligations. Open-source rights continue under the applicable open-source license. You may continue to use Outputs generated during a valid license term.

If you need extended build reproducibility, escrow, long-term support, or air-gapped/offline license rights, those terms must be stated in an Order Form.

9. Third-party components

PaperJSX may include or depend on third-party open-source or commercial components. Your use of third-party components is governed by the applicable third-party licenses and notices. We may provide a third-party notices file or dependency list where appropriate.

10. Audit and verification

We may use technical measures to verify entitlements and prevent license abuse. For enterprise plans, an Order Form may include additional reporting, true-up, or audit terms. We will not access your source code, generated documents, or Customer Content merely to verify a license unless you provide it to us or a hosted feature processes it.

11. Questions

License questions: legal@paperjsx.com Commercial access support: support@paperjsx.com