FAQ

Common questions about gpdf-api — billing, security, support, hosting, comparisons.

FAQ

Billing

When does the monthly counter reset?

The first of the month, UTC 00:00:00. Any quota you haven't used doesn't carry over, but purchased addon packs do — they stay usable until the end of the current billing period.

Are 4xx and 5xx responses billed?

No. Only successful 200 responses count toward your quota.

What happens if I cancel mid-month?

Your Pro access continues until the end of the current billing period, then reverts to Free. No prorated refunds. You can downgrade and re-upgrade freely.

Can I run Self-host and SaaS together?

Yes, with separate accounts. Each instance key is independent.

Do you offer annual plans?

Pro is monthly only at v1. Annual contracts (and net-30 invoicing) become available on the Self-host plan — contact sales@gpdf.dev.

Do addon packs roll over?

No. They're usable until the end of the billing period in which you bought them.

What payment methods are accepted?

Visa, Mastercard, AMEX, Apple Pay, Google Pay (via Polar). Wire transfer is available for Self-host annual contracts.

Security & privacy

Where are PDFs stored?

They aren't. We don't persist generated PDFs server-side at all — the bytes are streamed straight from the renderer to your client and discarded. There is no "redownload" feature because there's nothing to redownload.

Are templates stored?

No. The template you send is held in memory only for the duration of the render. We do log the slug (a short label you opt in by passing) and a few request metadata fields (status code, latency, page count, byte count) for 7 days for the dashboard's Logs view. We never log the template body.

What about the data block?

Same answer. The data block lives in memory for the render and is then discarded. Logs do not include it.

Are you GDPR-compliant?

Yes. Account email is the only PII we retain, and you can request deletion any time via /app/account or by emailing privacy@gpdf.dev. Logs are retained for 7 days max.

Can I sign a DPA?

For Pro and Self-host: yes. We use Polar's DPA template. Email legal@gpdf.dev to start the process.

Where does the engine run?

Currently us-central1 (Iowa, USA) on Google Cloud Run. EU and APAC regions are on the roadmap for v1.x. If your workload requires data residency, Self-host gives you a single-binary deploy you can run wherever you want.

Compatibility

Which PDF version do you produce?

PDF 1.7 by default. Set options.pdfa: "1b" for PDF/A-1b, "2b" or "2u" for PDF/A-2.

Is the output ISO 32000 compliant?

We aim for it and run pdfcpu validation in CI on every change. If you find an output we produce that fails a strict validator, that's a bug — file it.

Does it work with [Adobe Reader / Apple Preview / Foxit / Sumatra]?

Yes, all of them. We test against Adobe Reader DC, Apple Preview, Foxit Reader, and Sumatra on every release. CJK rendering specifically is verified against Reader DC and Preview.

Can the output be edited in Acrobat?

Yes, the same way any PDF can. If you want to prevent editing, use options.encrypt with permissions.modify: false, or sign the document — signed PDFs show a warning in Acrobat if anyone modifies them post-signing.

Engineering

What's your SLA?

99.9% uptime on Pro (≈ 43 minutes of downtime per month). No SLA on Free. Self-host: you're on your own infra, but the binary itself has no required network calls during a render — only the daily license heartbeat.

Where can I see real-time status?

status.gpdf.dev. Subscribe via email or RSS for incident notifications.

Do you support webhooks?

Not at v1. We don't have async events — every render is synchronous. The only "webhook" we accept is from Polar for billing, and that's internal.

How do I report a bug?

GitHub issues for the API; GitHub issues on the engine repo for the engine. Include the request_id from the response — that's the fastest path to a fix.

Is the engine open source?

Yes. The rendering engine (gpdf) is MIT-licensed pure Go. The SaaS layer (auth, quota, billing, logging — gpdf-api) is closed source, but you can self-host the same binary.

Can I contribute?

To the engine: please do. PRs welcome on github.com/gpdf-dev/gpdf, with the issue-first PR policy described in CONTRIBUTING.md.

Comparisons

How does this compare to Puppeteer / WkHtmlToPdf / WeasyPrint?

We're 10–30× faster on equivalent documents because there's no headless browser. The trade-off: no HTML/CSS — you describe the document in JSON. See Migrating from other PDF APIs.

How does this compare to PDFShift / DocRaptor / API2PDF?

Same answer. Those services accept HTML, take 300–1000 ms, and cost more per render. We accept JSON, take 10–500 ms, and have a friendlier free tier.

How does this compare to AWS Lambda + headless Chrome?

Lower variance and lower 99th-percentile latency. Cold starts on Lambda + Chrome are 2–8 s; we never have a cold-start penalty visible to you because we keep a warm pool.

Is it really pure-Go zero-dependency?

The engine is — the only thing it imports is the Go standard library. The SaaS layer (gpdf-api) of course pulls in a few service SDKs for auth, billing, and email.

Self-host

What does "self-host" mean exactly?

You run the gpdf-api binary on your own infrastructure (Docker, Cloud Run, bare-metal, anywhere). It serves the same /v1 API. You skip our quota system; you have your own. You still need a license key to pass a daily heartbeat.

What if your license server goes down?

The binary keeps a 24-hour grace period. If our heartbeat endpoint can't be reached for more than 24 hours, the binary refuses new renders until it can re-validate. We give you 90 days of advance notice for any planned downtime, and the status page is the canonical source.

Can I bake the license into a Docker image?

You can put the license key in an env var (GPDF_API_LICENSE_KEY). Don't bake the key into the image itself — it's a secret. Use Docker secrets, AWS Parameter Store, etc.

Do you offer airgapped self-host?

Not at v1. The license heartbeat needs an outbound HTTPS call once a day. If your environment forbids that, talk to us — we have a roadmap item for offline activation but no public timeline.

Anything else?

If your question isn't here, the right places to ask are:

Something unclear or missing on this page?