New ezeep API Offers Software Developers an Alternative to Google Cloud Print

BERLIN/DENVER, Sept. 15, 2020 – ThinPrint’s cloud printing solution, ezeep, today launched its developer API, which enables easy integration of its cloud printing services for any device or platform. Software developers and companies which previously relied on Google Cloud Print, which will be discontinued at the end of the year, can now easily migrate their apps to ezeep, without the need for cloud printing expertise.

In contrast to Google Cloud Print, which never evolved out of its beta stage, ezeep has been designed from the outset to fully meet the needs of enterprise customers. The announcement of the ezeep API allows software developers and enterprises to highly automate and streamline backend and web applications in terms of printing. Business processes can then be accelerated significantly. Since ezeep also handles all print rendering in the cloud, hardware requirements at the endpoints can be reduced, saving considerable costs in terms of procurement and maintenance. Technically complex issues, such as communication with the printer or converting documents into all printer languages, are handled by the ezeep cloud.

“Enabling apps to print with our API, is not a piecemeal process, or a tool conceived for individual users, but part of an enterprise-wide cloud printing solution that can be used for all devices and platforms,” says Christoph Hammer, Senior Vice President Cloud Services at ThinPrint. “Possible applications range from restaurant chains or delivery services which print orders placed online to cloud storage, or CRM systems that want to enable managed printing for their corporate customers. The possibilities are boundless.”

Software vendors which want to embed the ezeep API into their solutions can contact the ezeep team at Comprehensive documentation ensures the smooth integration of printing.

Have news to share? We want to help you spread the word. Submit your media releases to Please submit releases in Word or text docs or in the body of an email. Please do NOT send PDF documents.