Here are some important considerations when evaluating remote browsers for your organization: - Need for local agent—check if the solution requires deployment of an agent or local proxy on user endpoints. This can make deployment and operations of the solution much more complex. - Rendering engine—check how content is rendered and delivered by the remote browser service, and whether it uses the pixel pushing or DOM reconstruction technique. - Support for plugins—check which browser plugins are supported, and whether the remote browser solution supports common extensions like PDF and Java. - Support for web applications—check if the remote browser supports SaaS applications used by your users, such as Gmail and Office 365. In some cases, web applications may be blacklisted by the remote browser due to security concerns. - Cut and paste—if your security policy allows users to cut and paste content to the local device, check if the remote browser solution supports this, and whether copy-paste is enabled only for text, or also for rich objects like images and documents. - Operating system licensing—check which operating system is used for browser containers or VMs. If it is Windows, identify if licensing is included in the service price or if you need to provide licenses for each remote browser. - Virtualization model—check if browsers run in full VMs or containers. VMs provide stronger isolation, but they require more resources to run and take longer to start. Containers offer faster startup and better server utilization.