Going to PRINTING United 2026?
A buyer can describe the job one way, a producer catalogue another, and a workflow system a third. Gnaww turns that mess into controlled print requirements, then uses SpecMatch™ to identify production capability that fits.
Available today
A reviewed public developer API, a command-line interface and official SDKs for TypeScript, Python and PHP.
Start with the way print is actually described
The problem is that print rarely starts there. A customer sends an email. A sales team writes a note. An ecommerce platform uses its own product names. A producer has years of capability hidden inside catalogues, APIs, spreadsheets and production systems.
Gnaww gives those different descriptions a controlled meaning that software can work with.
Buyer
“We need 5,000 flyers for a launch next month. Matt finish, probably A5.”
Gnaww keeps what is already known, identifies the decisions that still change production, and asks for those rather than making the customer learn a print specification form first.
Once the physical requirement is resolved, it can be represented as a controlled print requirement and, where eligible, given a stable Recipe identity.
Producer
That capability may be spread across product catalogues, ecommerce configuration, APIs, spreadsheets, MIS rules and production knowledge.
Gnaww normalises the production meaning into governed producer capability so SpecMatch™ can compare it with demand. The producer does not need to replace the systems that already run the business.
Software
A platform should not need its own growing collection of rules for paper sizes, materials, finishes, folds, binding and every other way print can be described.
The Gnaww API accepts controlled or ordinary-language print requirements and returns explicit interpretation, unresolved decisions and capability results that the calling product can use in its own journey.
From intent to compatible production capability
It interprets the request, keeps unresolved decisions visible, creates canonical production requirements and compares them with structured producer capability.
SpecMatch™ explains why a capability fits, what blocks it and what still needs review. When the exact physical job is fully resolved, Gnaww can give that production identity a stable Recipe so the same thing means the same thing when it appears again.
Capability and commerce
A capability match tells you whether a production route can satisfy the requirement. It does not, on its own, tell you that the producer is available now, what the current price is, or that the producer has accepted the job.
Those are transaction-stage facts and stay separate. Where a connected transaction route supplies them, they can be added without changing what the print requirement or capability means.
Software can be very precise around the wrong fact. Gnaww keeps the production meaning stable while current commercial and operational facts can change around it.
Controlled print meaning, capability fit, blockers, warnings and unresolved decisions.
Current price, availability, producer acceptance, ordering and fulfilment where supplied.
Use Gnaww in the systems you already have
Your ecommerce platform, MIS, catalogue and workflow can remain where they are. Gnaww sits in front of those sources when their production meaning needs to become controlled, matchable and understandable to another application or authorised agent.
Private capability remains controlled. Making capability machine-readable does not mean making every internal production detail public.
Use the public developer API, Gnaww CLI or official SDKs to add print interpretation and SpecMatch™ without moving canonical print rules into your own application.
The calling product keeps its own customer journey, account model and workflow while Gnaww owns the print intelligence.
Explore the developer docs →See Gnaww with your own example
We will start with your example and show what Gnaww can interpret, what still needs clarification, how the requirement becomes controlled and how SpecMatch™ evaluates compatible production capability. Current price, availability and producer acceptance stay separate rather than being implied by the match.
Arrange a Gnaww demoQuestions people usually have
No. Gnaww is designed to start with incomplete, inconsistent or ordinary-language print requirements. It keeps what is known and asks for the decisions that genuinely change production.
A Recipe is the stable identity of a resolved physical print requirement. It gives software a reliable way to recognise that two requests describe the same producible thing without mixing in changing facts such as run quantity, price or current availability.
No. SpecMatch™ evaluates production capability. Current price, availability, producer acceptance and ordering are separate transaction facts.
No. Gnaww is intended to sit in front of existing capability sources and operational systems when their production meaning needs to be normalised and exposed in a controlled form.
Yes. Gnaww has a reviewed public developer API, a CLI and official SDKs for TypeScript, Python and PHP. The developer documentation describes the current public operations and their truth boundaries.
A real print requirement is better than a polished example. Bring an email, a product description, a catalogue problem or a workflow that currently relies on somebody translating print by hand.
Bring something real
It can be an email, a product description, a catalogue entry or a half-complete brief. We can work through what Gnaww understands, what it still needs to know and how SpecMatch™ would evaluate the production capability behind it.
