Directory Cloud InfrastructureContainers & KubernetesKEDA

KEDA

Open Source

About KEDA

KEDA is a Kubernetes-based Event Driven Autoscaler. It allows scaling of any container in Kubernetes based on the number of events needing to be processed. KEDA is a single-purpose and lightweight component that can be added into any Kubernetes cluster. It works alongside standard Kubernetes components like the Horizontal Pod Autoscaler and can extend functionality without overwriting or duplication. Users can explicitly map which apps use event-driven scale, while other apps continue to function. The product includes a catalog of built-in scalers for various cloud platforms, databases, messaging systems, telemetry systems, and CI/CD.

Products

Predictkube: Provides AI-based predictive scaling based on Prometheus metrics and PredictKube SaaS.

Used for

Scaling applications based on ActiveMQ Queue.
Scaling applications based on an Apache Kafka topic or other services that support Kafka protocol.
Scaling applications based on AWS SQS Queue.
Scaling GitHub Runners based on the number of queued jobs in GitHub Actions.
Running and scaling Azure Functions on Kubernetes in production workloads.

From KEDA's own website, read 2026-10-23. How we build listings.

How to evaluate Containers & Kubernetes

This is how the CIOPages Research Team evaluates this category. It is not an assessment of KEDA. It comes from our Kubernetes Platforms buyer guide.

25%

Control Plane & Day-2 Lifecycle

Managed vs. self-managed control plane and its SLA; how Kubernetes version upgrades roll (in-place, surge, blue-green) and how disruptive they are to running pods; long-term-support version options; CVE patch cadence and how quickly fixes reach the fleet; automated node remediation and certificate rotation

20%

Fleet & Multi-Cluster Management

Single console and API to govern many clusters across clouds, on-prem, and edge; declarative cluster lifecycle and config (Cluster API or equivalent); fleet-wide policy and drift detection; zero-touch provisioning for edge; whether it manages clusters it did not create (imported/attached) or only its own

20%

Security & Compliance

Default-deny posture and admission control (Pod Security, OPA/Kyverno); image scanning and signing in the supply chain; RBAC plus OIDC/enterprise-identity integration; network policy and microsegmentation; CIS-benchmark conformance, audit logging, and FedRAMP/FIPS coverage where regulated

15%

Networking, Storage & Service Mesh

CNI options and how locked-in the default is; ingress and gateway controllers with TLS, rate-limiting, and WAF; CSI drivers for block/file/object and stateful-workload maturity; service mesh integration (Istio, Linkerd, Cilium); cross-cluster connectivity and load balancing

10%

Developer Experience & Self-Service

Namespace and cluster self-service vs. ticket-based provisioning; GitOps support (Argo CD, Flux) as a first-class workflow; developer portal and golden-path integration (Backstage or built-in console); IDE plugins and local-dev parity; how opinionated the platform is about how teams ship

10%

Cost, Portability & Commercial Model

Licensing unit (per-core, per-node, per-cluster, consumption) and how it scales with you; control-plane and extended-support fees; realistic exit cost and how provider-shaped the abstractions are; GPU/AI scheduling support; ecosystem breadth (operators, Helm, marketplace) and how much you must self-integrate

Other Containers & Kubernetes Vendors

View all

AKS Engine for Azure Stack

Accordion

Alauda Container Platform (ACP)

Alibaba Cloud Container Service for Kubernetes

Amazon Elastic Container Service (ECS)

Amazon Elastic Container Service for Kubernetes (EKS)

CIOPages put this listing together from public sources. It’s information, not an endorsement. How we build listings. Work here? Claim this listing or .