CompilePDF CompilePDF

The writer half of the stack

CompilePDF exists because every PWS-stack consumer needs to write PDFs eventually — and the existing options force you to choose between heavy proprietary tooling and brittle shell-scripts. We built the open writer, deterministic by construction, AGPL-3.0-licensed.

Think Neverland

CompilePDF is built by Think Neverland, a product studio focused on developer tools for the print and publishing industry. Every web-to-print platform, every MIS, every preflight tool eventually needs to write a PDF — to apply a fix, stamp marks, impose a sheet, trap an ink pair. The options today are bad: pay Acrobat by the seat, license a proprietary backend, or stitch together shell-scripts against Ghostscript.

CompilePDF is the third option. Four first-class producer engines that consume the same Codex extract on the read side, share a published cache-key contract, and round-trip deterministically. Drop it into your stack as a CLI, a FastAPI sidecar, or a Celery worker. No plug-ins, no per-seat licenses, no vendor lock-in.

Composable by design

CompilePDF doesn't try to be your preflight tool, your viewer, or your job board. It's a writer — it applies the operation you asked for and gets out of your way.

The CJD pipeline covers the orchestration surface: a single JSON (or XML) envelope chains rewrite → marks → impose → trap, with one lineage record per step. Bring your own preflight verdicts (LintPDF, PitStop, callas), brand specs, or job-board context — the producers stay composable; the host stays in charge.

What you don't get: a half-finished editor, a forced sign-up flow, or hidden telemetry. What you do get: a writer that respects your stack and your customers.

Open standards commitment

CompilePDF writes against the same standards every prepress professional already knows. We don't invent — we implement.

ISO 32000-2

The PDF 2.0 specification. CompilePDF writes through pikepdf with deterministic_id=True; every save round-trips cleanly.

PDF/X-4

The rewrite producer's pdfx_pin op writes compliant OutputIntents and trapping flags so downstream preflight runs clean.

DeviceN + Spot

Trap operates per-spot-ink with delta_e_2000 verification against the codex-pdf color resolver — no Compile-side color math.

JDF / PJTF (planned)

The CJD XML envelope is shaped to slot into existing JDF / PJTF integrations; the full schema translator lands alongside the first customer integration.

See what CompilePDF can write

Four producer engines, one CJD pipeline, lineage records on every step — all open source, embeddable in any host.

View on GitHub