QL Server Requirements

QL Server Requirements and Scalability

QL Server requirements depend on the number of concurrent player downloads your platform is expected to handle. You may also self-host your platform in a hybrid mode: QL Server hosted on premise with SQL or Blob / CDN hosted on Microsoft Azure.

QL Server Optional Modules for Scalability and Reliability

Security Certifications

Every version of QL Digital Signage Software is security certified by a renowned third-party company. Navori Labs uses state-of-the-art tools like the Windows Communication Foundation framework for its software development.  This ensures interoperability, multiple message patterns, service metadata, data contracts, multiple transports and encoding, and reliable queued messages. The work of generating and reading Web Services – Security-compliant SOAP headers is done by a set of filters and hosted on IIS servers. Incoming messages are passed through a series of these input filters, modified if necessary, and then generate a related set of programming objects. Outgoing messages pass through a set of output filters that serialize certain headers as defined programmatically by the Web service objects.

These protocols include the following:

• Digital signatures
• Data encryption
• Encrypted sign-in with username tokens

Data and message structure are fully protected by means of our own encryption and asymmetric algorithm at the transport and store level.

QL Server API

Our API lets users and system integrators customize QL Server. Web and C# developers can use our API to automate QL Content Manager. You can move players and edit their attributes, edit content, data feeds, playlists, and programming, or you can trigger content and programs on the fly.

Enterprise users often develop middleware applications to control QL Server from their Digital Asset Management (DAM), Business Intelligence, or Advertising booking platforms. The QL API can also be used to create a custom GUI for any vertical or customer application.