Iteration Layer vs Gotenberg
Gotenberg runs Chromium and LibreOffice in Docker — you get a conversion service, not a generation API.
Why developers switch from Gotenberg
Gotenberg needs a 1GB+ Docker image running Chromium and LibreOffice on your infrastructure.
No container to run or scale
Gotenberg's Docker image is over 1 GB — it bundles a full Chromium and LibreOffice installation. Each instance runs two heavy processes at idle. We are a managed API: send a request, get a document back, no infrastructure to manage.
Generate from data, not convert from HTML
Gotenberg converts files to PDF — it doesn't generate documents from data. You still need to produce the HTML or DOCX before handing it to Gotenberg. Our JSON content model builds the document directly from your data in one step.
Four output formats, not just PDF
Gotenberg converts to PDF. We render PDF, DOCX, EPUB, and PPTX from the same JSON content definition. One content model, four formats, zero additional infrastructure.
Feature-by-feature comparison
We went through the docs so you don't have to. Here's how every feature compares — including the ones where we're not the better choice.
| Feature | Iteration Layer | Gotenberg |
|---|---|---|
| Output formats |
4 formats
PDF, DOCX, EPUB, and PPTX from the same JSON content definition |
PDF
Converts various input formats to PDF via Chromium and LibreOffice |
| Template model |
JSON blocks
Content defined as JSON block arrays — versionable and diffable |
HTML or Office files
Converts existing HTML or Office files to PDF — you still need to produce the source document first |
| Custom fonts |
Yes
Upload and use custom fonts in any document |
Limited
Custom fonts require building a new Docker image with the fonts pre-installed |
| Memory at idle |
Serverless
No idle resource consumption — processing happens per request on managed infrastructure |
500 MB+
Each running instance consumes 500 MB+ of memory at idle with Chromium and LibreOffice loaded |
| Open source |
Proprietary
Closed-source managed SaaS platform |
MIT license
Free and open source under the MIT license |
| Office-to-PDF conversion |
JSON only
Generates documents from JSON content model only, does not convert existing files |
Built-in
Converts existing DOCX, XLSX, and PPTX files to PDF via LibreOffice |
| Composability |
Standalone
Standalone document generation API |
Composable
Useful as a conversion layer in combination with other document generation tools |
| EU hosting |
EU only
All processing happens exclusively on EU-hosted servers |
Your choice
Runs on your infrastructure, so data residency depends on where you deploy |
| Pricing model |
Per document
Pay-per-use pricing based on the number of documents generated |
Free
Open source and free to use — costs are limited to running the Docker container |
| Infrastructure required |
None
Fully managed API with no containers, binaries, or infrastructure to manage |
Docker container
Requires running a 1 GB+ Docker image bundling Chromium and LibreOffice |
| GDPR / Data privacy |
Zero retention
No files or results stored beyond temporary 90-day logs |
Your responsibility
Data privacy depends entirely on your deployment and infrastructure choices |
Pricing
Start usage-based. Switch to a subscription when your volume becomes predictable.
Usage-based
Graduated pricing. Your effective rate decreases automatically as monthly usage grows.
- No monthly commitment
- Pay only for credits used
- Automatic volume discounts as usage grows
Predictable volume
Fixed recurring credit packs with lower effective credit prices for steady usage.
- Lower effective per-credit prices
- Fixed recurring credit packs
- Predictable monthly budget
Still evaluating?
See how we compare — and where the competition still wins. Choosing the right tool shouldn't require a week of research.
Start building in minutes
Free trial credits included.