What is the (high-level) architecture for an Awingu deployment?

A simple Awingu architecture can be seen in below picture.


The Awingu virtual appliance can be deployed on one or more virtual machines. It can run in your cloud of choice: on-prem or cloud and we support all mainstream hypervisors.


Awingu will then be connected to a back-end setup that is typically already available:

-          A connection with AD or LDAP (or Azure AD)

-          A connection to application servers running RDP (Terminal Server) for (legacy) software or desktops. This means you will still require RDP licenses for users accessing legacy software

-          A Single-Sign-On connection to SaaS apps (leveraging the built-in connectors in Awingu, and/or, leveraging out integration with Azure AD and Okta)

-          A connection to file servers (WebDav, CiFS)

-          Optionally, Awingu can be connected to external SSL infrastructure, databases and Multi-Factor Authentication solutions http://www.awingu.com/what-are-the-options-to-securely-login-to-awingu/



Awingu will then act as an html5 gateway…

-          Software published with RDP (Terminal Server) will be available in html5, and thus in a browser

-          Files will be available in Awingu’s html5 file browser

-          SaaS or Web applications are obviously already available in html5, but the usage is simplified via 1 Single-Sign-On


… and will ‘aggregate’ everything consistently in an online workspace that runs in a browser. (see below)