The AppsAnywhere server is provided as a virtual appliance, so it will be up to you to import this into your environment to create a new server.

Full details on how to import the virtual appliances are available in the Deploying the AppsAnywhere Appliance section.

Supported Hypervisors

At the time of release, the following hypervisors are supported:

  • Microsoft Azure

  • Microsoft Hyper-V 2012 R2 or later

  • VMware vSphere v6.0 or later

  • OpenNebula with KVM

If you need us to provide support for another format or hypervisor, please let us know or contact AppsAnywhere Support and we will try to help.

To import the virtual appliance to OpenNebula KVM you will need to convert from the provided VMware OVA template.

Server Specification

The following resources are required for each AppsAnywhere server:

  • 4 vCPU

  • 8GB RAM

  • 32GB Disk space

  • Gigabit Ethernet adapter (1Gbps connection is ideal)

  • IPv4 address (IPv6 is not supported)

You will need to configure your hypervisor to provide these resources for your new AppsAnywhere server, unless you are importing our VMware OVA template, in which case the specification will be configured automatically.


The AppsAnywhere appliance can be configured to use either DHCP for automatic IP address assignment, or a static IP address.

A fully qualified DNS name will need to be registered and assigned to the appliance prior to its configuration by Software2.

Please create a DNS ‘A’ record containing the DNS name you wish to use. (e.g. appsanywhere01.uni.edu).

The appliance will use the assigned the hostname as advertised by your DNS servers.

We recommend that you make your AppsAnywhere servers private, and configure a load balancer with health checks to act as the gateway for all external (and internal) traffic.

Please see Network Requirements for full details.

SSL Certificates

An SSL certificate issued by a trusted public certificate authority is required for AppsAnywhere, to secure access, and so that users accessing your app store on personal devices do not see security warnings in-browser.

It is the customer's responsibility to obtain and maintain up-to-date certificates.

The certificate issued must have a ‘common name’ value matching the service URL that your end-users will use to access your AppsAnywhere service. Typically this will be the load balanced AppsAnywhere FQDN (e.g. appsanywhere.uni.edu).

Software2 will need to apply your certificate to your AppsAnywhere servers on your behalf.

Certificate formats:

  • We request that the certificate is supplied to Software2 in a .PFX (Personal Information Exchange) format.

  • Alternatively, separate files for the certificate (.CRT), private key (.KEY) and chain (.CRT) can be supplied.

Any passwords associated with the .PFX and/or .KEY (private key) file must be supplied if required.

Please save your certificate to a location that will be accessible to Software2 Support and from your AppsAnywhere servers.

If you prefer to use SSL offloading provided by your load balancer, you will need to apply the certificate to your load balancer and select it for use within the relevant load balancing rule.