axesFlip converts documents into accessible PDF files using templates created with axesFlip Designer.
There are different deployment options available for axesFlip. The deployment options differ only in how axesFlip is executed and integrated into your environment.
Purpose of axesFlip
axesFlip takes two inputs:
- A non‑accessible PDF document, provided as a file or as a stream
- A template authored with axesFlip Designer
Using this input, axesFlip converts non‑accessible PDFs into fully accessible PDF documents. The conversion logic is entirely defined by the template.
axesFlip is designed for high‑volume batch processing and achieves performance ranging from dozens to hundreds of pages per second, depending on document complexity.
Available deployment options
You can run axesFlip in different ways, depending on your architectural and integration requirements. There are different deployment options available:
Both deployment options:
- Use the same execution engine
- Consume the same templates
- Produce identical accessible PDF output
The choice affects only how you invoke axesFlip, not the conversion results.
axesFlip CLI
axesFlip CLI runs as a command‑line tool. It is well suited for batch processing, scripted workflows, and automated pipelines.
Key characteristics
- Executed directly from the command line
- Accepts documents (single files or all files in a directory) and templates as parameters
- Supports processing files from local directories and shared network locations (file shares)
- Easy to integrate into scripts, schedulers, and CI/CD pipelines
- No continuously running service required
Typical use cases
- Batch conversion of large PDF sets
- Scheduled document processing
- Automated workflows in controlled environments
- Offline or file‑based processing scenarios
When to use axesFlip CLI
Choose axesFlip CLI if your use case is:
- Script‑driven or batch‑oriented
- File‑based rather than service‑based
- Focused on simple, explicit execution control
Learn more: axesFlip CLI
axesFlip REST Server
axesFlip REST Server runs as a long‑lived service and exposes the axesFlip functionality through an HTTP API. It enables service‑based and application‑level integration.
Key characteristics
- Runs continuously as a service
- Accepts documents (files or streams) and templates via REST requests
- Suitable for concurrent and multi‑user access
- Designed for integration into distributed systems
Typical use cases
- Application‑driven document conversion
- Centralized conversion services
- Integration into enterprise or backend systems
- Scalable or asynchronous processing workflows
When to use axesFlip REST Server
Choose axesFlip REST Server if you need:
- API‑based access to document conversion
- Integration with web applications or backend services
- Centralized processing for multiple clients or systems
Learn more: axesFlip REST Server