Codex
Structured PDF extraction API that turns complex files into consistent JSON.
Atlas is the one canonical record of your print business — jobs, orders, customers, estimates, substrates, and margins — kept in sync with the MIS, ERP, and prepress tools you already run, over JDF/JMF and native connectors. API-first, hosted or self-host.
canonical entities · cross-system references · feeds your prepress tools
How it works
Atlas connects to the systems you already run, ingests their events onto a canonical model, reconciles a single record per job, and serves it to your prepress tools by a stable id — so everything reads the same facts.
Point a connector at your MIS, ERP, or 3PL, or open a JDF/JMF endpoint. Each connector declares what it can read and write, so the integration surface is explicit from day one.
Source events land on one canonical event envelope through endpoint-authenticated ingest. Atlas maps each onto the canonical model and reconciles it on a worker — replays are idempotent, so nothing double-applies.
One canonical record per job, order, customer, and estimate — with a cross-reference map back to every source system's own id. The business record becomes a single, versioned source of truth.
Your prepress tools resolve any record by its stable id, and write-back pushes canonical changes outbound to the systems of record. codex, lint, sift, compile, and lens all work from the same facts.
Built for web-to-print platforms, packaging houses, and prepress teams that need one trustworthy record of the business — synced with the systems they already run, without lock-in.
Job, order, customer, estimate, quote, substrate, shipment, and margin — modeled once, owned in one place. The business record your prepress stack never had, instead of fields parsed and dropped per request.
Every canonical record carries a stable id plus a cross-reference map back to each source system's own key — MIS, ERP, 3PL, and each prepress tool. Resolve any job by one id and see where it lives everywhere.
Native connectors for the systems print shops actually run — NetSuite, Dynamics, Amtech, Cerm, LabelTraxx, PrintEps, and a generic MIS adapter — plus JDF/JMF ingest and emit. Each declares a clear read/write capability lane.
Source events land on a single canonical event envelope through endpoint-authenticated ingest, are mapped and reconciled on a worker, and changes push back out to the systems of record. Replays are idempotent — the same event never double-applies.
Map any source document onto the canonical model with a versioned mapping spec — saved or inline — and dry-run it before anything is written. Tenant-defined mappings handle the dialect quirks of every shop's MIS.
Per-tenant isolation enforced at the database, an HMAC-chained audit trail on every change, and a versioned, content-addressed contract. Self-host or use managed hosting — same model, same guarantees.
Connect everything
Atlas augments your existing MIS, ERP, and prepress automation — it doesn't replace them. Connect once, map the dialects onto a canonical model, and keep every system in step.
Native connectors for the systems print shops actually run — NetSuite, Microsoft Dynamics, Amtech, Cerm, LabelTraxx, and PrintEps — plus a generic MIS adapter for everything else. Pull estimates, jobs, and customers in; push status and canonical updates back out.
Receive JDF job tickets and JMF messages and emit them back — the dialect quirks of Esko Automation Engine, HYBRID Cloudflow, and your MIS normalized onto one canonical model instead of parsed and dropped. The print-floor lingua franca, kept as first-class data.
One inbound envelope shape, with a per-source adapter for each dialect — internal webhooks and external systems alike map onto it. Add a system by writing an adapter, not by reshaping the model. Endpoint-authenticated and idempotent by design.
A versioned mapping spec turns any source document into a canonical entity — saved by id or supplied inline — and you can preview the result before a single write lands. Tenant-defined mappings absorb the field-naming differences between shops without code changes.
Pricing
Run the integration hub as a managed hosted service, or self-host on your own infrastructure — same engine, you pick who runs it.
Your infrastructure
Run the whole integration hub yourself on your own Postgres. No quotas, no per-record fees — ever.
Pros
Cons
managed · onboarding now
Let us run the hub for you. Managed database, connectors, and the canonical data plane — wired into your Print With Synergy workspace.
Get early accessPros
Cons
Hosted plan details are shared during early-access onboarding.
Self-hosted · managed hosting
A toolkit of focused, standalone PDF utilities — extraction, preflight, viewing, assembly, imposition planning, and an asset store. Each one plugs into the prepress workflow you already run. Self-host any tool, or let us host it for you on host.withsynergy.io.
Structured PDF extraction API that turns complex files into consistent JSON.
Objective file-comparison engine — measured coverage and geometry differences for plate ↔ 1-up and document ↔ document, never a verdict.
Detection-only PDF preflight engine — 500+ checks plus the PDF/X-4 conformance suite.
Embeddable PDF viewer with separations, TAC, layers, and annotation overlays.
GWG 2022 conformance assay — benchmark a preflight engine against the spec.
Content-addressed digital-asset plane — versioned blobs, a presigned data plane, and on-prem agent recall.
The print-data integration hub — canonical jobs, orders, and customers kept in sync across your MIS, ERP, and prepress tools.
The deterministic PDF writer — trapping, marks, imposition, soft-proof, and white-underbase as audit-logged producers.