The use case: how Qrvey deploys Harness
Qrvey replaced its Jenkins setup with Harness CI and Harness Cloud builds to run its software builds and pipelines. The DevOps team uses it to speed up builds, reduce infrastructure upkeep, and manage security and access.
More reported results
Figures published in Harness’s case study. They are not independently measured by usedby.
However, with Harness, the migration took only 3 months.
The Qrvey team was able to leverage 30+ threads with Harness Cloud in a cost-effective way, which would otherwise cost significantly more using self-hosted Jenkins servers.
In the customer’s words
Today, I am the hero for the engineering team at QrveyHarness users in Data & Analytics
Companies in the same sector, with public evidence.
See all Harness customersGo straight to the source
Based on Harness’s published case study. We check the public evidence; the results are reported by the vendor.
harness.io- Source published
- Aug 28, 2026
- Last checked
- Oct 7, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 12 minutesChecked
Printed word for word on the page, near the name of Qrvey.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Qrvey.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Qrvey uses HarnessChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
With Harness CI, Qrvey reduced their build times from a few hours to 12 minutes on average. One of the reasons for the fast builds is Harness Cloud's build infrastructure.

