Zedmos

Deployment

Four ways to run it, one way to manage it

Deploy a Zedmos firewall, build it into hardware you ship under your own name, run a hub that terminates the other sites, or start with the engine on a box you already have. The console does not care which you chose.

4
Deployment models
2
Supported platforms
5
Sizing classes
Docker
Console install

Ways to run it

On a firewall that is already in production

The package installs alongside the platform rather than on top of it. Interfaces, rules, NAT and VPNs are untouched; you gain inspection and central policy. This is the shortest path and the one most sites take.

As an appliance we supply

Three reference platforms covering branch, campus and datacentre roles, sized against the same classes the sizing guidance uses. Delivered configured and enrolled, so the first console login already shows the site.

Inside hardware you ship

OEM builds carry your name, your interface prefix and your console domain. Nothing in the running system announces a supplier, and updates come through your channel rather than ours.

As the hub the other sites come home to

A concentrator terminating encrypted overlays from the branches, with an optional backup hub the console can move the spokes to. Sites come back without an engineer touching the branch.