A rare team fluent in prepress automation, modern full-stack, and the workflows that connect them.
Most web devs can't read a JMF dump. Most prepress engineers can't ship a Next.js app. The intersection is the core offer — and the same technical depth applies to general workflow automation and application builds with no print dependency at all.
Everything PWS builds is AGPL-3.0+ on GitHub. You get the source code, the right to run it, the right to fork it, the right to hire anyone you want to maintain it. The only thing tying you to PWS is the quality of the work.
Why this is hard to hire for.
Prepress automation and modern web development are two distinct disciplines. Finding a consultant who is genuinely senior in both — not superficially familiar with both — is unusual.
- PDF/X-4, overprint, Ghent Workgroup specs
- AE Pilot tickets, SmartNames
- Cloudflow workflow nodes, Pagebuilder
- JDF/JMF, hot folders, MIS integration
- ICC profiles, spot colors, screening
- Imposition, 1-bit TIFF or LEN for plate output
- React, Next.js, TypeScript
- REST/GraphQL API design
- Postgres, Docker, CI/CD
- Webhook plumbing, queue workers
- Node.js and Python services
- Shopify / WooCommerce ecosystem
Your stack, ours, or neither — no lock-in any way.
PWS can build on the open-source PWS stack, integrate with your existing print vendor stack, or use a general-purpose stack for workflow and application builds that have nothing to do with prepress. Every path ends with full source code in your hands.
PWS stack (recommended for new builds)
- Pixie Dust SaaS boilerplate (AGPL-3.0+)
- Fairy Ring plugin system (AGPL-3.0+)
- Five PDF tools: LintPDF, CompilePDF, CodexPDF, LensPDF, AssayPDF (AGPL-3.0+)
- Zero software fees — you pay for implementation and support only
- Full source delivered; fork it at any time
Your existing print stack
- Customer negotiates and pays licenses direct to their vendor
- PWS handles build, integration, and support
- Works with Esko, HYBRID, Enfocus, callas, and third-party systems
- No lock-in — bring your own tools
General stack (workflow & app builds)
- Plain Next.js, Python, Postgres, Node.js — whatever fits the problem
- No print vendor dependency required
- Internal tooling, portals, data pipelines, API integrations
- Same source delivery and support model
AGPL-3.0+ has commercial implications — customers can use it, host it, modify it, fork it. If you distribute modified versions or run a SaaS on top, AGPL terms require source disclosure to your users. For most prepress and print customers this is a non-issue. See the actual license on GitHub.
What does "production-grade" look like from this shop? Five AGPL-3.0+ PDF tools — LintPDF, CompilePDF, CodexPDF, LensPDF, AssayPDF — are the engineering receipt. See the tools →
What we build.
Web-to-print integrations
Shopify / WooCommerce → preflight → AE / Cloudflow hot folder. Customer portals. Self-service reorder.
JDF/JMF & MIS bridges
MIS↔prepress wiring. Job intake from ePS Pace, Avanti Slingshot (Print ePS), Label Traxx (Amtech), Cerm, ePS Radius, PrintVis. Status callbacks. Round-trip costing.
VDP pipelines
Data → templated PDF → imposition → 1-bit TIFF or LEN. Airtable/CSV/JSON ingest. Regulated-copy compliance for food and pharma labels.
Automated proofing
Lean Proofscope/WebCenter alternatives for SMBs. Online approval flows. Proof delivery integrated into AE and Cloudflow workflows.
Workflow & application builds
Internal tooling, ops portals, API integrations, data pipelines, custom SaaS features. No prepress dependency required.
Starts with a 30-minute technical call.
Fixed-fee scope follows the call. No sales deck, no obligation — just a conversation with the engineer doing the work.