Frequently asked questions.

Both. We build and maintain open-source developer tools for the print industry, and we take on consulting engagements to help print and prepress teams deploy, integrate, and extend them. The software and the services reinforce each other — we don't sell consulting as a substitute for product.

All three, but with different entry points. Print shops and trade shops use our tools to automate preflight, production prep, and job routing. Brands and packaging teams use them to enforce print standards across suppliers. Technology vendors — MIS providers, web-to-print platforms, prepress ISVs — use the OSS tools directly as library or API dependencies inside their own products.

Custom print workflow applications, preflight integrations, MIS/JMF connectors, prepress automation pipelines, and embedding our OSS tools into existing products. If it involves PDFs moving through a production environment, we've likely built something like it.

Yes. We design and build bespoke print automation and prepress tooling — from single-purpose CLI tools to full workflow applications. Deliverables are yours: source code, documentation, and handover session included.

Yes. Connecting production systems via JMF/JDF, webhooks, or direct API integration is standard work for us. We also build import adapters for existing preflight report formats (Pitstop XML, callas JSON, Acrobat XML) so you can ingest third-party output without re-running preflight.

Yes. Migrations start with a workflow audit that maps your current primitive usage to open equivalents. From there we scope what maps directly, what needs custom work, and what can be simplified.

Discovery → scoping → delivery → handover. Discovery maps your current workflow and identifies the gaps. Scoping produces a fixed-price or time-boxed proposal. Delivery is iterative with working software at each milestone. Handover includes documentation, runbook, and a session with your team.

Project engagements are fixed-price after scoping. Retainers are monthly with a defined hour allocation. We don't bill hourly for open-ended work — every engagement has a defined scope before work starts.

Use the contact form. We'll schedule a discovery call, map the scope, and come back with a proposal — usually within a week.

Yes. Support contracts are available for teams running our OSS tools in production who need guaranteed response times, direct access, and ongoing maintenance assurance.

Depending on tier: guaranteed response SLA for bugs and incidents, prioritized issue triage, patch backporting to pinned versions, quarterly review calls, and direct access to the team via a shared channel. Contracts do not cover net-new feature development — that falls under a consulting engagement.

Contracts are annual. Minimum engagement is one year. Month-to-month arrangements are available at a higher rate for teams that need flexibility during a pilot period.

Yes, with scoping. The base contract covers the upstream OSS tools; an integration layer extension is priced separately.

• LintPDF — preflight engine, 500+ checks, findings as JSON/HTML/annotated PDF.
• CodexPDF — PDF facts and render layer, extracts document model, renders separations and heatmaps.
• LensPDF — embeddable React viewer with separation overlays, TAC visualization, and finding annotations.
• CompilePDF — PDF writer for imposition, trapping, marks, color rewrites, and page geometry.
• AssayPDF — GWG 2022 benchmark harness, scores preflight accuracy TP/FP/FN/TN per rule.

Yes. Each is a standalone package. No engagement required.

All five are currently in beta and undergoing production testing. They are running in real production environments, but APIs and output formats may still shift before stable releases. Pin to a specific version in any production integration.

Calling the HTTP API from a closed-source application does not trigger AGPL copyleft — you are a network client, not a distributor of a modified version. The obligation applies if you modify the source and run that modified version as a network service. For embedding or modifying source in a proprietary product, contact us about a commercial license.