Enterprise

White-label deployment console

Prepare brand, domain and license metadata for an enterprise static package.

White-label compiler input

Brand nameAuthorized domainLogo path

enterprise.config.json

{
  "brand": "Acme Docs",
  "domain": "docs.acme.com",
  "logo": "/logo.svg",
  "slogan": "Private browser-local PDF tools",
  "cloudflare": {
    "pagesProject": "acme-docs",
    "workerName": "acme-docs-api"
  },
  "license": {
    "allowedHosts": [
      "docs.acme.com"
    ],
    "expiresAt": "2027-12-31T23:59:59.000Z"
  }
}

This page exposes the configuration surface. The actual one-command enterprise deployment still requires a signed license generator and Cloudflare credentials in the customer's environment.

License validation is local; signing keys must stay outside the public frontend.

User guide

How to use White-label Deployment

Generate a branded static build from approved customer configuration and deployment settings.

1
Create a customer configuration with brand name, colors, logo, domains, and enabled tools.
2
Validate asset paths and signed license data.
3
Run the enterprise build and inspect the generated static package.
4
Deploy to the customer-controlled account and perform acceptance tests.

Best for

Private enterprise branding
Customer-controlled static deployments

Important limitation

Client-side license checks can be bypassed by a determined operator. Commercial enforcement also needs contracts, signed releases, support controls, and secure key management.

Frequently asked questions

Can a front-end license be unbreakable?

No. Public client code can be inspected; signatures prevent forgery but cannot prevent all bypasses.

Who controls the Cloudflare account?

The intended private deployment uses the customer's own account and credentials.

PDFPerch processes files locally unless this guide explicitly identifies a cloud-dependent feature. Always keep an original copy and verify critical output before submission, printing, signing, or accounting use.