Features & Pricing

It is enabled by default unless the customer decides to opt-out.
Please check the fleet-in-motion device’s technical requirements.

There are 2 modes of activation
– On-Display activation (for small deployments). A 6 Alphanumeric Code shows on the screen used to pair it with the cloud account.
– Off-Display activation (for large deployments). Customers prepare to create many displays in their cloud account and hand over a code to the remote person who will activate the hardware display using a 12 Alphanumeric Code and a PIN.

Displays can/must use private enterprise networks without any external intrusion. Display.Stream in this case will detect that the network is private and instruct the player to use outbound connectivity to get content from the customer’s cloud account.

Display.Stream may provide white labeling rights and assets to customers based in the US, Canada, UK, and Australia. Customers are required to sign a “Player White Label License Agreement” which defines branding and sales distribution and usage in the countries listed above.
Provided Sources with customer branding include:
“Web Player”, “Android Player”, “FireOS Player”, “Tizen Player”, “WebOS Player”, “ChromeOS Player”, “Raspberry Player”, and “Windows Player” Documentation:
How to publish all the players in Google Play, Samsung Seller Central, Amazon Apps, and Google Chrome Store.

Display.Stream, Inc. is responsible for the backup and availability of these assets in all regions across the globe securely unless the customer decides to make some of his assets public.

Customer files are stored in AWS and Google clouds in secure buckets. Accessible only by customer API Security Tokens. Display.Stream is not responsible for stolen tokens from customers’ systems but has the obligation to advise how to store and use API Security Token.

Display.Stream has no ownership nor rights to use customer assets nor distribute them unless stated by a special agreement “Assets Copyright Transfer Agreement” between the customer or its subsidiaries and Display.Stream, Inc.

When customers delete files, Display.Stream keeps the files for about 30 days then purges them from the cloud storage allowing customers to request these files in case of an erroneous operation.

The customer is an enterprise having multiple departments or locations and wants decentralized management of billing, assets, displays, and users either per country, region, subsidiary, or department.

The customer is a Business using Display.Stream offers his services to other customers and wants to manage each of his customers in a separate environment while having some resources in common.

When users add new resources such as Assets and Displays to the workspace they are part of, the Customer Account owner of this workspace will be responsible for the corresponding billing charges by default unless specified that a specific user should pay for his use rather than the Customer Account.
When adding Users to workspaces, the Workspace Administrator will decide who will be paying for anything that the User is doing.

While it is possible to share Assets, Stories, and Displays across all Customer Account Workspaces, it is recommended to do so ONLY with Assets to avoid creating a complicated Operational Delivery Process.

When customers delete Workspaces, Display.Stream keeps the data for about 30 days then purge it from the cloud allowing customers to request rollbacks in case of an erroneous operation.

Display.Stream may provide white labeling rights and assets to customers based in the US, Canada, UK, and Australia. Customers are required to sign an online “Workspace White Label License Agreement” which defines branding, custom domain, and usage in the countries listed above.

Users are bound by the workspace they operate in. The Account Owner may grant access to a User to a specific Workspace but only the Workspace Administrator can grant him appropriate Access Rights.

Users can co-exist in different Workspaces at the same time and they can switch from one to another. For example, a Consultant may be working with different customers in different Workspaces.
The Workspace Administrator can set a start date and an expiry date for a User to access the workspace.

If a User has the right to create API Security Keys, these keys are valid only for the period that User has access to the Workspace. These keys are under the same Access Rights as the User who owns them. If the User has no access right to Upload Assets, he will not be able to do so using his API Security Keys.

Resource and Stories Tags are the most common Tags where Customers organize and search content based on a set of Tag rules. Display and Spot Tags are very helpful when broadcasting content to multiple displays/spots while User Tags are mostly used to define Access Rights.

– API Data Source: An external or Customer API
– Table Data Source: It is a 100% hosted Database Table and Search Index in Display.Stream Cloud. It can be integration with the Scene Builder and
Customer custom applications.
– Stream Data Source: It’s Display.Stream most recent and trending type of data. It’s 100% hosted in Display.Stream Cloud. It’s a real-time stream of
data collected from Customer’s Customers and routed to the Customer dashboard to integrate into his stories and displays.

– Private Spots are used to allow other parties to show their content in specific order and date/time in your displays.
– Monetized Spots are used to sell air-time in your displays to advertisers to place their Ads. Display.Stream takes a 15% while the Customer takes 85%.