Inside the pdfRest API Toolkit Container: Licensing, Support, and Deployment Options

For teams that have already concluded a self-hosted PDF API is the right architecture, the remaining questions are practical: what's actually included, how is it licensed, how does support work, and what does deployment look like day to day. Here's a straight answer to each.

What's included

The pdfRest API Toolkit Container ships as a single container image with the complete PDF processing toolkit built in: conversion, editing, extraction, security, optimization, and forms, all exposed through standard REST endpoints. There are no add-on modules or feature tiers. The license covers the full toolkit, so there's no separate negotiation for capabilities you already assumed were included.

It's built on the Adobe PDF Library, the same core PDF engine Datalogics has developed and supported for decades, and the same engine underlying PDF applications used across the industry.

Deployment options

The container is designed to deploy wherever your infrastructure policies require:

• On-premises data centers: full deployment within your own infrastructure using Docker, Kubernetes, or your preferred orchestration platform, with no external calls made during processing.
• Private cloud: deployed into AWS, Azure, or GCP private environments, including air-gapped configurations, satisfying data residency requirements within your own tenancy and compatible with AKS, EKS, GKE, and Oracle Kubernetes Engine.
• Hybrid architectures: sensitive documents processed on-premises, lower-sensitivity batch jobs handled in a private cloud, and development/testing isolated separately, all with identical API behavior so there's no environment-specific logic to write or maintain.

Licensing built for enterprise operating patterns

Self-serve and per-call SaaS pricing generally doesn't map to how enterprise teams actually operate. The Toolkit Container's licensing is structured around:

• Multi-environment deployments: development, staging, and production under a single agreement
• High-volume and batch workflows: licensed to your operational capacity, with no per-call metering surprises
• Customer-facing and OEM use cases: embed the container in your own product and redistribute it under your brand
• Long-term production commitments: multi-year terms with renewal protections and predictable costs

Because every organization's infrastructure and usage pattern is different, licensing is scoped through a direct conversation rather than a fixed price list. Contact Datalogics to determine the right structure for your organization.

Support that doesn't route through a tiered queue

Enterprise deployments come with a support expectation: when something breaks in a compliance-critical workflow, you need someone who actually understands the product, not a first-line queue. The Toolkit Container is backed by:

• Implementation support: Datalogics software engineers work directly alongside your team to integrate, deploy, and configure the container from day one.
• Engineers, not escalations: dedicated account management with direct access to the PDF engineers who built the product.
• A relationship built to last: decades of active enterprise customer relationships and a 91% customer retention rate.

Getting started

Evaluation starts with a free trial. Fill out the trial request form to receive an activation key, pull the Docker image, and deploy with Docker Compose (recommended) or Kubernetes, configuring environment variables as needed. Full setup steps and API routes are covered in the pdfRest API Toolkit Container documentation - please note this will take you to our sister site pdfRest, but it's still Datalogics technology and expertise.

If your team has already validated the architecture case for self-hosted PDF processing, the practical next step is a conversation about licensing and deployment scope. Request a free trial of the pdfRest API Toolkit Container to get started.

Next up: the engineering heritage behind the Toolkit Container, and why it matters for reliability at scale. See 30 Years of Adobe PDF Library Engineering.