
Overview
Harness is an AI-powered software delivery platform that enables DevSecOps and engineering teams to accelerate and secure software delivery across cloud and hybrid environments. Harness automates every stage of the SDLC, from code integration and testing to deployment and verification, using AI for advanced deployment strategies, automated rollbacks, and real-time analytics.
With Harness, teams benefit from:
- Faster Builds: Run only tests affected by code changes, thus accelerating build time by up to 4x.
- Rapid, Reliable Deployments: Build and execute complex deployment pipelines in minutes, supporting blue/green, canary, and rolling updates across AWS services like EKS, ECS, Lambda, and Auto Scaling Groups.
- Automated Security & Compliance: Built-in secret management, audit trails, and continuous security scanning ensure secure, compliant deployments at every step.
- Smart Automation & Continuous Verification: Leverage machine learning to detect deployment anomalies and automatically roll back to stable versions, minimizing downtime and risk.
- Cloud Cost Optimization: Harness Cloud Cost Management helps FinOps and engineering teams maximize savings with automated resource orchestration, commitment management, and cost visibility.
- Enterprise-Grade Support: Trusted by organizations worldwide, Harness provides robust support and integrations for seamless adoption on AWS.
- Suite of Products Across SDLC: Harness offers modular products across the SDLC for use cases such as feature management and experimentation, IDP, infrastructure as code, end-to-end test creation using AI, code repository, and others.
Harness empowers teams to deliver software faster, safer, and more efficiently, reducing manual effort, minimizing errors, and optimizing cloud spend. Contact the Harness team directly for custom pricing or to support larger deployments.
Highlights
- Accelerated Delivery & Reliability: Speed up builds by up to 4x and execute complex deployments in minutes with advanced strategies like blue/green, canary, and rolling updates.
- Secure & Intelligent Automation: Ensure compliance with built-in security, audit trails, and continuous scanning while leveraging AI for anomaly detection and automated rollbacks.
- Optimized Cloud Value: Maximize AWS consumption and savings with automated cost management, visibility, and orchestration, supported by enterprise-grade integrations across the SDLC.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Trust Center
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Dimension | Description | Cost/12 months |
|---|---|---|
Service Instance | A Service Instance is an application runtime, such as JVM, K8s Pod etc | $300.00 |
Vendor refund policy
Contact Harness Support - support@harness.io
Custom pricing options
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Support
Vendor support
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.
Similar products

Customer reviews
Automated deployments have reduced incidents and improve feature control with flexible rollbacks
What is our primary use case?
I use Harness for multiple things, such as the CI/CD process, feature flag management, security testing, and infrastructure provisioning. The primary use case is the CI/CD and deployment along with feature flag management.
In my day-to-day work, when multiple developers are collaborating on a single project and I commit my changes and raise a pull request for the main branch, the CI/CD process starts automatically after my code gets merged. It builds the code automatically and deploys it on a cloud provider of my choice, such as GCP , Azure , or AWS , after proper configuration. This allows for automated deployment across various environments, including dev, prod, QA, and staging. Additionally, deployment approvals can be sought for prod deployment. If I need to roll back, Harness offers a rollback strategy and shows all the steps in the pipeline, enabling me to directly restart any failed step. Harness also generates alerts for any deployment failures. Regarding deployment strategies, it enables options such as blue-green deployment, canary deployment, rolling deployment, and alpha-beta testing deployments. For feature flags, I can hide a new feature in our application, which can be activated by simply changing the flag value in Harness without needing to redeploy, which is particularly useful for timed events such as sales.
What is most valuable?
The best features that Harness offers include the CI/CD, continuous integration, continuous deployment, deployment strategies, cost management dashboard, and feature flag management, which I consider the top three because they significantly reduce human effort and deployment time while improving release confidence. If we have a release on a Friday, we can easily roll back in case of failure.
CI/CD and feature flag management are the two features that have had the biggest impact on our team, with CI/CD being the primary one.
Harness positively impacts our organization by reducing deployment time, improving release confidence, and lowering operational overhead during deployment. It fosters better collaboration between development and operational teams, enabling faster incident recovery. For instance, in case of a production incident, we can revert the current build and deploy the last stable version easily.
What needs improvement?
The initial setup can be complex and time-consuming, and the advanced features may require some learning time due to a steep learning curve. Additionally, the pricing may be high for smaller organizations, which could present a challenge.
For how long have I used the solution?
I have been using Harness for around four point five years.
What do I think about the stability of the solution?
Harness is quite stable.
How are customer service and support?
The customer support is excellent. There was an instance when I faced issues with third-party plugins, and after raising a support ticket, they responded in a few hours with a documentation link that resolved my issue. I would rate customer support a ten out of ten.
Which solution did I use previously and why did I switch?
I have previously used multiple solutions such as GitLab , Jenkins , and GitHub Actions . One feature that I did not find in those other solutions is feature management. While everyone provides CI/CD, Harness excels in feature management, which is a very good feature.
How was the initial setup?
The setup time for Harness takes quite a long time, but I do not think the pricing is excessive.
What was our ROI?
I have seen a return on investment primarily through time saved and reduced incident recovery time.
Which other solutions did I evaluate?
I did not evaluate other options before choosing Harness, as it was already in use at the company when I joined.
What other advice do I have?
My advice for others considering Harness is that if you are a large organization, you should definitely go for it. However, if you are a smaller organization, it may be better to use free solutions such as Jenkins or GitLab that provide similar functionalities. I would rate this review an eight out of ten.
Automated pipelines have streamlined Kubernetes deployments and accelerated troubleshooting
What is our primary use case?
Harness is a delivery platform where we can create pipelines. I have been using Harness for deploying my application into my Kubernetes environment.
I had a couple of backend applications which used to talk with some other remote vendor-based services where they used to fetch data. For those applications' deployment I used Harness where I set up code push stages, build app stages, test stages, and then the deployment stage in Harness. Through Harness we deployed the code to my environment.
I set up those pipelines in the form of multiple environments. By multiple environments, I mean that normally we do have multiple environments such as dev, QA, pre-prod, and prod. What we used to do was have pipelines based on environments. For example, if the build happens and the Docker images are being created and then there comes a stage where it gets deployed. If everything works fine in the dev stage, it automatically gets deployed to the QA, then pre-prod and prod. All of these things were done by Harness, and Harness was so advanced that it used to understand the integration of those pipelines and it used to work in a coalition manner.
What is most valuable?
Harness is a managed platform that has a modern UI compared to the other CI/CD tools out there. It has built-in CI/CD features, and nowadays, it has AI features as well. AI-based troubleshooting, AI-based pipeline generation, and AI-based features are available. It also has test intelligence and automatic rollbacks. With AI, you can create scripts, and it requires less scripting, and it's commercial.
AI pipeline generation and AI test creation are two certain things which have really helped me. The reason being is that if my application requires or I'm onboarding a new application, I can use that AI pipeline generation feature to generate the pipeline and AI test creation also to create the test cases for my application. If something goes wrong, I can use AI troubleshooting to build or test my fails and analyze the logs, suggesting the fixes.
Using Harness, the deployment time has been reduced, plus the time taken during troubleshooting any issue is reduced, and the time taken to write the test cases has reduced using the AI features. Deployment time has really been reduced. If we want to onboard some new applications, we can just quickly onboard it and quickly create the pipeline to deploy it. Even if something goes wrong while deploying it to production or any environment, the AI troubleshooting feature which Harness has really helps to analyze the logs and suggest the fixes.
What needs improvement?
Nowadays, most of the applications are containerized applications. Harness has really rich features, and ideally, it's based on the CI/CD tool. However, native integrations with tools or features that normally people use would be beneficial. For instance, Argo CD or Helm should have some direct implementation on Harness. Even though they have those AI features, if some sample pipelines or some advanced level integrations are already pre-made, that would be really great.
The licensing cost can be significant for larger teams, which should be taken into account. If we are already using some other CI/CD tools, Harness should provide a way so that we can migrate our CI/CD pipelines to Harness. Currently, if we are moving from another tool to Harness, we just have to write the pipeline from scratch. Even though we can use AI features, we still have to give a lot of effort. Harness should have some way that if we provide them our previous application pipelines, they can generate a pipeline based on top of Harness. Sometimes some advanced workflows also may require custom scripting. Those features should also be there, so that if there are some advanced workflows, Harness is intelligent enough to just create a sample pipeline according to the use case and then we can modify it according to our need.
The same concerns about the guardrails apply. If Harness can also tell us what guardrails they have for their AI features, that would be really great.
For how long have I used the solution?
I have used Harness for a couple of years.
What do I think about the stability of the solution?
Harness is stable.
What do I think about the scalability of the solution?
As Harness is a managed SaaS solution, the vendor has to maintain the scalability. If we have deployed it on-prem, we can work as it is and just scale on our need.
How are customer service and support?
Customer support is really great and does really help us.
Which solution did I use previously and why did I switch?
I did evaluate options such as native CI/CD cloud solutions. I used Jenkins , GitHub Actions , GitLab , and Tecton.
What was our ROI?
The major investment which I have seen is time saved. As I already told previously, Harness has AI capabilities and we don't need to have multiple stacks. Harness comes with all the stacks inbuilt. So we don't have to look or invest our time in looking for the other tools to suffice our use case. We can use Harness as a single source of truth. The AI features that they have and with which we can rewrite the pipeline and troubleshoot issues significantly saved time.
What's my experience with pricing, setup cost, and licensing?
Everything is fine with licensing and setup. However, the licensing cost is a little bit too high. If cost is something that can be looked upon, it would be really great.
What other advice do I have?
I was using Jenkins and GitHub Actions . Because I am a client intrinsic company, it depends on what the client needs. According to client need, I use GitHub Actions, Jenkins, or GitLab . However, if sometimes clients do ask me my opinion, I do tell them that Harness can be explored.
Approximately seventy-five percent time was reduced in case of deployment and around sixty to sixty-five percent time was reduced while troubleshooting it.
In my case, the number of times I have used Harness, it has given me the appropriate output and appropriate suggestions. So I think the accuracy and reliability of Harness is really high.
I would really advise them to use it if they don't want multiple tech stacks and cost is not a concern. So I would really suggest others to use Harness.
Harness is a really good tool with the rich features it has, and it's really advanced nowadays. I gave this review a rating of eight out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Unified pipelines have streamlined deployments and automated security testing across environments
What is our primary use case?
My main use case for Harness is to create pipelines, deploy applications, and manage security pipelines.
I use Harness to deploy applications to EC2 instances and Kubernetes instances, and I created pipelines for building an application, deploying an application, running security scans on repositories, syncing scans, and many more. I even used running automation tests on Harness pipelines.
What is most valuable?
The best features Harness offers, in my opinion, are the ability to create pipelines with YAML files and the Terraform codes. It is easy to manage, easy to scale up, and easy to create multiple stages. It interacts with a lot of third-party applications. We use Terraform everywhere, so using Terraform to create pipelines makes our job easier.
Harness has impacted my organization positively; we use Harness in most of all deployments, so it is uniform. When I say it is uniform, it has helped us save time, reduce errors, and make collaboration easier, with the AI integrations helping us to create tests faster, trigger tests faster, and finish tests faster while keeping logs.
What needs improvement?
There are some UI components that can be improved. The needed UI improvements include more graphs, more history, the ability to create pipelines through the UI, and more interactions, with UI components being more standardized.
For how long have I used the solution?
I have been using Harness for two years.
What do I think about the stability of the solution?
Harness is stable.
What do I think about the scalability of the solution?
Harness can be scaled very fast.
Which solution did I use previously and why did I switch?
I used Concourse and Bamboo before switching to Harness.
What other advice do I have?
My advice for others looking into using Harness is to use AI capabilities, create pipelines, and then use it to deploy. Harness is a good tool. I would rate this review a nine out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Automation has reduced deployment effort and now delivers cloud releases faster with fewer errors
What is our primary use case?
Harness automates the CI/CD pipelines and manages applications deployments across different environments like staging, development, and production. I use it to monitor the deployments and ensure stability, so when developers push new code to the repository, Harness automatically triggers the CI pipeline, builds the application, runs tests, and prepares the deployment packages. After validation, the CD pipeline deploys the applications to the cloud environment, automating the workflow and helping us deliver faster.
What is most valuable?
Some of the best features of Harness include powerful CI/CD pipeline automation, intelligent deployment strategies, and building monitoring. The platform also supports cloud-native environments and Kubernetes deployments, making pipeline management easier, and its automation capabilities significantly improve speed and reliability.
Harness improved deployment reliability by automating the continuous delivery pipelines and adding building verification checks, so deployments are automated and verified using performance metrics, and the platform also saved time by reducing manual operational tasks.
It has saved time; previously I needed many employees to handle deployments, but now the number of employees has reduced and the speed has increased, which is one of the good benefits.
What needs improvement?
One improvement I see for Harness is simplifying the configuration process for smaller teams or startups, as the platform offers powerful features that new users may require some time to understand. Improved documentation and onboarding tutorials would help accelerate adoption.
The analytics dashboard could be enhanced to provide deeper insights into pipeline performance.
The user interface could be improved.
For how long have I used the solution?
I have been using Harness for several months while working in CICD and deployment automation.
What do I think about the stability of the solution?
Harness is stable.
What do I think about the scalability of the solution?
It is scalable.
How are customer service and support?
Customer support is good.
What other advice do I have?
I appreciate that Harness provides good visibility into pipeline execution and deployment status, and I appreciate how it simplifies the complex CI/CD workflows. Its automation features help reduce human errors during releases.
The pricing is good, but it can be reduced if there is a bigger team, and it should have a good plan.
Using Harness, I now need fewer employees.
Harness is good to use; I have to look after the deployments as well. I give this review a rating of 9.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Modern pipelines have improved compliance, accelerated builds, and simplified security testing
What is our primary use case?
Harness helps us build a pipeline with containerized steps that isolates virtual machines, reduces DevOps-based drifts, and improves our process by integrating several security testing-related steps in the pipeline. Beyond that, it helps us remain regulatory and compliance adherent.
A specific example of how I use Harness for security testing or compliance in my pipeline involves the audits and certifications that our institution undergoes, such as SOC 2 and SOC 2 Type 2 certifications, as well as ISO 20001 certification needed for regulatory compliance in certain specific geographies where we operate. Harness comes in because it is compliant with these international regulations, and other larger institutions also use Harness for the same reason.
What is most valuable?
Harness offers several best features that I have worked with, including an intelligent caching system for dependencies and artifact building that allows for extremely short build times without extra bash scripting, a pipeline as code visual editor, and Harness Cloud along with small-lived virtual machines that we can run on Kubernetes .
The intelligent caching system has impacted my build times significantly by auto-caching dependencies and allowing smaller ephemeral runs to shorten build times without any need for detailed scripting, which has made a noticeable difference.
I would add that Harness has dedicated support for unit tests based on my experience, and this support is not restricted to only Java-based tests. I have seen support for Java tests, Scala , Ruby, and Kotlin, which helps us prevent flaky test management patterns.
Harness has positively impacted my organization as several teams have already migrated to it, and some are in the process of moving. It has reduced the dependency on one specific platform and has made it faster, with shortened build times and much faster deployments.
What needs improvement?
Harness can be improved by providing more clarity on the credits it issues for Harness Cloud, as it has a tiered pricing structure involving license and credit costs, which can get confusing. Additionally, there is a learning curve, as Harness is not currently an industry top-recommended solution, especially for teams coming from a Jenkins background.
For smaller teams, having features similar to GitHub Actions could be implemented by Harness, as this could really help the smaller teams who are moving to it.
For how long have I used the solution?
I have been using Harness for three years now.
What do I think about the stability of the solution?
Harness is completely stable, and we are using it in production without facing any stability issues at all.
What do I think about the scalability of the solution?
Currently, out of twenty teams that are supposed to adopt it, five or six have adopted Harness, and we have not seen any kind of scalability issues, such as slowness in performance or build time reduction, so I am satisfied with the scalability.
How are customer service and support?
We have a direct line of enterprise support from Harness, and we have not faced any customer support issues, with tickets resolved in less than a four-day SLA.
Which solution did I use previously and why did I switch?
We were using Jenkins before switching to Harness, as there was a lot of dependency, slowness, and build stability issues in Jenkins.
What was our ROI?
I cannot provide data on how much time has been reduced, but I believe the efficiency improvement is more than a twenty to thirty percent increase compared to Jenkins.
Which other solutions did I evaluate?
Before choosing Harness, we evaluated GitHub , GitHub Actions , GitHub CI, and CircleCI , in addition to Jenkins which we originally used.
What other advice do I have?
My advice for others looking into using Harness is to perform a trade-off analysis between GitHub Actions, GitHub CI, CircleCI , and conduct a cost analysis. Harness is still new to the market and is cheaper, but Jenkins is completely open source and requires hosting, while Harness provides enterprise support for us to work with. Pros and cons need to be evaluated before adopting Harness. I am very happy with my current usage of Harness and would rate this review an eight out of ten.