Branding

Branding

At a glance

The branding subsystem applies visible evaluation branding to generated PDFs during an evaluation and applies nothing under a paid license. It is delivered in the nextpdf/enterprise package, governs evaluation behavior across editions, and is driven entirely by the license — not by application code. For the end-to-end evaluation story, see Trial and Evaluation Branding; this page documents the branding subsystem itself.

Install

composer require nextpdf/enterprise:^3

Conceptual overview

The runtime has a branding mode with two states, modeled by BrandingMode:

• None — no evaluation branding. Paid and normal output is never modified. This is the default.
• EvaluationWatermark — visible evaluation branding is applied to generated PDFs.

BrandingStrategyFactory maps the mode to a strategy: NullBrandingStrategy for None (it performs no work and produces no modification) and EvaluationBrandingStrategy for EvaluationWatermark. The license state — not application code — selects the mode. A paid license never produces branded output, and there is no production build to switch and no code flag to flip.

This page describes runtime behavior only. It makes no warranty and no statement about eligibility or legal effect; the terms that apply to your evaluation or subscription are defined solely by your license agreement.

API surface

Concept	Behavior
BrandingMode	Two states: None (default, no modification) or EvaluationWatermark.
BrandingStrategyFactory	Resolves a BrandingMode to a strategy.
EvaluationBrandingStrategy	Applies the evaluation watermark and metadata decoration.
NullBrandingStrategy	No-op strategy for paid / normal output.
EvaluationBrandingConfig	Immutable watermark text, metadata decoration, font size, gray level, and angle.

The branding subsystem ships in the nextpdf/enterprise package under the enterprise.branding capability code and governs evaluation behavior across editions. It is documented here at the behavior level and is driven entirely by the license.

There is no callable application API to invoke: the branding mode is selected by the license envelope, not by application code, so this page omits the Code sample — Quick start / Code sample — Production sections that callable-API references carry. The only actionable configuration is installing the package and the license; the deterministic-build front matter below shows how to assert no-branding output in a reproducibility profile:

# Front matter for a reproducible (no-evaluation-branding) build profile.
# BrandingMode::None is the default; a paid license keeps it None.
reproducibility_profile: structural
branding_mode_expected: none   # assert null strategy: no watermark, no metadata markers

What evaluation branding does

When the active license selects EvaluationWatermark, the evaluation strategy:

• draws a light-gray diagonal watermark text on each page, rendered as a page content stream in an isolated graphics state so it does not alter surrounding content or your layout;
• appends an evaluation suffix to the document’s producer metadata;
• prepends an evaluation prefix to the document’s subject metadata.

The watermark uses a Base14 font and a rotation matrix to position the text diagonally across the page center. The configuration object is immutable and validates its inputs (for example, watermark text cannot be empty and font size must be positive).

How a paid license removes branding

Under a paid (non-evaluation) license the branding mode is None and the null strategy is selected: no watermark, no producer suffix, no subject prefix. Output is identical to output produced with no branding subsystem at all. Removing evaluation branding requires no code change — install a paid license and the next generated document is unbranded.

Edge cases & gotchas

• Branding appears when the license state is evaluation-style. This reflects the license state, not a defect; check license status and renew through the license portal.
• The watermark is centered and diagonal by design so evaluation output is unambiguous; it is not intended to be tuned for production. A paid license removes it entirely.
• Producer and subject metadata carry evaluation markers during an evaluation and are absent under a paid license.

Performance

The watermark is a small, fixed per-page content stream with negligible impact on generation time or document size. Under a paid license the subsystem performs no work. The page performance budget reflects documentation rendering.

Security notes

Evaluation branding is a visibility marker, not a security control. It indicates evaluation output. It is not a digital signature and must not be relied on as one. For tamper-evident output, use the signing capabilities described in the feature matrix. The license that selects the branding mode is a signed envelope whose issuer signature the runtime verifies.

Data residency & PII mitigations

The branding subsystem adds a fixed watermark and metadata markers; it does not read or transmit document content and makes no network calls.

Safe telemetry & log scrubbing

The subsystem does not log document content. License-state transitions that change the branding mode are surfaced through the licensing subsystem, not here.

Conformance

No standards conformance is claimed for this page. It describes runtime behavior only. It does not state or imply any warranty, certification, or eligibility. The terms of your evaluation or subscription are defined solely by your license agreement.

FIPS-mode behavior

This module performs no cryptographic operations. License signature verification is handled by the licensing subsystem.

Threat model

The branding subsystem itself processes no external input beyond the resolved branding mode. The license envelope that selects the mode is signed and its issuer signature is verified by the runtime; spoofing the mode would require forging that signature.

Commercial context

Evaluate the complete feature set with evaluation branding, then remove the branding by installing a paid license — no code changes, no separate build. See Trial and Evaluation Branding for the full evaluation lifecycle. To start an evaluation, visit the license portal.

Edition gate

This subsystem ships in the NextPDF Enterprise package under the enterprise.branding capability code and governs evaluation behavior across editions. Its mode is selected by the license, not by application code. Get a license.

License feature flag

This subsystem is gated by the enterprise.branding capability code in the nextpdf/enterprise package. Unlike most Enterprise surfaces it has a dedicated capability code because it governs evaluation behavior across all editions. The branding mode is resolved from the license envelope at runtime; no application flag selects it.

Behavior contract

• BrandingMode has two states: None (default; no modification of output) and EvaluationWatermark.
• Under a paid (non-evaluation) license the mode is None and the null strategy is selected: output is identical to output produced with no branding subsystem at all.
• Under an evaluation license the strategy draws a diagonal watermark in an isolated graphics state and appends evaluation markers to producer and subject metadata.
• The configuration object is immutable and validates its inputs (watermark text non-empty, font size positive).

NDA scan status

This public page describes externally observable behavior only. It contains no internal namespace paths, no internal trait names, no runbook filenames, and no internal ticket prefixes. Detailed internals are in the gated deep reference under NDA.

Core fallback

The branding subsystem ships in the nextpdf/enterprise package but governs evaluation behavior across all editions, including Core- and Pro-only deployments that use an evaluation license. There is no Core-only branding subsystem to fall back to; a paid license in any edition resolves to BrandingMode::None.

Pro fallback

There is no separate Pro branding subsystem. The same nextpdf/enterprise branding subsystem governs evaluation behavior for Pro deployments; a paid Pro license resolves to BrandingMode::None exactly as a paid Enterprise license does.

Enterprise boundary note

The branding mode resolution, the watermark rendering, and the metadata decoration are described at the behavior level only. The internal license-state-to-mode mapping, the internal watermark geometry, and the internal strategy-factory wiring are out of scope for the public surface and are not reproduced here.

Deployment boundary

The license envelope that selects the branding mode is a signed artifact whose issuer signature the runtime verifies; license provisioning, renewal, and secure storage of the license are the operator’s responsibility. The subsystem makes no network calls and reads no document content.

Legal-compliance boundary

This page describes runtime behavior only. It does not state or imply any warranty, certification, or eligibility, and it does not constitute legal advice. The terms of your evaluation or subscription — including what branding applies and for how long — are defined solely by your license agreement. Consult that agreement or contact sales.

See also

• Trial and Evaluation Branding — the end-to-end evaluation story.
• License activation
• Enterprise overview
• Core vs Pro vs Enterprise feature matrix