signageOS Frequenly Asked Questions

Our ultimate goal: Bringing you a complete Backend as a Service(BaaS) designed for digital signage.

Who is the ideal customer for signageOS?

CMS companies that want to integrate a wide variety of digital signage hardware, software, and media players into their network. signageOS focuses on the compatibility with the varying integrations so the CMS can easily manage a complex network.

Does signageOS support offline playback (caching media files)?

signageOS uses a built-in failsafe that caches previously uploaded content. In the event of connectivity failure, the device will display the previously cached media until the device goes back online. The CMS has full capability to determine what will be cached and what will not.

What is an applet?

The applet is the HTML5 player/application used to play content on registered devices. CMS companies develop custom HTML5 players to display their content with the JavaScript unification layer provided by signageOS.

Can we develop an HTML5 Player (Applet) as freely as we want?

Yes, signageOS does not interfere nor limit the feature and playback variations offered by the CMS company. Freely develop and create as many Applets as desired for each organization.

What are the steps to getting started with signageOS?

  1. Introductory Call: Partner Introduction / signageOS Introduction
  2. Mutual NDA Signing
  3. Get API Documentation and Box Credentials
  4. Follow Up Call: Plan for Integration/Onboarding
  5. signageOS Assists in First Applet Creation
  6. Register and Verify First Devices (Integrating REST API)
  7. The CMS is Ready to Begin Displaying Content Across Device Types

Once you have the Box credentials, we will call to discuss your current caching and video playback protocols. After you create your initial Applet, signageOS will test and review your Applet. Once the Applet creation process is reviewed, integration of the REST API for device management occurs next. Each device integration is different so we have specific instructions on how to install the signageOS App on each device. After final testing, you are completely integrated and operating with signageOS.

Does signageOS support white labeling by the CMS?

signageOS fully supports white labeling by the CMS.

Will the CMS or end-users be able to see signageOS branding anywhere?

The CMS/partners will not be able to view any signageOS branding if they do not want to. The only persons that will be able to view the signageOS branding are the persons that integrate the CMS with signageOS.

Are media files or any content-related files passed through signageOS?

No. All content and data stay inside your CMS and are transported to all your connected devices directly.

Are hardware specific features available?

signageOS does support hardware specific features. Examples of hardware specific features include remote firmware upgrades, enhanced pin security, custom alerts, status reporting, internal memory status and much more.

How does signageOS handle firmware updates and testing?

signageOS can automatically update the platform to reflect new versions or updates for every major device type based on the desires of the CMS. As new firmware versions are released, signageOS tests and analyzes the benefits of the updated firmware. If the firmware updates enhance the functionality of the displays the updated firmware will be certified and recommended to the CMS.

How heavy is sOS in linux distribution?

Less than 4GB.

How does signageOS guarantee performance?

signageOS has failsafe protocols that store data on the devices in the event of the device going offline. If the device goes offline the cached content will still be displayed. Also, signageOS routinely tests for availability and scores are consistently 99.7% or higher, including scheduled maintenance.

How does the signageOS software recognize devices when verifying them?

Native applications crafted for each platform are able to recognize when a compatible device is available. The verification process allows for the recognized devices to then be securely added via verification hashes. Once verified, the device is then ready for full management control over the API or within the Box.

Do you use any Proprietary server component by Samsung (MagicInfo) or LG (SuperSign) with signageOS?

No, no proprietary components by Samsung or LG are used in conjunction with signageOS. All data traffic between the client and signageOS are encrypted and checked for security, validity, and reliability using multiple methods. All management and monitoring features are built-in and completely developed by signageOS.

More questions? Great! We are thrilled to answer them. Let's get in touch!

Ask now