Choosing the Right Intuiface License And License Distribution Method

Let’s touch on the basics of licensing and your options for equipping clients with licenses. If you’d like a graduate course, feel free to contact your favorite Intuiface Sales rep for assistance.

All accounts begin with a Platform plan

Platform plans are the entry point for a paid Intuiface account. Each account must have a Platform plan, and every plan grants the account one Composer license, one Player license, and access to the Intuiface Cloud. (The Intuiface Cloud consists of Analytics, Headless CMS, Sharing and Deployment, and Account Management.

There are three Platform plans are they are differentiated as follows:

All Platform plans are available as a subscription on an annual basis. The Enterprise tier is also available as a month-to-month subscription.

Composer is the editor. 

Intuiface Composer, the editor, uses what is called a concurrent user license. You need as many licenses as you’ll have concurrent users – that is, users working at the same time. Five people will use Composer but only one at a time? Then you only need one license.

There is no relation between the number of Composer licenses and the number of experiences created, the number of changes made to an experience, or the number of deployments active in the field.

Remember, all Platform plans include a single Composer license. Additional Composer licenses can be purchased as needed.

Player is a universal runtime for all supported operating systems.

Player, the runtime, can be used across three deployment options:

1. In-venue (e.g. in the store, museum, workplace, tradeshow, etc.)
2. In a webpage
3. As an app on a personal mobile device

For in-venue and personal app use, Player has a concurrent device license. You need as many licenses as you’ll have devices running experiences in the field. Five devices will be running experiences at the same time? Then you need five licenses.

The webpage option uses a views-based license - i.e. the number of times the experience is loaded in a web browser.

For in-venue deployments, Player runs on the following operating systems:

• Windows
• iOS on the iPad
• Android
• BrightSign
• Chrome
• Samsung Tizen
• LG webOS

For web and mobile app deployments, Player runs on

• Windows
• iOS (including mobile phones)
• Android
• macOS
• Linux

Our technical specifications page identifies supported models and configurations required to ensure optimal performance.

The in-venue Player is available through a monthly or annual subscription. Web and mobile app deployments are solely available on an annual basis.

Intuiface Cloud is available to all Platform tiers

At all Platform levels - Essential, Premier, and Enterprise - Intuiface users can take advantage of all features found within the Intuiface Cloud. That means use of

• Analytics
• Headless CMS
• Sharing and Deployment
• Account Management

As noted above when discussing the Platform tiers, differences with the Intuiface Cloud primarily concern scale, such as the data point maximum for Analytics.

Equipping your clients with licenses

You can transfer your licenses to whomever you wish. This means it is not mandatory for your clients to buy Player licenses (or even Composer licenses) for themselves. It comes down to how you want to conduct your relationship with each client. You may choose a business model in which clients directly shoulder the license costs, or you may choose a model that bakes license costs into your services fee.

Here’s a cool thought: If you make a multi-year pre-purchase of Player, you could actually charge each client a fee lower than the annual list price and still earn a profit!

Whether your sell the license explicitly or hide it within a larger service fee, we recommend the use of secondary accounts for license distribution. See the next section.

Secondary Accounts

Juggling multiple clients, each of whom may have multiple projects, is tough enough without also having to juggle licenses, Players, data points, and more. We created the notion of secondary accounts to simplify your management of multiple clients and to limit client visibility to experiences specific to their project(s).

The idea is that your Intuiface account becomes an umbrella account - aka a "primary" account - for any number of secondary accounts. As detailed in our article about secondary accounts, your primary account can do things like

• share a single data point pool across multiple secondary accounts
• deploy experiences to secondary account Players
• share storage accounts for experience publishing and sharing
• easily loan and retrieve licenses as needed

We're sure you'll appreciate the benefits of secondary accounts so keep them in mind.