Project description
TranslatedWe're building a product with heavy document flow and we need a dedicated PDF generation microservice that lives on its own and does exactly one thing very well: takes an HTML template together with a set of dynamic data and returns a pixel-perfect PDF. We're talking invoices, contracts and multi-page reports that must look identical every time, regardless of who triggered the render or which part of our system made the request. This is strictly a PDF rendering service. It's not a document automation application or e-signature workflow—those live separately. Your task is the rendering engine and the API around it, nothing more and nothing less.
The service should provide a small predictable HTTP API: send a template identifier or inline template together with a JSON data object and get back either a binary PDF or a link to a saved file. Templates are HTML and CSS, so we expect proper handling of page size and margins, repeating headers and footers, page numbering, clean page breaks and embedded custom fonts so the result matches our brand exactly. Server-side rendering must be deterministic: identical input always produces byte-comparable output. For us, correct handling of tables that break across pages, unicode and high-resolution logos matters. Performance matters too—the endpoint should quickly render a typical multi-page invoice and handle a reasonable spike of concurrent requests without falling over.
Propose a sound engine choice and justify it, package the service in a container for independent deployment and include an approach for template management, versioning and basic API authentication. Give clear documentation and a working example so our backend team integrates everything in one day. When you respond, share your experience with headless rendering and font embedding.
— Clean HTTP API: template + JSON in, PDF out
— Pixel-perfect layout with headers, footers, page numbering and breaks
— Custom font embedding and full unicode support
— Deterministic reproducible server-side rendering
— Containerization, independent deployment and API authentication
— Documentation and working integration example
The service should provide a small predictable HTTP API: send a template identifier or inline template together with a JSON data object and get back either a binary PDF or a link to a saved file. Templates are HTML and CSS, so we expect proper handling of page size and margins, repeating headers and footers, page numbering, clean page breaks and embedded custom fonts so the result matches our brand exactly. Server-side rendering must be deterministic: identical input always produces byte-comparable output. For us, correct handling of tables that break across pages, unicode and high-resolution logos matters. Performance matters too—the endpoint should quickly render a typical multi-page invoice and handle a reasonable spike of concurrent requests without falling over.
Propose a sound engine choice and justify it, package the service in a container for independent deployment and include an approach for template management, versioning and basic API authentication. Give clear documentation and a working example so our backend team integrates everything in one day. When you respond, share your experience with headless rendering and font embedding.
— Clean HTTP API: template + JSON in, PDF out
— Pixel-perfect layout with headers, footers, page numbering and breaks
— Custom font embedding and full unicode support
— Deterministic reproducible server-side rendering
— Containerization, independent deployment and API authentication
— Documentation and working integration example
Software development Cash, Bank transfer
