Your Report Designer install

Pixel-perfect PDFs, designed by your users

Embed the template designer in your application, and render bills of lading, pick lists, labels and invoices from your back end: one template, any amount of data, the same layout every time. Everything runs on this server, on your network.

Checking status…
curl -X POST https://reports.internal.example.com/api/v1/render \
  -H 'Content-Type: application/json' \
  -d '{"template": …, "data": {"bolNumber": "BOL2026102001", …}}' \
  -o bol.pdf

Designer

Let your users design templates

The <report-designer> web component runs inside your app. Authors lay out documents, bind fields from your data contract and preview the real PDF. Your app stores the template JSON.

How: set template and schema, listen for save. Works in any framework:

Render service

Template + data → PDF

Your WMS or ERP posts a saved template and one document's data, and gets the PDF back: fonts embedded, barcodes exact, page breaks and repeated headers handled. Batches render into one PDF.

How: POST /api/v1/render with { template, data }. Clients in curl, Node, Python, Java and C#.

Everything else