The Awingu 5.2.4 maintenance release is now available!
Don’t be in a vendor lock-in that dictates your ways. With Awingu, you are in control. Your cloud of choice, your endpoint of choice.
Awingu was built with security in mind, including built-in MFA, SSL, granular controls, auditing, etc.
Awingu is simple to operate; get new technical staff up and running in no time
Start small with a single Virtual Machine and easily scale from there with our built-in load balancing tools etc.
Awingu is a Unified Workspace solution. It’s an alternative to classic VDI solutions, and end users simply access their workspace – including legacy Windows, Linux applications and full desktops, file shares, etc. over RDP in a browser.
The access runs in a fully secured context, and there is nothing to install on the end-user device. As such, it offers full mobility without any device lock-in. The architecture is easy to set up and maintain, it’s scalable and cost-efficient.
Host and manage the Awingu virtual appliance,
and provide a digital workplace to your customers.
Host and manage full desktops or app offerings
as a full outsourcing service for micro & SMB customers.
Setup Awingu’s Virtual Appliance with multiple tenants. Each tenant…
End-users log in via the browser and get HTML5 access to their published apps, desktops & file shares. This means there is no management required of the end-user devices. Interesting: Awingu’s usage audit and/or Open API can be used to trigger
The simplicity of the model, both in initial setup, as in the addition of new customers is what makes this attractive for a lot of MSPs.
Technically, you’re not using a different Awingu product to build a ‘Workspace-as-a-Service’. And that’s the beauty of it. The architecture is equally simple, but here the full infrastructure is hosted (and managed) by the M/CSP.
Similar to the Awingu-as-a-Service architecture, the access to the Awingu virtual appliance is shared between end-customers. Each customer will typically get its own tenant which…
End-users log in via the browser and get HTML5 access to their published apps, desktops & file shares and thus no management required of the end-user devices. Awingu’s usage audit and/op
Open API can be used to trigger billing.
M/CSPs can decide to use Awingu as the main portal of entry, but, they can also integrate Awingu into other portals. Have a look at how Awingu direct links work here.
In this blog post we're looking at the primary options to offer Awingu in a M/CSP model. The possibilities are vast and a lot of M/CSPs have shown to be very creative.
Do you have any more questions about Awingu? Reach out to our Awingurus!