Web Version Client Side

The web version of TTP 3.0 is a Single Page Application (SPA). This is an open standard and the benefits are that it is not reliant on plugins, performs across most recent devices and operating systems (Windows, Mac, iOS and Android) including tablets and phones. The architecture of the web version also means that the code can be re-factored and the entire application re-engineered for specific clients if need be.

Server Side

If you decide to host your TTP books on your own server, you’ll need to operate Windows Server.

Turning the Pages is not CPU-dependent and the main constraint will be bandwidth as it serves many images in quick succession for each user (all the pages of a book download as thumbnails at book launch, plus 6 high-resolution pages). This means you should be conservative in using TTP on a VM if many other services are running on the server that would consume port bandwidth. For storage purposes, you should calculate in the region of 500k per page or 2500k for Deep Zoom books.


The kiosk version runs on the Windows OS with the Microsoft .NET framework. By default, the TTP Content Management System creates kiosks that don’t rely on external dependencies. All media files are stored locally, and database content is exported as local XML. This enables a kiosk to be copied to a USB drive and operated anywhere. However, kiosks can also be configured to fetch assets and metadata from a central server, which can be advantageous for content that is regularly updated. For more information, please contact us.

TTP Content Management System

The CMS is a standalone application designed to run on Windows. By default, it is set up to produce both web and kiosk versions, requiring a database connection. This connection can either be to the Armadillo TTP server or a server of your choice.