Selecting the Type of Gateway

We offer two core types of gateway deployments - through a virtualization platform, or with a physical device. A third option, through a container service like Docker, Kubernetes or Neeve Secure Edge is also available in scenarios where VM or hardware are unavailable.

Virtualization platforms enable the creation and management of multiple virtual instances of a physical computer system. We currently support a VM based deployment, and support VMWare, Hyper-V, and Nutanix.

The hardware gateway is a physical device that gets plugged directly into the network, requiring no additional servers, no additional software. The device gets shipped to the site, and then housed in the appropriate server room / server rack.

The containerized option requires someone familiar with the container platform, as we are unable to provide consistent Docker/Kubernetes/Neeve support due to the myriad of versions and configurations that have to be maintained. That said, if the expertise is present, this option can be relatively quick and easy.

Selecting the type of gateway deployment from the options above really only depends on your networking team and what they're most comfortable utilizing. All options provide the same Mapped features and functionality, so there's no benefit to choosing one over the other when it comes to our side, it all comes down to what deployment method is best for you and your team.

The process essentially breaks down like this:

• Does your network have a Virtual Machine platform available, like VMWare or Hyper-V, and internal IT/networking support to help deploy an image utilizing it? If so, then choosing the VM gateway option is likely the best solution for you.
• If a VM platform isn't available, or your IT team is unfamiliar with the platform, then the hardware gateway option is likely the best solution. The hardware gateway does not require any additional software or platforms, and can be installed by directly plugging it into the network.
• If a VM platform is unavailable, additional hardware isn't something you're comfortable with having on your network, and you have a container platform with an available domain expert - then the containerized option may be the best bet for you.

Since all options operate the same way to detect devices, extract the data and send it on its way, determining which deployment best suits your existing network is all that's necessary. If you have any questions or need any additional help, please don't hesitate to contact support.