# How Vivun uses Harness

**300%**: “300% improvement in DevOps engineer efficiency”

As published on [harness.io](https://www.harness.io/case-studies/vivun-scales-devops-with-harness), August 2026. Captured by usedby on 2026-10-09.

- Company: [Vivun](https://www.usedby.ai/companies/vivun.md)
- Tool: [Harness](https://www.usedby.ai/tools/harness.md)
- Industry: [Artificial Intelligence](https://www.usedby.ai/companies/industry/artificial-intelligence.md)
- Teams: SRE, QA, Developers

## What the story says

Vivun uses Harness CI for builds and Harness CD for deployments, with pipeline templates and automated testing, moving from monthly releases to on-demand releases and letting developers self-serve deployments and debugging.

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

> Previously, one DevOps engineer was needed for every 20 to 30 developers. Now, a single person can support 50 to 75 engineers.

- **50 to 75**: “Now, a single person can support 50 to 75 engineers.”
- **20 to 30**: “Previously, one DevOps engineer was needed for every 20 to 30 developers.”

> Today, we ship on demand, not on monthly calls.
>
> Jon Call, Engineering Manager for SRE

Source: [harness.io](https://www.harness.io/case-studies/vivun-scales-devops-with-harness), captured 2026-10-09.

## What usedby checked

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

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

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