# How Qrvey uses Harness

**12 minutes**: “Qrvey reduced their build times from a few hours to 12 minutes on average.”

As published on [harness.io](https://www.harness.io/case-studies/qrvey-saves-hours-on-build-time-leading-to-happy-engineers), August 2026. Captured by usedby on 2026-10-07.

- Company: [Qrvey](https://www.usedby.ai/companies/qrvey.md)
- Tool: [Harness](https://www.usedby.ai/tools/harness.md)
- Teams: DevOps, Engineering, QA

## What the story says

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.

Summary written by usedby from the source page, in English. The figures are those of Harness and Qrvey, not ours.

> 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.

- **3 months**: “However, with Harness, the migration took only 3 months.”
- **30+ threads**: “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.”

> Today, I am the hero for the engineering team at Qrvey
>
> Luis Contreras, Lead DevOps Team

## What usedby checked

We compared the story with its live page on 2026-10-07.

- Checked: the figure 12 minutes is printed word for word on the page, near the name of Qrvey.
- Checked: the passage quoted above is copied word for word from the page, near the name of Qrvey.
- Checked: the publication date is read from the page’s own metadata, never guessed.
- Checked: Qrvey uses Harness. Confirmed line. Latest check across sources: 2026-10-07.
- Not checked: the result itself. We quote it; we did not measure it.

---
Source: https://www.usedby.ai/case-studies/qrvey-harness · How we check: https://www.usedby.ai/methodology