Protecting networks since 2010

We started out in 2010 with network security and systems integration projects. For years our vendor-certified engineers deployed, operated and handed over Fortinet, Sophos, SonicWall, WatchGuard and Palo Alto solutions.

That field experience showed us two recurring problems: licensing costs rose unpredictably at every renewal, and organizations had to manage three separate products for firewall, Law 5651 log management and hotspot.

SignWall was created to address both, and it was written from the ground up. Rather than forking an existing open-source firewall and fitting an interface over it, or reselling a manufacturer's appliance under our own name, we built the components ourselves — from the packet processing pipeline to the policy engine, from IPS to VPN termination. It was the longer road; in return we know, and can change, why every layer of the product behaves as it does.

It brings stateful filtering, IPS/IDS, application control, web filtering and VPN onto one platform, and meets SignLogger on the compliance side and SignClient at the endpoint within the same ecosystem. With appliance models (S, M, L, A) and a virtual appliance (V), the same management language covers everything from a small business to a multi-branch enterprise.