Harness and AWS CodePipeline compete in the CI/CD platforms category. AWS CodePipeline has an advantage due to its integration with AWS services and feature set, while Harness offers cost-effectiveness and excellent customer service.
Features: Harness offers AI-based deployment verification, canary and blue-green deployment strategies, and tools for optimizing resource usage. AWS CodePipeline integrates with AWS services, provides robust automation, and is flexible to incorporate third-party tools. Harness automates processes efficiently, whereas AWS CodePipeline offers a suite of cloud-native tools.
Ease of Deployment and Customer Service: Harness provides a streamlined setup and strong customer support, which aids in quick deployments and issue resolution. Its proactive support model helps avoid technical delays. AWS CodePipeline is well-suited for AWS-integrated environments, although its setup can be more complicated. Support is consistent but may necessitate familiarity with AWS services.
Pricing and ROI: Harness offers a cost-effective entry with an emphasis on ROI through reduced cloud costs and effective scaling. AWS CodePipeline pricing aligns with its deep AWS integrations, which can be economical for current AWS users but could escalate for others. Harness is known for transparent pricing, while AWS CodePipeline provides value through its service integration.
By adopting templates and various different pipelines across our own IDP platform, we have saved upwards of 30 to 40% of development time.
I believe the efficiency improvement is more than a twenty to thirty percent increase compared to Jenkins.
With Harness, the release process decreased from three or four hours to one or two hours, making deployments much quicker.
We have not faced any customer support issues, with tickets resolved in less than a four-day SLA.
We have rarely faced issues with Harness tech support.
We have been receiving incident reports whenever an incident occurs on Harness, and they are usually quick to respond.
AWS CodePipeline is good for scalability, and I rate it as nine out of ten.
It is able to work on our infrastructure side, which is EKS, and we are able to handle our organization growth effectively for an enterprise use case.
Our entire organization uses it with hundreds of applications, and it supports this scale effectively.
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.
I rate the stability of AWS CodePipeline as a ten out of ten because I have not experienced any issues with it.
Harness is completely stable, and we are using it in production without facing any stability issues at all.
We have rarely faced issues with Harness tech support.
Harness is decently stable.
The documentation for AWS CodePipeline is lacking and makes it difficult to find information due to its complexity.
There is not a lot of good support for pipeline as code, and I often find myself not using pipeline as code the way other platforms such as GitHub Actions or Jenkins integrate pipeline as code.
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.
Previously, when deploying a version that had been deployed successfully before, it sometimes failed upon trying again, which seems to be an intermittent issue about stability.
I estimated it costs around $5 monthly.
From what I understand with respect to Harness, licensing and setup costs were relatively low for an enterprise, and the pricing was more catered toward enterprises who would invest in the technology.
It allows me to test changes in an isolated environment before deploying them to the entire user base.
Harness uses AI to suggest errors in case of deployment failures.
The main feature is that it asks for approval before proceeding ahead.
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.
| Product | Mindshare (%) |
|---|---|
| AWS CodePipeline | 3.2% |
| Harness | 5.3% |
| Other | 91.5% |
| Company Size | Count |
|---|---|
| Small Business | 13 |
| Midsize Enterprise | 4 |
| Large Enterprise | 7 |
| Company Size | Count |
|---|---|
| Small Business | 1 |
| Large Enterprise | 9 |
AWS CodePipeline is a fully managed continuous delivery service that helps you automate your release pipelines for fast and reliable application and infrastructure updates. CodePipeline automates the build, test, and deploy phases of your release process every time there is a code change, based on the release model you define. This enables you to rapidly and reliably deliver features and updates. You can easily integrate AWS CodePipeline with third-party services such as GitHub or with your own custom plugin. With AWS CodePipeline, you only pay for what you use. There are no upfront fees or long-term commitments.
Harness offers a comprehensive toolset for automating deployment processes and enhancing software update efficiency. It's lauded for its CI/CD capabilities, feature flagging, and real-time deployment monitoring. Key features include an intuitive UI, secret management, and robust rollback functionalities, all contributing to improved productivity and reduced errors in DevOps environments.
We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
