[a9t9]

Ouch. I was not aware of this, so thanks for the info! I guess the reason for this surprisingly restrictive license is/was the version 1/first release character of the software (namespace Windows"Preview".Media.Ocr).

The good news: In Win 10 the separate library is gone and the OCR feature is a regular part of Windows (Windows.Media.Ocr namespace). Along with this, the separate OCR runtime license is gone. -> I could not find any hint that the new OcrEngine class (or Windows Store apps in general!) have similar "no server use" restrictions -> I will move the OCR app to a Win 10 platform asap.

And while I can not speak for Microsoft, I have good reasons to assume that the ocr api service is doing Microsoft a favor by advertising the great Win 10 OCR features. My web service allows for quick prototyping and testing on any platform. But ultimately no web api can be as responsive as a native OCR solution - which is only available on the Windows platform.

I would not be surprised if the OCR engine shows up in Windows Server 2016, directly usable from ASP.NET.

[a9t9]

Update: I confirmed that Microsoft's OCR.dll is indeed part of Windows Server 2016. More info: http://blog.a9t9.com/2015/10/microsoft-ocr-on-windows-server...