# How PlayQ uses Harness

**4x**: “4x faster Kubernetes cluster upgrades”

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

- Company: [PlayQ](https://www.usedby.ai/companies/playq.md)
- Tool: [Harness](https://www.usedby.ai/tools/harness.md)
- Teams: Platform Engineering

## What the story says

PlayQ uses Harness Infrastructure as Code Management to provision and manage its cloud and Kubernetes infrastructure through self-service, GitOps-based pipelines. It supports both Terraform and OpenTofu, with a gradual migration to OpenTofu.

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

> With Harness, all Terraform plans and applies run concurrently. Pushing upgrades to Kubernetes clusters is 4x faster than it used to take with Terraform Cloud

- **100%**: “100% self-service infrastructure workflows”
- **80%**: “80% migration to OpenTofu and 20% workloads on Terraform”

> With Harness, all Terraform plans and applies run concurrently. Pushing upgrades to Kubernetes clusters is 4x faster than it used to take with Terraform Cloud
>
> John Maynard, Director of Platform Engineering

## What usedby checked

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

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