- Easy to connect and leverage external services out of the box (e.g. MFA, printing, auto provisioning, etc.)
- Use Awingu's Open API for automation
Multi-tenant & easy to scale
- Service provider ready with built-in multi-tenancy, even from one single VM deployment
- ‘Stackable’ architecture: just add VM’s when more users are needed
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, LDAP or an external IdP for user management. It will connect to application servers running Microsoft RDP for legacy applications or desktops. Web applications (e.g. intranet) can be connected via the “Awingu Reverse Proxy”. 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.
Allow our Chief Operations Officer Steven Dewinter to explain the Awingu architecture in detail in the video below.
GET IN TOUCH!
Do you have any more questions about Awingu? Reach out to our Awingurus!