No PDF upload API
Hosted APIs reject file uploads. PDFs are processed in-browser or by the Local Agent running on customer-controlled hardware.
ZERO DOCUMENT RETENTIONPDF bytes stay off PDFKite servers. Hosted services store workflow metadata and SHA-256 hashes only.
PDFKite Enterprise
Enterprise signing without hosting your documents
Create hash-bound signing requests, capture consent and audit events, use customer-controlled document storage, and add certificate-backed signatures through a local endpoint.
SHA-256 document binding
Signing requests store the document hash. The editor verifies the exact file before allowing an enterprise signing event.
Append-only signing events
Capture link access, file verification, consent/signing events, timestamps, IP and browser metadata without storing the document.
Certificate signatures
Use a P12/PFX credential through the Local Agent for cryptographic PDF signing. Trusted status depends on the certificate chain.
Customer-owned storage
Point the request at SharePoint, S3, Azure Blob, a secure portal, or any storage controlled by the organization.
Compliance-ready architecture
DPA/BAA/security policy templates, retention controls, audit schema, and operational checklists are included in the master package for legal/security review.
Create a zero-retention signing request
The selected PDF is hashed in this browser. The PDF itself is not uploaded.
SHA-256
Select a PDF to calculate its hash locally.