Skip to content


There are number of key concepts that you should know and understand about the platfom.


The Appearition platform has been designed as a multi-tenanted system. Essentially a tenant is an isolated part of the platform where content is stored in its own data store. Users of the platform are allocated to one or many tenants.

How you treat a tenant depends on your organisational needs. A tenant can represent anything from a business unit (e.g. HR, IT, Finance) to a faculty in a university (e.g. Faculty of Marketing, Faculty of Medicine).

Please contact us for further assistance.


A channel represents a group of related records inside a tenant.

How you treat a channel depends on your needs. In the Appearition cloud, a subscription to an account will result in a dedicated channel being allocated to the account. All content created by that account is stored in the channel and not available to anyone else.

In other solutions, a channel can be used to represent a specific app. Consider an organization that has subscribed to an entire tenant. Each app built and released can be allocated to a dedicated channel for storing and retrieving content.

Customise the Channel label on the portal

Product and Project are terms which have been used in different solutions running on the Appearition platform. On the portal web interface, a Channel can be configured to have another label (e.g. Product or Project). This capability exists to give flexibility when designing enterprise solutions.

The concept of Channel is universal, but the terminology may be misleading to certain organisations. In these cases, the label can be modified to some other text which aligns with business processes.


Hence, throughout the API, you will see a field named: “productId”. This represents the “ID” of a Channel which can be sourced from the portal.


A module represents a specific function or feature on the platform. A module can extend an existing feature, provide an alternative implementation to an existing interface or introduce a whole new set of capability to the platform.

There are already numerous modules available on the platform and more are being added all the time. You can read about them in later sections of this documentation portal.


Depending on your level of subscription, you will be able to activate available modules via the Appearition platform portal.

Please contact us for further assistance

Data Integrations#

The Appearition platform can be configured to connect to your existing business data stores. Data Integration is the concept for connecting to external data sources for querying data.

Data Integrations are created as modules. So, if your data source has an accessible endpoint API, then the platform can connect to it. Currently there are modules for Splunk, MS SQL Server and Open data URI.

Please contact us for further assistance

Marker vs Markerless Experiences#

AR experiences can be triggered in two ways. Firstly using a marker which is scanned and recognised by an Image Recognition (IR) provider and the experience is augmented relative to the marker. The second trigger is markerless which uses SLAM technology (AR Core/AR Kit) to recognise a physical surface (eg. table top) so that the experience can be placed on top of that surface.

Register an IR Provider for Marker Based Experiences#

The Appearition Platform has modules to enable third party IR providers. To begin using this feature you’ll need to register an account with your preferred IR provider.

Vuforia IR Provider#

The Appearition Platform will be configured by default to have the Vuforia IR Provider module activated. You will need to bring your own Vuforia license . For more information visit the Vuforia Developer website.

Configure your IR Provider Account on the Appearition Platform#

Login to the Appearition Platform and under the Developer section click on Image Recognition. Click on Add Provider. Enter the required information by referring to your IR provider’s access settings.

For a Vuforia account you’ll find Database name, Server Secret Key, Server Access Key, Client Secret Key and Client Server Key under Target Manager in the Database Access Keys section for a selected database. License Key will be in the License Manager in the License Key section for a selected Development Key.

Installing On-Premise#

You manage the infrastructure, deployments, patches and updates. We’ll provide you with an installation pack with guided instructions.

Please contact us for further assistance: