OrbitPDF Core

No. OrbitPDF does not replace Odoo's PDF report pipeline, nor does it enforce a single rendering model. It introduces a parallel rendering path that operates alongside Odoo's existing pipeline. wkhtmltopdf remains available and unchanged, and reports can opt into an alternative rendering engine on a per-report basis.

OrbitPDF is not a PDF renderer. It is the layer that sits between Odoo documents and the engines that transform them into PDF. Its role is to make rendering behavior explicit and controlled, so that engines can evolve without forcing documents or workflows to evolve with them.

OrbitPDF decouples document authoring from rendering technology. It does not replace Odoo's pipeline; it clarifies and extends it.

No template rewrite is required in most scenarios. Selecting the appropriate rendering engine and paper format per report is typically sufficient for predictable output. For edge cases involving complex layouts or custom pagination, targeted paged-media CSS adjustments may be needed. Fast Print ships with pre-calibrated patches for all 7 standard Odoo layouts, so standard reports work out of the box.

OrbitPDF Core (MPL-2) exists for teams who want to self-operate and have the technical capacity to do so. Fast Print is a commercial product built on top of that foundation, sold to deliver a complete, production-ready solution.

Fast Print Starter is a one-time purchasing, licensed per customer and per production instance under SPL-1. The license includes 3 months of free support from the date of purchase. After that period, continued support is available as a paid service.

Redistribution, sublicensing, or reselling Fast Print to third parties is not permitted under the license terms. If you are an Odoo partner deploying for clients, please contact us about the Implementer Partnership program, which is structured for that purpose.

Yes. Both Core and Fast Print are compatible with Odoo.sh and self-hosted on-premise environments. Rendering runs entirely within your own infrastructure. There are no external API calls and no cloud dependency for document generation.

OrbitPDF currently operates with PlutoPrint as its primary engine. Integration with Paper Muncher is planned once the engine demonstrates production-ready stability and behavior.

• Paper Muncher follows a browser-based approach. It treats HTML as a web runtime and focuses on improving fidelity and performance within a modernized rendering stack. This model aligns naturally with web-centric documents and evolving frontend layouts.
• PlutoPrint takes a document-first approach. It treats HTML as document markup and embeds pagination directly into the layout process, prioritizing predictable output and long-term stability over browser simulation.

OrbitPDF remains engine-agnostic by design. Paper Muncher treats HTML as a live web runtime; PlutoPrint treats it as document markup. That single distinction drives every meaningful difference between the two engines.

PlutoPrint is built on PlutoBook, which implements W3C CSS standards directly rather than emulating a browser. For document work, this means reliable support for running headers and footers, automatic page numbering, table-of-contents leaders, cross-page references, and precise margin control — features that browsers handle inconsistently or not at all.

The full CSS layout toolkit works as expected: flexbox, multi-column, tables, 2D transforms, OpenType and variable fonts, CSS variables, and math functions. Standard print units are fully supported.

If you already know CSS paged media, everything applies directly. Full feature documentation: github.com/plutoprint/plutobook

OrbitPDF is not a renderer. It is the abstraction layer that sits between Odoo and the engines that produce PDF. PlutoPrint is the first engine connected to it, and the relationship runs deeper than a technical integration. PlutoPrint and PlutoBook were founded by Samuel Ugochukwu; Sveltware Solutions is the primary sponsor of both projects, working directly with the author to shape the engine's direction around real production requirements.

The choice was not purely technical. Both projects share the same software sensibility: fast, lean, direct, and built for infrastructure that lasts. OrbitPDF does not just use PlutoPrint; it was co-engineered with it. That spirit extends beyond Sveltware: Ashish Kulkarni, the principal contributor behind wkhtmltopdf, also sponsors PlutoPrint, motivated by what he describes on GitHub simply as "nostalgia" — a quiet signal from the engineer who built the tool PlutoPrint is positioned to replace.