Where should your Windows host live:
office or cloud?

A host is a Windows machine that runs the Onscryn agent. You create an enrollment token in the admin, run the agent on the machine with it, and the host comes online. Sessions are placed on hosts with spare capacity, and only on your hosts.

A machine in your own network is a natural choice when the application is tied to things that already live there.

• The app talks to a database or file server on your network.
• You already have the hardware and the Windows licences.
• Data has to stay in a place you physically control.

A cloud machine suits teams that want to add capacity without buying hardware.

• The app, or the systems it reaches, are already in that cloud.
• You want to add or remove capacity as demand changes.
• People are spread across regions and you want hosts nearer to them.

A few questions decide most placements.

• What the application must reach, and how close the host needs to be to it.
• Where your people are, since distance to the host affects how responsive it feels.
• Licences, since Windows and the application still need them wherever the host is.
• Capacity, including whether some people or apps need a more powerful class of host.

Your host reaches Onscryn over an outbound, encrypted connection, so nothing on your network has to be opened to the internet. The application runs in its own separate account for each session, and only what your rules allow leaves the host.

You can begin with one host and one application, prove the experience, and add hosts as demand grows. How many hosts you can connect, the performance classes you can assign and the warm pool all depend on your plan.