What do you dislike about Harness Platform?
The initial rollout requires a massive mental shift because you are adopting an entirely new operating model, not just a simple deployment tool. Learning the configuration hierarchy of Accounts, Organizations, Projects, Connectors, and Resource Groups takes considerable time. Furthermore, the Harness Delegates—the lightweight workers installed inside our own cluster to execute deployment tasks—are still infrastructure that our engineering team has to monitor, scale, and upgrade. This adds an element of operational overhead that you might not immediately expect from a managed SaaS product. Review collected by and hosted on G2.com.
Recommendations to others considering Harness Platform:
To ease the transition, consider starting with a pilot project to familiarize your team with the new system. Leverage the extensive documentation and community forums to address any initial challenges. Regular training sessions can also help in understanding the configuration hierarchy and operational nuances. Additionally, setting up automated alerts for the Harness Delegates can preemptively address potential issues, ensuring smoother operations. Review collected by and hosted on G2.com.
What problems is Harness Platform solving and how is that benefiting you?
We are solving the problem of deployment anxiety and inconsistent pipeline governance. By using the platform's Open Policy Agent (OPA) integration, our platform engineering group can automatically enforce security guardrails and compliance policies as code across all pipelines. This benefits me directly because I no longer have to wait on manual security approvals or worry about violating compliance standards; if my code passes the automated CI checks and OPA policies, it promotes straight to our staging environment and eventually production, drastically reducing our cycle times. Review collected by and hosted on G2.com.