Skip to content
SPECIFICTION
Get listed

Aviatrix Kubernetes Firewall vs Liqo

Aviatrix Kubernetes Firewall

aviatrix.ai

Liqo

liqo.io

Side by side

FigureAviatrix Kubernetes FirewallLiqo
Price from——
Free plan——
Free trialYes—
Open source——
WebYes—
Windows—Yes
macOS—Yes
Linux—Yes
Self-hostedYesYes
Plans published10
Spec score · Container Networking Software8.5 (#2)7.1 (#18)
IntegrationsAviatrix describes Terraform and Kubernetes custom resource definitions as ways to automate firewall policy deployment.The installation guide describes using Helm 3 to install Liqo, and the CLI supports kubectl-style Kubernetes API access.
PurposeAviatrix Kubernetes Firewall secures Kubernetes traffic across clusters, clouds, and environments.Liqo is an open-source project for creating dynamic Kubernetes multi-cluster topologies across on-premise, cloud, and edge infrastructures.
SupportAviatrix’s contact page links to a Support Portal and lists the support phone number +1 (888) 311-8328.The official site links to Liqo’s documentation, quick-start guide, and community Slack.

Plans

Aviatrix Kubernetes Firewall

  • 30-day free trialFree

Aviatrix Kubernetes Firewall pricing →

Liqo

No plans published.

Liqo pricing →

In their own words

Aviatrix Kubernetes Firewall

Aviatrix Kubernetes Firewall governs traffic entering, leaving, and moving between Kubernetes workloads across clusters and environments. It applies Zero Trust controls at the cloud network layer, outside Kubernetes clusters, so deployment does not require sidecars, agents, CNI replacement, or application changes. Policies can target pods, namespaces, services, and labels using Kubernetes-native identities. A centralized control plane manages policy across multicloud and multicluster environments, with automation options including Terraform, Kubernetes custom resource definitions, GitOps, and policies in Kubernetes manifests. Supported environments include AWS, Microsoft Azure, Google Cloud, and on-premises deployments, including EKS, AKS, and GKE. The product offers traffic visibility, observability, and anomaly detection, along with distributed firewalling, threat prevention, URL filtering, egress control, micro-segmentation, TLS decryption, DNS firewalling, and advanced NAT for overlapping address ranges. It can use a shared security model for containerized and legacy VM workloads. There is no free plan.

Visit aviatrix.ai

Liqo

Liqo connects Kubernetes clusters into multi-cluster topologies, allowing them to share namespaces, resources, and workload capacity. It can extend consumer namespaces and replicate configurations, secrets, services, and other resources. A remote cluster appears as a virtual node, so the consumer cluster can schedule workloads there. Liqo’s network fabric connects pods across peered clusters using WireGuard VPN tunnels by default, and it describes cross-cluster storage support for stateful workloads. Peering can be declared with Kubernetes resources and managed through GitOps tools such as ArgoCD. The liqoctl CLI installs and uninstalls Liqo, manages peering, configures namespace-level offloading, and reports status. Liqo targets heterogeneous on-premises, public cloud, edge, and multi-cloud environments, with support listed for Kubernetes, Kubeadm, K3s, K0s, AKS, EKS, GKE, Aruba Cloud KaaS, and OpenShift. It is free and open source under Apache-2.0. Liqo requires Linux kernel 5.10 or later and recommends at least 2 CPUs and 2 GB of RAM for a cluster.

Visit liqo.io