FAQ

Everything you were about to ask.

How Pagr generates documents, what developers integrate against, and where your data lives. For plans and billing, see the pricing FAQ.

Product

Pagr is AI-native document generation software: a non-technical person designs a branded template in the browser, and a developer renders pixel-perfect PDFs from it with one API call — at any volume.

Most no-code tools stop at the template and expect you to work inside their app. Pagr ships as a real API with native TypeScript, Python, C#, Java, Ruby and C++ SDKs, so document generation drops into your own product instead of living in a separate one.

No. The editor opens in Canvas, where you describe what you want in plain language or point straight at the preview to change text, styling and layout. Studio additionally exposes the same template as JSON for teams that want precise control. Publishing a template locks its data model, which is the entire handoff to your developers.

Yes. Add translated text on a template's Translations tab and pick the language at render time — the same template and data model produce the same document in each language.

Yes. Define shared layout, styling and a header or footer once as a master template, then build other templates as children of it. Update the master and every child template picks up the change automatically.

Yes. A template holds multiple versions — publishing one marks it live for production, but you keep working by duplicating it into a new draft. Publish the draft when it's ready and the previous version keeps serving production until that exact moment, so there's no gap.

Yes. Upload your own font files and build a shared image library from the workspace's Fonts and Image Gallery sections, alongside your brand colors in General settings, so every template reuses your team's actual assets.

Integration & data

Yes. Building or editing a template with the AI Assistant draws on a monthly AI token allowance, separate from the page allowance you render against — rendering itself never costs tokens, and editing a template by hand costs nothing at all.

Through the API: call render synchronously to get the PDF straight back, or asynchronously with a webhook once it's ready — batches are supported too. The data model is generated from each template, so you know exactly what JSON to send.

Pagr posts a webhook to a callback URL you supply — one call per document as it renders, and a final one when the whole job completes — each signed so you can verify it came from Pagr. No public endpoint to receive it? Poll the job status instead; it carries the same information and is the authoritative signal.

Each document's render data can be up to 50 MB of JSON, nested up to 32 levels deep, and Pagr allows up to 60 seconds to render it — limits that apply per document even inside a batch.

Python, TypeScript, Java, C#, Ruby and C++, plus raw HTTP if you'd rather skip a library. All six are kept at full feature parity — every endpoint, every rendering shape, and the same webhook verification and parsing.

Yes. Upload the PDF, image or Stimulsoft file you already generate — up to 10 MB — and Pagr rebuilds it as an editable template, so you stop maintaining rendering infrastructure or brittle HTML-to-PDF scripts by hand.

Pagr is built and hosted in the EU by Metanous, based in Ghent, Belgium. See Security and DPA for how document data is handled, and the pricing FAQ for Enterprise's on-premises option.

For as long as your organisation's retention settings allow. You choose separate retention periods for PDFs and render data, capped by what your plan permits, and can leave either empty to keep them indefinitely.

Pricing & support

Pricing is page-based: start free with 100 pages a month, no credit card, and scale into Builder, Scaler or Enterprise as your volume grows. See the pricing page for plans and billing-specific questions.

Yes. Invite teammates under Settings → Users and grant granular view, edit or delete permissions per area — templates, images, fonts, projects and organisation settings — so a designer can build templates without touching billing or org-wide settings.

Reach the support page for billing questions, technical issues and bug reports, or book a demo and walk through your own documents with us directly.

Still have a question?

Bring your own document and we'll answer the rest live.