Kedify Autoscaler, powered by proven open source technologies and KEDA (Kubernetes Event-Driven Autoscaling), is an enterprise-grade service that allows teams to autoscale any workload using 65+ event sources including HTTP events.
Kedify Autoscaler, powered by KEDA (Kubernetes Event-Driven Autoscaling), is an enterprise-grade service for optimizing and scaling your cluster workloads. Supporting over 65 event sources, including HTTP events, Kedify seamlessly integrates with your Kubernetes clusters to improve performance and cost efficiency across any type of application, including but not limited to AI training, AI inference, E-commerce, Financial Services, Energy and much more.
Reduce Costs: Optimize resource usage and reduce cloud costs by scaling your infrastructure based on real-time demand. Reduce Complexity: Simplify the management of your infrastructure with easy-to-implement autoscaling solutions.
Scale to and from Zero: Efficiently manage periods of low or no demand by scaling down to zero instances and scaling up seamlessly when demand increases. Manage and Monitor Across Clusters: Easily manage and monitor your autoscaling configurations across multiple clusters and cloud environments.
Enhance Security: Ensure robust security by keeping KEDA up-to-date and CVE-free, and specifying role-based access controls for autoscaling configurations.
Highlights
Reduce Costs: Optimize resource usage and reduce cloud expenses by scaling your infrastructure based on real-time event-based demand - including HTTP events.
Reduce Complexity: Simplify infrastructure management with easy-to-implement autoscaling that is intuitive and secure.
Scale to and from Zero: Efficiently handle periods of low or no demand by scaling down to zero instances and seamlessly scaling up as demand increases.
Access real-time vendor security and compliance information through their Trust Center powered by Drata or Vanta. Review certifications and security standards before purchase.
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time. Alternatively, you can pay upfront for a contract, which typically covers your anticipated usage for the contract duration. Any usage beyond contract will incur additional usage-based costs.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
This Enterprise listing offers two usage-based pricing options, and you pick the one that fits how you want to be billed. The first charges by the number of nodes per hour. The second charges by the number of cores per hour. Both track your real infrastructure usage rather than user seats, so cost rises or falls as your cluster scales. Choose the node-based option if you measure capacity by node count, or the core-based option if you measure it by CPU cores. Kedify measures usage through cluster-level telemetry it collects, and billing follows that measured usage.
Top-of-mind questions for buyers
What counts as one node or one core for billing?
A node is one Kubernetes worker machine in your cluster. A core is one CPU core running across those nodes. Kedify's agent collects cluster-level telemetry, such as node and CPU counts, to meter your real infrastructure per hour. Both options count the infrastructure Kedify helps you scale, not user seats.
How does cost change when my cluster scales down or workloads idle?
Charges follow your measured infrastructure per hour, so cost drops as node or core counts fall. Kedify's scale-to-zero and right-sizing reduce idle compute, which lowers what you are billed. As your cluster grows, the hourly count rises and cost tracks it. Billing follows the telemetry the agent collects.
How do I choose between node-based and core-based billing?
Both meter usage per hour and bill on real infrastructure, not seats. The node option counts worker machines; the core option counts CPU cores across them. Pick node-based if your capacity planning uses node counts. Pick core-based if you track CPU cores, for example with larger nodes where core-level detail matters.
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Helm charts are Kubernetes YAML manifests combined into a single package that can be installed on Kubernetes clusters. The containerized application is deployed on a cluster by running a single Helm install command to install the seller-provided Helm chart.
Version release notes
Automated release from GitHub Actions for chart v0.6.4.
Enterprise support from Kedify for teams of all sizes (see https://kedify.io/pricing for more information about our plans). Contact us at support@kedify.io for more details.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Kedify Autoscaler, powered by proven open source technologies and KEDA (Kubernetes Event-Driven Autoscaling), is an enterprise-grade service that allows teams to autoscale any workload using 65+ event sources including HTTP events.
Be the first to review this product. We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.