One question comes up again and again in conversations: “Can we have just the detection?” There is a reasonable wish behind it. If you run a CAQ system, an ERP or your own portal, you do not want to send your users into a second program merely to get a drawing numbered. The characteristics should come into being where the work happens anyway. That is what StampKit is for.
The core, not a copy
StampKit is the detection core of DrawingStamp Pro, extracted into a library of its own. One point matters to us that sounds like a formality and is not: this is not a reimplementation of the method, nor a frozen second version, but the same code that finds the characteristics inside the application itself. Build StampKit in and you get every improvement to the detection — without having to expect the embedded variant to fall behind the application over the years.
A library rather than a service — and why that is the point
The obvious way to build this today would be a web service: upload a drawing, get characteristics back. We deliberately decided against it. StampKit is a native library that runs inside your own application’s process — no service to start, no database, no network connection. It is addressed through a deliberately lean C interface; anything that can load a C library can call it, whether your system is written in .NET, Java, Python or C++. Windows, macOS and Linux are served alike.
The real reason for this design is not technical but contractual: the drawings stay in the building. There is no service that accepts drawings and no path along which a drawing could leave. With parts under a non-disclosure agreement that is precisely where approval otherwise stalls — and the question “where are our drawings processed?” is answered with “on our own machines” a great deal faster than with a data processing agreement.
What comes out
An engineering drawing becomes structured inspection characteristics: dimensions, tolerances, GD&T callouts and surface finish callouts — each with its position on the drawing, its category and the evaluated tolerance range. What your own system builds from that is its business: an inspection plan, a characteristic list, a record in your database, a suggestion for the inspector to confirm. StampKit supplies the data, not the interface.
Three places where this pays off
- Inspection planning in CAQ: planning starts with complete characteristic data instead of a list to retype. That saves time — but above all it prevents the transposed digits that creep in during manual transfer and that nobody finds later.
- Costing and work preparation: “how many inspection characteristics does this part have?” is a question whose answer affects the price. It should be available when the quote is calculated — not once the drawing reaches the inspection room.
- Metrology and in-house portals: characteristics and their tolerances go straight into the software of the coordinate measuring machine. And because the detection works statelessly, several drawings may run at once on several cores — including batch runs overnight.
Honestly: where StampKit stops
StampKit is the detection core, not the whole chain. Reading the drawing — PDF, TIFF and the OCR for scans — belongs to the reading layer of DrawingStamp Pro and is licensed along with it. And what an integration looks like in practice depends so heavily on the target system that we cannot promise it here in good faith: so there is always a conversation about the specific case first — which system, what kind of drawings, what volume. A portal that grinds through whole drawing sets overnight is a different matter from a handful of drawings a day in work preparation. For the same reason the licensing page carries no speculative price tag, but price on request.
If that sounds like your case
All the technical details, the places it is used and the licensing model are set out on the page integration and licensing. If you would rather talk about your own case straight away, a few sentences about the system and the drawings are enough to start — this way to the contact form. Even if StampKit turns out not to be right for you, we would rather say so early than late.