Adaptive Rendering
Adaptive layout for complex data including hierarchical tables, dynamic cards, structured content, and enterprise templates.
- Hierarchical tables
- Dynamic cards
- Structured content
Back to platform
Document Rendering & Processing Engine
Refract Logic Product Suite
REFRACT PDF™
Adaptive Document Rendering & Processing Engine
REFRACT PDF turns structured data and templates into PDF documents with adaptive layout, optional accessibility tagging, tenant-managed assets, and controls such as redaction and watermarking. A document can be re-rendered from its archive and compared byte for byte with the original.
REFRACT PDF™
Document Infrastructure for the Verifiable Enterprise
Adaptive Rendering
Adaptive layout for complex data including hierarchical tables, dynamic cards, structured content, and enterprise templates.
Sovereign Content & Assets
Templates, images, and annex content are kept in your own SharePoint or Azure storage libraries. A standard font is bundled; additional non-Latin fonts are supplied by your administrator at deployment.
Document Controls & Security
Policy-driven redaction and masking of data fields before layout, so redacted values are not written into the PDF. When an audit archive is built, the unredacted source stays in it, in your own storage. Text or image watermarks can be set per document from the data.
Signature-Ready Output
Signature zones and a printed Approval and Verification page are part of the rendered document. Signing order and approvals are handled by REFRACT eSign and REFRACT Workflow.
Document Infrastructure for the Verifiable Enterprise
Product capabilities
Built for teams that need dynamic document composition, optional accessibility tagging, redaction, and signature-ready output, rendered inside their own Azure subscription.
Sovereign Content & Assets
Templates, images, and annex content are kept in your own SharePoint or Azure storage libraries. A standard font is bundled; additional non-Latin fonts are supplied by your administrator at deployment.
- Images
- Annex content
- Templates
Document Controls & Security
Policy-driven redaction and masking of data fields before layout, so redacted values are not written into the PDF. When an audit archive is built, the unredacted source stays in it, in your own storage. Text or image watermarks can be set per document from the data.
- Data redaction
- Per-group redaction policies
- Dynamic watermarking
Signature-Ready Output
Signature zones and a printed Approval and Verification page are part of the rendered document. Signing order and approvals are handled by REFRACT eSign and REFRACT Workflow.
- Signature zones
- Approval page
- Hands off to eSign and Workflow
Queue-Based Rendering
Optional rendering on Azure Service Bus with separate priority, standard, and low queues, retries, and dead-lettering. Batch distribution runs record by record, up to 1,000 records per batch.
- Separate priority queues
- Retries and dead-lettering
- Batch distribution
Navigation & Accessibility Tagging
A table of contents generated from section headings and, when accessibility tagging is switched on for a template and your licence includes it, tagged PDFs with document language, title, heading bookmarks, table headers, and image alt text that you supply. The engine runs its own structural checks and records the results; they are self-assessed, not a certification.
- Optional TOC
- Tagged PDF structure
- Self-assessed checks
Execution model
How it fits into the REFRACT Platform
1
Ingest structured data, tenant-managed assets, and approved template definitions.
2
Render document sections from the template and data, with optional accessibility tagging and a table of contents.
3
Apply document controls such as redaction, watermarking, and signature zones.
4
Write final outputs to your SharePoint or Azure storage and hand them to REFRACT Workflow, eSign, Delivery, and Audit when those are licensed.
Enterprise proof points
Built for verifiable document infrastructure
Queue-based rendering is available for larger workloads. Sizing guidance is provided for deployment profiles; it is guidance, not a benchmark.
Accessibility tagging and XMP metadata are separate licensed features. The engine's PDF/UA-1 check reports a failure when XMP metadata is missing.
Re-rendering an archived document uses a pinned timestamp, bundled fonts, and archived assets, and the engine reports whether the result matches the original byte for byte. This covers rendered documents; sealed workflow documents are checked against their recorded hash instead.
Keeps assets and templates organized inside tenant-controlled infrastructure.
Works as the rendering foundation for the broader REFRACT Platform lifecycle.
Ready to modernize?