Intuiface's infrastructure requirements are quite flexible. As a result, multiple usage options are available, enabling selection of the most appropriate approach for a given set of IT restrictions and preferences. The following three scenarios are examples of possible Intuiface usage models, from the most open model (where all Intuiface cloud-hosted services are used) to the most closed model (where none are used).
Three Usage Model Options
Use Intuiface Cloud Storage or a private Amazon S3 bucket to store published Intuiface experiences. (Intuiface projects are referred to as “experiences”) and Headless CMS. All Intuiface cloud services such as remote experience deployment onto Player as well as Intuiface Analytics and Headless CMS are available.
No Experience Publishing
Experiences are not published to the Intuiface Cloud or to an Amazon S3 bucket. Intuiface experiences are either deployed manually or via in-house automated means. All devices running Composer and Player have at least occasional access to the Internet, so their licenses can be checked and renewed when required. Players can use Intuiface Analytics; locally stored data points are sent to the Analytics server when Player has access to the Internet. Experiences can also still access and use Headless CMS content stored on Intuiface Cloud.
Intuiface experiences are managed using a LAN file system; deployment onto Player (Windows version only) is an in-house responsibility. (With Players offline, it is not possible to remotely deploy or manage experiences). Also unusable are Intuiface Analytics, Headless CMS, and any of the cloud-hosted social media platforms supported by Intuiface. Intuiface’s offline licensing option is also required, involving manual license requests submitted to Intuiface Technical Support. All in all, about 70% of Intuiface capabilities will be accessible. (Still impressive by any measure!)
Document: Intuiface Cloud Infrastructure Guidelines
See our detailed guide about the Intuiface Cloud Infrastructure for a look at the global architecture, servers, endpoints, and more.
Article is closed for comments.