A Production Pattern for AI Image Recognition Without Hardwiring Model Logic Into Your Backend

Direct model integration is not a crime. But if image recognition in your product is not the whole point of the system and is just one feature, an unpleasant thing shows up very quickly: the backend starts doing work that is not really its job. I am just describing the case of my own. Maybe it's not so important for you. But it's something - for me. This is not a holy war against SDKs. SDKs are not the real issue here. The real issue is where all the mess around the model should live so the application does not slowly start rotting from the inside. Because one thing is when AI is the product. In that case, yes, build around it. It is a different story when AI is just one function inside a larger system. A user uploads an image, and you want structured data out of it. A receipt. A document. A label. A business card. A book cover. It does not matter. The object changes clothes, but the mechanics stay the same. That is where I like a simple boundary: the app owns auth, validation, and bus