# How WorkJam uses Harness

**40%**: “Docker image generation times dropped by around 40%”

As published on [harness.io](https://www.harness.io/case-studies/workjam), August 2026. Captured by usedby on 2026-10-07.

- Company: [WorkJam](https://www.usedby.ai/companies/workjam.md)
- Tool: [Harness](https://www.usedby.ai/tools/harness.md)

## What the story says

WorkJam migrated its CI from Bitbucket Pipelines to Harness CI and continued using Harness CD. It uses pipeline templates, Docker layer caching, Harness-managed build infrastructure, integrated vulnerability scanning and parallel multi-environment deployments with approval workflows.

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

> Reduced Build Times: Docker image generation times dropped by around 40%. For example, what previously took 24-30 minutes now takes 15-17 minutes.

- **90%**: “Production deployments that used to take three days now take two to three hours—a more than 90% improvement in efficiency.”
- **15-17 minutes**: “For example, what previously took 24-30 minutes now takes 15-17 minutes.”

> We achieved 40% faster builds and 90% faster deployments using Harness CI/CD.
>
> Venelin Koulaxazov, Software Development Manager at WorkJam

## What usedby checked

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

- Checked: the figure 40% is printed word for word on the page, near the name of WorkJam.
- Checked: the passage quoted above is copied word for word from the page, near the name of WorkJam.
- Checked: the publication date is read from the page’s own metadata, never guessed.
- Checked: WorkJam 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/workjam-harness · How we check: https://www.usedby.ai/methodology