Skip to content

Wallarm Node Deployment Options

Wallarm supports multiple deployment models — from Security Edge and Kubernetes to cloud VMs and API gateways. Choose by who hosts the Node, the infrastructure that handles your traffic, and whether you need inline or out-of-band protection.

Security Edge

Fully managed at the edge: no Node to run. Traffic goes to Wallarm’s edge, is filtered, and forwarded to your origin. Choose Security Edge for zero-infrastructure API security.

Kubernetes

Choose a Kubernetes option if your APIs run in-cluster and you want in-cluster protection or a connector to your mesh/gateway.

Cloud platforms

Choose a cloud option if you run in a public or private cloud and want ready-to-use artifacts (AMIs, Docker, Terraform, etc.).

Amazon Web Services

Artifacts for Wallarm deployment on AWS

Google Cloud

Artifacts for Wallarm deployment on GCP

Microsoft Azure

Artifacts for Wallarm deployment on Microsoft Azure

Alibaba Cloud

Artifacts for Wallarm deployment on Alibaba Cloud

Heroku

Build a Wallarm Docker image and run it on Heroku

Private Cloud

Deploy Wallarm in a private or hybrid cloud

Microsoft Azure

Artifacts for Wallarm deployment on Microsoft Azure

Azure Container Instances

Use the Docker image with Azure Container Instances

Alibaba Cloud

Artifacts for Wallarm deployment on Alibaba Cloud

Docker on ECS

Use the Docker image with Alibaba Elastic Compute Service

API gateways

Choose an API gateway connector if traffic already flows through a gateway and you want to add protection alongside it.

CDN

Choose a CDN or edge integration if your traffic is fronted by a CDN and you want protection at the edge.

API management platform

Choose an API management connector if you expose APIs through one of these platforms and want to add security without changing it.

TCP traffic mirror

Deploy the Wallarm Node for TCP traffic mirror analysis when you need out-of-band analysis of network-layer mirrored traffic. Wallarm analyzes TCP streams for attack observation without affecting production flow.

Packages & Containers

Choose packages or containers if you run on VMs or bare metal and prefer them over managed options.

On-premise

Run the full stack (Nodes + Cloud) in your datacenter. Choose On-Premise for compliance, data residency, or internal policy.

Special setups

Deployment options that don’t follow the platform matrix: known scenarios (multi-tenant, separate postanalytics, custom NGINX) and custom requests when nothing above fits.