License the pdff PDF Engine

1. What is being licensed

The Service is built on a complete, production-hardened PDF engine that executes in the browser: 23 tools covering merge, split, rotate, crop, compress, OCR, redact, annotate, sign, form-fill, page-number, metadata and conversion, with no server component, no file upload, and no per-user operating cost.

If your product needs PDF capability, adopting this is usually faster and cheaper than building it, and the architectural advantages below are difficult to replicate.

2. Why the client-side architecture is commercially valuable

• No server cost per user. Your margin does not degrade as volume grows. This is the single most important commercial property of the design.
• No document ever reaches your infrastructure. This removes an entire category of compliance conversation, breach risk, and infrastructure cost.
• Works offline once the page has loaded.
• Deployment is a static bundle. No container orchestration, no job queue, no file store, no worker fleet.
• No document storage means no storage compliance burden, no data residency question, and no retention policy to write.

3. Licensing options

No price is published. Pricing depends on scope, support commitment, volume, and exclusivity, and is quoted in writing rather than listed on a page.

4. What a licence would include

• Use in commercial products, including paid tiers, subject to the scope agreed.
• Permitted modifications, including your own interface and branding.
• Fixes and updates for the period covered by the agreement.
• A defined support channel and response expectation.

5. Expected restrictions

Any licence granted would be expected to include limits that protect the integrity of the work, subject to negotiation:

• No false capability claims. You may not advertise encryption, secure redaction, certified digital signatures, or legal compliance unless the licensed software genuinely delivers it. Redaction does not remove underlying text; the digital signature is not certificate-based. Advertising either as though it does would expose you to liability under consumer protection law.
• No fabricated reviews or ratings in any listing, marketplace, or search result.
• Attribution where the licence is not white-label.
• No warranty passthrough beyond what is actually delivered.

The restriction on false claims is not a negotiating position to be traded away. It is the reason this project removed its own fabricated ratings, and it will not be re-introduced through a licensee.

6. Open-source position

The public repository referenced in the About page is available for inspection. The Operator does not represent that the source is published under a permissive open-source licence granting unrestricted reuse rights. If you need reuse or modification rights, that must be the subject of a licence agreement.

Inspecting public source is encouraged. Reusing it without permission is not authorised.

7. Enquiries

Email accts.pak@gmail.com with "Licensing" in the subject, and include:

• What product you are embedding this into.
• Whether it should be branded as your own or attributed.
• Which of the 23 tools you actually need.
• Whether your users need file uploads, or strictly local processing.
• Volume, support, and any exclusivity expectations.

The Operator replies within a few working days. Queries receive an honest answer about feasibility, including where the answer is that licensing is not the right approach for your requirement.

These pages describe capability and enquiry terms only. No paid tier is currently offered on https://pdff.online itself.