Official sources reviewed
| Primary source | What it establishes | Review date |
|---|---|---|
| Carbone documentation | Published template-based document-generation workflow and API documentation. | 2026-07-22 |
What this decision is actually about
The difference is not just syntax. It is the infrastructure behind conversion and whether the document workflow needs to remain lightweight enough for serverless and modern deployment models.
Evaluation prompts—not a feature scorecard
| Alternative boundary | Confirm the supported input, deployment, and output behavior in the official source above using your current version. |
| PaperJSX boundary | Prove one real artifact locally first; local package behavior does not imply hosted access. |
| Delivery decision | Test the native file, recipient handoff, and release check that matter in your product. |
When PaperJSX is the better fit
PaperJSX is the stronger fit when you like template-driven authoring but cannot accept a LibreOffice runtime, large Docker images, or a conversion stack that fights serverless deployment.
When Carbone is the better fit
If the team is already comfortable operating LibreOffice-backed infrastructure and does not need track changes, accessibility, or serverless deployment, Carbone may be sufficient.
Cost of choosing PaperJSX
Carbone has a longer history in office-template workflows. Teams with deeply invested LibreOffice infrastructure that works well may not need the migration yet.
Evaluate the file your customer receives.
Bring one real payload, its expected file, and the release check you cannot miss. Pro and Platform are self-serve; contact us when the evaluation requires Enterprise terms or architecture review.