PDFFleet

PDFFleet / Gotenberg alternative

Gotenberg alternative — managed vs self-hosted

The managed alternative
to self-hosting Gotenberg.

Gotenberg is excellent open-source software — the same headless Chromium engine PDFFleet runs. The difference is deployment: Gotenberg means your own Docker containers, your own monitoring, your own API key system. PDFFleet is that same engine, fully managed — an HTTP request in, a PDF out, no DevOps required.

honest comparison

PDFFleet vs Gotenberg

Full disclosure: Gotenberg is free, open-source, and widely trusted (71M+ Docker Hub pulls, 12K+ GitHub stars). Both tools render with the same headless Chromium engine. PDFFleet is not "better" at rendering — it removes the operational burden of running Gotenberg yourself.

 Gotenberg (self-hosted)PDFFleet (managed)
Render engineHeadless ChromiumHeadless Chromiumidentical engine
Cost$0 (open-source)$0–$29/mo
Free tierUnlimited (you host it)100 PDFs/mo free
Deployment Run your own Docker container Zero deployment — just an API call
Server / infrastructure You provision, monitor, scale Managed — nothing to provision
API key management Build it yourself Built-in key generation & auth
Usage metering & billing Build it yourself Built-in usage tracking + Stripe
Chromium security updates You track and rebuild Handled automatically
HTML / URL / template input
Markdown / screenshot captureHTML / URL / templates
Best forTeams with DevOps capacityTeams that want PDF as a service
when each makes sense

Should you self-host or go managed?

Self-host Gotenberg if…

You have DevOps infrastructure, run Docker in production, and want zero per-PDF cost at any scale. You are comfortable maintaining Chromium dependencies, implementing your own API key and rate-limiting layer, and monitoring uptime yourself.

Use PDFFleet if…

You want to send an HTTP request and get a PDF back — no servers, no Docker, no Chromium to update. You need API keys, usage metering, and billing handled for you. At $4/mo for 10,000 PDFs, the managed layer typically costs less than the engineering hours to operate your own render fleet.

migration

Same engine, one-line switch

Since both use headless Chromium, your HTML and CSS need no changes. Replace your Gotenberg endpoint with an authenticated PDFFleet request.

Before — Gotenberg

POST to your self-hosted container.

POST http://your-server:3000/forms/chromium/html
{"files":["index.html"]}

After — PDFFleet

POST with HTML and your API key.

POST https://pdffleet.com/v1/pdf
X-API-Key: pf_yourkey
{"html":"<html>..."}
faq

Gotenberg vs PDFFleet — questions

Is PDFFleet the same as Gotenberg?

Both render HTML to PDF using headless Chromium — the same browser engine. The difference is deployment: Gotenberg is free, open-source software you run yourself inside a Docker container. PDFFleet is a fully managed API: you send an HTTP request and receive a PDF, with no servers, Docker, or DevOps to maintain. PDFFleet also adds API key management, usage metering, and Stripe-based billing that Gotenberg does not include.

When should I use Gotenberg instead of PDFFleet?

If you already have DevOps infrastructure, run Docker containers, and want zero per-PDF cost, self-host Gotenberg — it is excellent software with over 71 million Docker Hub pulls. PDFFleet is for teams that want PDF generation as a service: no infrastructure to maintain, no Chromium security updates to track, and built-in API keys and usage billing. The free tier (100 PDFs/month) lets you evaluate the managed experience at no cost.

Why pay for PDFFleet if Gotenberg is free?

You are paying for the managed layer, not the rendering engine. With Gotenberg you provision a server or container, monitor it, handle Chromium dependency updates, implement your own API key system, and scale it yourself. PDFFleet handles all of that. At $4/month for 10,000 PDFs, the cost is typically far less than the engineering time to operate and monitor your own Chromium rendering fleet.

Does PDFFleet use the same Chromium engine as Gotenberg?

Yes. Both PDFFleet and Gotenberg render PDFs using headless Chromium — the same engine that powers Google Chrome. This means identical CSS support, web font rendering, and print media handling. If your HTML renders correctly in Chrome, it will render identically through either tool.

Can I migrate from Gotenberg to PDFFleet?

Yes. Since both use Chromium, your HTML and CSS need no changes. Replace your Gotenberg container endpoint with an authenticated POST to https://pdffleet.com/v1/pdf including your HTML payload. The PDF output will be visually identical because the rendering engine is the same.

The same engine. Zero DevOps.

Start free with 100 PDFs/mo · $4/mo for 10,000 · same Chromium as Gotenberg

Get started →