Thank you for considering PSPDFKit for Web. Licensing for PSPDFKit for Web operates on a subscription model, which takes several factors into account such as the operational mode, required components, whether you require headless server-side processing, and the number of users leveraging the technology.
When you purchase a subscription license for PSPDFKit for Web, you’re able to deploy on a given number of agreed-upon domain names. You can set up these domains in the PSPDFKit Customer Portal.
PSPDFKit for Web will verify that the
Origin of the browser tab where it’s used matches the list of allowed domains for your license.
Document Engine pings the PSPDFKit Licensing Service to verify its license and download updated license information.
Document Engine sends anonymous usage analytics to the PSPDFKit Licensing Service. These analytics help us in diagnosing issues and improving the product.
PSPDFKit for Web can be activated with a production or development key. Development mode doesn’t restrict the allowed
If your license agreement differs from the above, then the language of that agreement is binding.
When PSPDFKit for Web Server-Backed is purchased, the Document Engine backend product can only be used in the context of the PSPDFKit for Web product. To use Document Engine with other PSPDFKit products, these products must be licensed as well.
Headless Server-Side Processing
PSPDFKit for Web Server-Backed cannot be used for headless server-side processing unless these headless processing components have been licensed as well.
Components are the smallest licensable part of PSPDFKit, and they come with a set of unique features. When you license a component, you license the component’s entire feature set, regardless of if you use a single component feature or all of them. A full list of licensable components and their features can be found on our features list.
By downloading and evaluating the PSPDFKit SDK demo, you accept the terms of the evaluation license agreement.
To purchase PSPDFKit, a license contract needs to be signed with the company that owns the end product/app. We use DocuSign for a fast and secure digital signing experience. If you require a physical copy of a contract, we can accommodate this need as well. Licensing is done on a per-year basis. It is not possible to change this to a monthly license.
Because PSPDFKit licenses technology to a large number of companies, we need to keep modifications to our contract to a minimum, as modifications incur additional management and reviewing overhead. The quote we send is based on the acceptance of our standard license agreement. We’re somewhat flexible; however, making changes to a contract will take more time and likely increase your cost. As we’re an Austria-based company, the place of jurisdiction is Vienna, Austria.
Setting Up a Domain in Our Customer Portal
When setting up your license using the PSPDFKit Customer Portal, you’ll be asked to assign a web domain to activate your product.
Always make sure to use the exact domain (including any subdomains) your product is using. If your product runs on multiple domains — for example,
board.internal.example.com at the same time — please reach out to us so we can discuss a custom solution.
Updating Your PSPDFKit for Web License
You can safely update your license without updating to the newest PSPDFKit for Web version.
Our license key is an encrypted JSON Web Token (JWT). This is a specially encrypted JSON payload, and the SDK can easily verify offline if it was produced by us and if it’s been tampered with. It allows us to provide details about what you can and can’t do with the SDK.
The way this works is: When you purchase our license, you provide a domain on which you’re deploying your application. This is part of the encrypted information.
The PSPDFKit SDK then checks locally from the browser if it’s been loaded at the same location/domain contained in the license. If so, the key is safe to use, because if someone stole it, they’d only be able to use it at the permitted locations encoded within the key itself. If they tried to change the content to add their own domains, we’d be able to detect it.