Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

LiteSpeed Ingress Controller

litespeedtech.com

  • Free trial
  • macOS
  • Linux
  • Web
  • Self-hosted
7.7 Club score Visit litespeedtech.com

What LiteSpeed Ingress Controller is

LiteSpeed Ingress Controller is the Kubernetes ingress component of LiteSpeed Web ADC, a software HTTP load balancer and application delivery controller. It supports HTTP versions including HTTP/2 and HTTP/3, the Kubernetes Gateway API, and installation through Helm. Its native ingress design requires no sidecars or Kubernetes modifications. ZeroConf applies Kubernetes configuration changes without restarting the load balancer. The solution includes LiteSpeed Cache for web-application acceleration and a Web Application Firewall that can use ModSecurity rules and templates. Realtime statistics and controller commands are available in the Web ADC WebAdmin Console. Web ADC can run on private dedicated hardware, hosted environments or cloud infrastructure, and works with all web servers, though LiteSpeed Web Server is preferred for the backend. The default LoadBalancer installation exposes it to the internet and load-balances all Ingress definitions; documentation recommends Kubernetes cert-manager to manage TLS secrets for HTTPS. Helm installation includes full 24-7 support. Listed Web ADC plans are billed monthly: Web ADC Small is $65 a month with one worker, Medium is $130 a month with two, Large is $260 a month with four, and Ultimate is $520 a month with configurable workers.

Who it suits

LiteSpeed Ingress Controller suits teams deploying Kubernetes ingress with LiteSpeed Web ADC across dedicated hardware, hosted environments or cloud infrastructure. It may also fit operators who want Gateway API support, Web ADC monitoring and ModSecurity-rule compatibility.

Good to know, and what to watch

  • Supports HTTP/2, HTTP/3 and Kubernetes Gateway API
  • Helm installation includes full 24-7 support
  • ZeroConf changes avoid restarting the load balancer
  • Web Application Firewall can use ModSecurity rules
  • Works with all web servers
  • Default installation exposes the LoadBalancer to the internet
  • Default installation load-balances all Ingress definitions
  • No Windows support is listed

Web ADC Small

$65/mo

Web ADC Medium

$130/mo

Web ADC Large

$260/mo

Web ADC Ultimate

$520/mo

Free plan

Getting started

  1. Open the LiteSpeed Web ADC product website
  2. Start the available free trial
  3. Prepare a self-hosted Linux, FreeBSD, macOS, or Solaris environment
  4. Install the Kubernetes ingress solution through Helm
  5. Use Kubernetes cert-manager to manage TLS secrets for HTTPS
  6. Manage ingress changes with ZeroConf and monitor through WebAdmin Console

Limits to check

There is no free plan. Listed Web ADC plans are billed monthly and provide one worker on Small, two on Medium, four on Large, or configurable workers on Ultimate.

The Club's review

Overview

LiteSpeed Ingress Controller is the Kubernetes ingress layer within LiteSpeed Web ADC, a software load balancer and application delivery controller. It is best suited to operators who want Kubernetes routing, HTTP/3, caching, firewall controls and Web ADC monitoring in one self-hosted deployment. The trade-off is that administrators must carefully control the broad exposure and routing behavior of the default installation.

Key features

Helm installation supports both Kubernetes Ingress definitions and the Gateway API. The controller uses native ingress rather than sidecars or Kubernetes modifications, which keeps the architecture comparatively direct. ZeroConf applies Kubernetes configuration changes without restarting the load balancer, a useful advantage for teams that need routine updates without avoidable interruption.

All HTTP versions are supported, including HTTP/2 and HTTP/3, along with WebSockets. Built-in LiteSpeed Cache targets web-application acceleration, while canary routing, rate limiting, authentication policies and TLS automation provide practical traffic-management controls. The Web Application Firewall accepts familiar ModSecurity rules and templates, giving security teams a known policy model rather than requiring a new rule language.

Realtime statistics and controller commands are available through the Web ADC WebAdmin Console. Kubernetes installation through Helm includes full 24-7 support. For HTTPS, cert-manager is recommended for managing Kubernetes TLS secrets. Operators should also account for the default behavior: installing the LiteSpeed LoadBalancer exposes it to the internet and load-balances all Ingress definitions. That may be convenient for a deliberately public cluster, but it requires explicit exposure and routing decisions in shared or restricted environments.

LiteSpeed Web ADC can run on private dedicated hardware, hosted environments or the cloud, and it works with any web server, although LiteSpeed Web Server is the preferred backend. The deployment is self-hosted and has a plugin or module system, but Windows is not supported.

Pricing

The product uses a freemium model with a free trial, but there is no ongoing free plan. The pricing note says paid service starts at $10/mo; the named Web ADC plans are billed monthly at higher published tiers:

PlanPriceIncluded workersBest fit
Web ADC Small$65 a month, billed monthly1 workerSmall production or development environments needing one worker
Web ADC Medium$130 a month, billed monthly2 workersTeams needing additional worker capacity
Web ADC Large$260 a month, billed monthly4 workersHigher-throughput deployments with a defined four-worker requirement
Web ADC Ultimate$520 a month, billed monthlyConfigurable workersOrganizations that need to set worker capacity to their architecture

There are no published seat quotas or usage caps in these plan descriptions. The cheaper tiers give up worker capacity rather than core ingress functions, so selection is primarily an operational sizing decision. Custom pricing applies where a named tier does not fit.

Platforms

LiteSpeed Ingress Controller is self-hosted and supports Linux, FreeBSD, macOS and Solaris. It is also presented for web and hosted use, but Windows is not supported. That makes it a natural match for Unix-based infrastructure teams and a poor fit for Windows-first operations.

Who it's for

Choose it when a Kubernetes platform team wants ingress and Web ADC capabilities together: modern HTTP protocols, application caching, ModSecurity-compatible WAF policies, traffic controls and a graphical monitoring console. It is particularly suitable when native ingress, Helm deployment and no-restart configuration changes matter.

Look elsewhere if you need an always-free production tier, Windows support, or a narrowly scoped default exposure model that does not require administrators to review every Ingress definition and internet-facing listener.

Pros and cons

Pros

  • Broad protocol coverage: HTTP/2, HTTP/3 and WebSockets cover contemporary application traffic.
  • Integrated acceleration and security: LiteSpeed Cache and a ModSecurity-compatible WAF reduce the need to assemble separate layers.
  • Direct Kubernetes operation: Helm, Gateway API support, native ingress and ZeroConf avoid sidecars and restart-based configuration workflows.
  • Operational visibility: WebAdmin provides realtime statistics and controller commands, with 24-7 support included for Helm installation.

Cons

  • No permanent free plan: a trial is available, but continued use is paid.
  • Default internet exposure: the installation exposes the load balancer and routes all Ingress definitions unless operators adjust that behavior.
  • Unix-only platform scope: Windows environments cannot host the controller.
  • Worker-based pricing: scaling to two, four or configurable workers raises the monthly cost substantially.

Alternatives

For a broader comparison, see Kubernetes Ingress Controllers.

  • ngrok is a better choice when you need Windows support, API-oriented deployment and a free tier with up to three online endpoints and 1GB of transfer.
  • Airlock Microgateway suits small environments or local development with a no-cost Community Edition, though throughput is enforced and its license is valid for six months.
  • Kusk Gateway is preferable when a 100% open-source, MIT-licensed gateway is the priority.
  • Traefik Proxy fits teams seeking a free open-source ingress controller, reverse proxy and load balancer with service auto-discovery.
  • agentgateway is an option for an open-source gateway delivered as a binary, Docker image or Kubernetes deployment.
  • BFE Ingress Controller offers an Apache 2.0-licensed open-source alternative without a free trial.
  • Contour is a free, self-hosted Kubernetes ingress controller with community support.
  • Higress provides a free self-hosted Community Edition with community support and documentation, while the user handles stability and performance.

Verdict

LiteSpeed Ingress Controller is a strong choice for Unix-based Kubernetes operators who want Gateway API support, HTTP/3, caching, WAF controls and Web ADC monitoring in one self-hosted stack. Choose it for that integrated capability and 24-7 Helm support; look elsewhere if a permanent free tier, Windows hosting or tighter default internet-exposure boundaries matter more than the bundled feature set.

The verdict

LiteSpeed Ingress Controller combines Kubernetes ingress with Web ADC caching, security and monitoring features. Operators should review the internet-exposure behavior of the default installation and configure TLS secrets as recommended.

Questions people ask

Is there a free plan?

No. A free trial is available, but the facts list no free plan.

How much do the Web ADC plans cost?

Web ADC Small costs $65 a month, Medium $130 a month, Large $260 a month, and Ultimate $520 a month. Each is billed monthly.

Which operating systems are supported?

Supported platforms are Linux, FreeBSD, macOS, and Solaris. Windows is not supported.

How is it installed with Kubernetes?

The solution installs through Helm and supports the Kubernetes Gateway API. Its native ingress design does not require sidecars or Kubernetes modifications.

Does it include security and TLS features?

It includes a Web Application Firewall that can use ModSecurity rules and templates, plus TLS automation. The documentation recommends Kubernetes cert-manager for HTTPS TLS secrets.

What support comes with installation?

The Kubernetes installation through Helm includes full 24-7 support.

What the maker publishes

Architecture
The controller uses native ingress with no sidecars or Kubernetes modifications required. source
Backend compatibility
LiteSpeed Web ADC works with all web servers, although LiteSpeed Web Server is preferred on the backend. source
Caching
The solution includes built-in LiteSpeed Cache for intelligent web-application acceleration. source
Configuration
Ingress management through ZeroConf allows Kubernetes configuration changes without restarting the load balancer. source
Deployment
It is a 100% software solution that can operate on private dedicated hardware, hosted environments, or the cloud. source
Founded
2002 source
Founded
2002 source
Headquarters
Newtown Square, Pennsylvania, USA source
Headquarters
United States source
Ingress solution
The LiteSpeed Ingress Controller is part of a complete Kubernetes ingress solution using LiteSpeed Web ADC. source
Kubernetes integration
It supports the Kubernetes Gateway API and installs through Helm. source
Monitoring
Realtime statistics and controller commands are available in the Web ADC WebAdmin Console GUI. source
Operational limit
By default, installing the LiteSpeed LoadBalancer exposes it to the internet and load-balances all Ingress definitions. source
Product role
LiteSpeed Web ADC is a high-performing HTTP load balancer and application delivery controller. source
Protocols
The controller supports all versions of HTTP, including HTTP/3. source
Security
It provides a Web Application Firewall implementation that can use familiar ModSecurity rules and templates. source
Support
The Kubernetes installation via Helm includes full 24-7 support. source
TLS integration
The documentation recommends Kubernetes cert-manager to manage TLS secrets for HTTPS connections. source

Checked against the maker's pages on 30 Sept 2026.