From an architectural point of view, Awingu can be summarized with three keywords:
Awingu leverages on your company’s current architecture and is deployed as a virtual appliance on most hypervisors. This can be a private or public cloud. From there, Awingu will connect into a classic back-end environment. It will link with Active Directory or LDAP for user management. It will connect to application servers running Microsoft RDS for legacy applications or desktops. It will setup a Single-Sign-On with SaaS services. Finally, it will connect to classic file systems via WebDAV and CIFS and with cloud storage environments such as Microsoft’s OneDrive.
For end-users, everything is available in a browser via Awingu’s online workspace. No need to install agents, plug-ins etc.
In its simplest of forms, Awingu will (a) aggregate applications and files, (b) act as an HTML5 gateway for applications and desktops running on the applications servers and (c) act as an Identity provider. For the sake of simplicity we’re not discussing security, compliance, audit, collaboration and other functionalities here.
In terms of scalability, Awingu is ‘stackable’. Our guidance is to host up to 100 concurrent users on one single Virtual Machine and simply add Virtual Machines for additional users. Finally, Awingu’s software is multi-tenant, can connect with multiple Active Directories, can be branded and is open API based. As such, it is also a Service Provider-ready solution.