Control your Backend with pdfRest API Toolkit Self-Hosted

Bring Powerful PDF Processing Into Your Own Infrastructure

Some documents simply should not leave your environment. Healthcare records, financial statements, legal files, intellectual property, and other sensitive content may need to remain inside infrastructure governed by your own security, residency, and access-control policies.

pdfRest API Toolkit Self-Hosted brings production-ready PDF processing to that controlled environment. Your applications gain a comprehensive REST API for document workflows while your team retains authority over the backend, network, storage, scaling, and security. You can place processing close to the applications and data that depend on it—inside AWS, another public or private cloud, an on-premises data center, or a hybrid architecture.

Deploy Natively on AWS

pdfRest API Toolkit on AWS gives AWS teams two ways to add private PDF processing to their existing cloud architecture:

• AMI / CloudFormation Template (CFT): Launch the preconfigured AMI from AWS Marketplace for a fast, single-instance deployment, or use the CloudFormation fulfillment option to build a scalable environment with supporting AWS infrastructure. Software usage is billed through the existing AWS account, simplifying procurement and cost management for organizations already standardized on AWS.
• Container Image (BYOL): Pull the pdfRest Container Image from AWS Marketplace and run it with Amazon ECS, Amazon EKS, AWS Fargate, or another Docker-compatible AWS service. Bring a pdfRest Container subscription to activate the image and fit PDF processing into the container orchestration, CI/CD, monitoring, and scaling practices your team already uses.

Both options process documents inside your own AWS environment. Choose the AMI or CFT when you want an EC2-based solution with AWS Marketplace billing, or choose the Container Image when containerized deployment is a better fit for your architecture.

Deploy the Container Anywhere

The pdfRest API Toolkit Container gives you the freedom to run the same powerful PDF capabilities wherever your applications and documents live. You can pull the license-managed pdfRest Container directly from Docker Hub, then deploy it with Docker or Kubernetes on-premises, in a public or private cloud, or across a hybrid environment. This portability makes it easier to align PDF processing with data-residency rules, existing operational tooling, and future infrastructure changes.

Self-serve subscriptions are available in several tiers, making it easy to start with the capacity that fits your current workload and expand as usage grows. These plans use a license key and make a lightweight external call to validate the subscription. That validation never sends your PDFs, document contents, extracted text, or proprietary customer data to pdfRest. Every customer file and every PDF processing operation stays entirely within the environment you control.

Organizations with higher-volume, specialized, or disconnected environments can work with the pdfRest Sales team on Enterprise licensing. Enterprise licensing removes license management from the Container itself, enabling fully offline and air-gapped deployments without an external license-validation check.

Keep Every Document Inside Your Security Boundary

With pdfRest Self-Hosted, customer files and data never leave your infrastructure. PDFs are uploaded to an API endpoint operating inside your environment, processed there, and returned or stored according to your own policies. pdfRest does not receive the source files, generated files, document contents, extracted text, or other proprietary data involved in the workflow.

For self-serve Container subscriptions—including the Container Image deployed on AWS—the only required outbound communication is the license-validation check. AMI and CloudFormation deployments use AWS Marketplace metering. Neither process transmits customer documents or their contents. Enterprise Container deployments can operate without any external license-validation connection.

Because the service runs within infrastructure you administer, you can apply your existing network controls, identity and access management, encryption standards, logging, monitoring, backup policies, and retention rules. This helps your PDF workflows fit into an established security program instead of creating a separate path for sensitive documents.

Build Complete Workflows with 40+ PDF API Tools

Self-hosting does not mean settling for a narrow set of PDF functions. pdfRest provides more than 40 API Tools for converting, optimizing, modifying, extracting, securing, and analyzing documents. Applications can convert Office files and images to PDF, transform PDFs into editable formats, compress and linearize files, merge or split documents, process AcroForms and XFA forms, apply encryption and restrictions, redact sensitive information, extract text and images, and prepare PDFs for archival or professional print workflows.

The tools use standard HTTP requests, making them straightforward to integrate with nearly any application or programming language. Resource-based workflows also let developers chain multiple operations efficiently. For example, an application can OCR a scanned document, extract its text, redact sensitive values, optimize the finished PDF, and return the result through one controlled backend workflow.

Find the Right Self-Hosted Fit

Explore pdfRest API Toolkit on AWS if your infrastructure and procurement are centered on AWS. Review the Container product and Container plans if you want portable Docker or Kubernetes deployment with a self-serve subscription. For higher capacity, custom requirements, or fully offline operation, contact the pdfRest Sales team to discuss Enterprise licensing.

Ready to plan a deployment? The AWS documentation and Container documentation provide technical guidance, and the pdfRest Support team is available to help with configuration or deployment questions.