Installing a Cameyo self-hosted server within your own network or data center is simple but requires a few simple steps.

Cameyo's server installer is available here:

  1. Prepare a server or virtual instance

    Cameyo Server requires an up-to-date Windows Server 2016 or higher. No specific pre-requisites or hardware is required. Please make sure your server is updated using Windows Updates before starting. If you plan to provide a cloud instance, create a clean Windows Server instance close to your end-users. For Microsoft Azure, you can find a tutorial here. For Amazon Web Services (AWS) EC2 machine, see tutorial here. For Google Cloud Platform (GCP), see here. For a VMware virtual machine, see here.

  2. Configure inbound ports access

    Configure your server to receive incoming ports (as well as some external addresses if your organization is blocking them) so that Cameyo Play Server can serve at least HTTP / HTTPS. See Network ports and addresses used by Cameyo

  3. Transform your pristine Windows Server into a Cameyo server

    • Download Cameyo's server installer from the link at the top of this page and run it on your clean Windows server. Confirm the validation messages and click "Install":null

    • Once component installation is finished, you will be presented with the server registration dialog:

      Configurations steps:
      • Login and password: your Cameyo credentials.
      • Universal host name: your machine's host name or IP address as accessible from anywhere. This field is typically the same as you enter for remote controlling this machine.
      • Externally-accessible HTTP port: Cameyo Play will configure this to be port 80. If you did not change the external in step 2, leave this at 80.
      • Externally-accessible HTTPS port (optional): same as the above, but for secure https access. Note that Cameyo Play does not configure https by default. If you wish to configure https access, you will need to manually set up Tomcat on the machine to use your SSL certificate.
      • Externally-accessible RDP port (optional): the external Remote Desktop port number for this machine. This is often 3389.

Once you are done configuring, you can click "Test" to test your settings. When you are ready to activate your server, click "Activate". By the end of the activation process you should see the following screen inviting you to reboot the server to finish installation:null

4) Test your new server

  • Navigate to and make sure you are logged in with the same credentials you activated the server with.
  • Check that your new server is listed:

  • Click on this server and connect to it using the wizard. The resulting URL should display your newly-activated server's address:

Congratulations, you are done. You can now install applications on this server and publish them as URLs.

HTTPS (optional)

If you'd like to turn your server into HTTPS, follow the instructions here.

Session measurement (optional)

For testing and capacity planning, you can observe your server's activity in real time by connecting to it as an admin and launching the Task Manager | Users from the Windows desktop.

Advanced: for more detailed monitoring you can use the Event Viewer:

  1. On your server, open the Event Viewer (eventvwr.msc)
  2. Go to to Applications and Services Logs -> Microsoft -> Windows -> TerminalServices-LocalSessionManager
  3. Open Admin or Operational
  4. You will see the sessions list. Date/Timestamped/IP/UserName etc.
  5. Alternatively, you can also navigate to Applications and Services Logs\Microsoft\Windows\TerminalServices-RemoteConnectionManager

Hardware capacity

Hardware capacity depends on the application that needs to run on the server. It can start from 1 CPU per 12 concurrent users and 2 GB RAM per user for lightweight apps, all the way up to multiple CPUs per session. You can estimate the required capacity for your app by connecting to a server as an admin while several app sessions are being used on it, and looking at the Task Manager's "Users" tab.