Managed PDF rendering for SaaS teams. Design templates once, render invoices, contracts, reports and labels from your API payload.
No headless Chrome. No render workers. No PDF pipeline to maintain.
"customer": { "name": "Acme Inc." },
"items": [{ "sku": "PRO", "amount": 99 }],
"total": 128.00What started as “just render a PDF” quietly turned into a long-running engineering project. Sound familiar?
A Chromium bump silently shifts page breaks. Customer invoices, monthly statements and contracts render wrong until you redeploy.
+400 MB to ship a browser nobody uses interactively. Slower CI, slower deploys, bigger attack surface.
Puppeteer flakiness, wkhtmltopdf font fallbacks, retry queues, signed URLs — maintenance nobody planned for in the roadmap.
10k invoices on the 1st of the month. One malformed payload triggers a retry storm. Dead-letter queues fill up before coffee.
Upload to S3, rotate keys, expire URLs, audit access. PDFs from last quarter still need to render their links today.
The branded invoice from 2023 has to keep rendering correctly forever, even after design moved on three iterations.
You wanted a PDF. You got a side project nobody asked for.
Not the cloud bill, the part that never makes it into a budget line.
Puppeteer flakes, font fallbacks, deploy hotfixes and queue babysitting instead of product work.
Heavier builds, slower CI, larger attack surface and longer cold starts for a browser nobody opens.
Queue backlogs, OOMs and retry storms tend to happen when customers need their PDFs most.
Send a template and JSON payload. We operate the render path, retries, storage handoff and delivery hooks.
Invoices, contracts, reports, labels: production-ready, branded, versioned, served from a stable API instead of a Chromium worker pool.
Six reasons Airpdf replaces the in-house PDF stack you didn’t want to maintain.
Stop shipping Chromium with your backend. Design templates once, send a JSON payload, get back a production PDF — with versioning, webhooks, customer-owned storage and SDKs for every stack.
No Chrome to ship, patch or restart. We run the renderer; you call the endpoint.
Send JSON to /api/v1/render. Get raw bytes or a signed URL. That’s the whole protocol.
Drag-and-drop layout with pages, containers, text, images and lists. Designers ship; engineers stay in flow.
Official SDKs for Node, Python, Ruby and Go. Signed webhooks with idempotency for async batches.
Push to your S3 / R2 / Wasabi bucket. Signed URLs by default. Credentials encrypted at rest.
Idempotent retries, queue-backed async for heavy reports, versioned templates so last year’s invoice still renders today.
Invite teammates into shared workspaces, review template versions, and ship documents that look the same whether they’re generated from a laptop or a CI pipeline.
See API docs →Drop-in SDKs for Node, Python, Ruby and Go. Webhooks, signed URLs, S3-compatible storage. Replace your old PDF stack in an afternoon.
View SDKs →Reuse blocks across hundreds of templates. Change a header once, ship it everywhere — no copy-paste, no drift, no Friday-night fire drills.
Start free →A quick read on where Airpdf fits, and where it doesn’t pretend to.
Full control, full maintenance. Browser updates, Docker weight, retry queues, signed URLs — all on your team.
→ Airpdf removes the operational tax, keeps the visual control.
Send HTML, get a PDF. Great for one-offs. You still own the templating, the variable injection and the visual editor.
→ Airpdf ships a typed template model and a visual editor out of the box.
Mature, deep, expensive. Multi-month procurement, per-document pricing, integration tax.
→ Airpdf is SaaS-friendly: free tier, REST API, SDKs, transparent pricing.
1. Create a template
in the visual editor. 2. Send JSON
to /api/v1/render.
3. Get a production PDF
— raw bytes, signed URL or async webhook.
$ curl -X POST https://airpdf.app/api/v1/render \
-H "Authorization: Bearer atl_live_…" \
-H "Content-Type: application/json" \
-d '{
"template": "invoice",
"data": {
"customer": { "name": "Acme Inc." },
"items": [{ "label": "Pro plan", "amount": 99 }]
}
}' -o invoice.pdf
→ 200 OK · application/pdf · 18 KB · 412msFive ready-made templates: invoices, contracts, reports, labels, receipts. Tweak the JSON, hit render, the PDF opens in a new tab. Same engine your production code would hit. Rate-limited to 5 / minute, watermarked, zero account.
Slide to your monthly volume, we’ll highlight the best plan and the estimated monthly cost.
Create a workspace, design your first template, render a production PDF from your API payload in minutes.