# How Whatfix uses TrueFoundry

**6X**: “6X Shorter Release Cycle”

As published on [truefoundry.com](https://www.truefoundry.com/case-studies/whatfix-truefoundry-kubernetes-migration-on-prem-deployment). Captured by usedby on 2026-10-09.

- Company: [Whatfix](https://www.usedby.ai/companies/whatfix.md)
- Tool: [TrueFoundry](https://www.usedby.ai/tools/truefoundry.md)
- Teams: SRE, DevOps, Machine learning

## What the story says

Whatfix used TrueFoundry to migrate from a monolithic architecture to microservices on Kubernetes. TrueFoundry orchestrates a core part of its CD pipeline, deploying each pull request for testing, and gives the SRE team a single view for managing multi-cluster and on-prem deployments.

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

> TrueFoundry partnered with the Whatfix team in their migration from a monolithic architecture to a microservices-based architecture deployed on Kubernetes.

- **40%**: “40% Time Saved in Testing”
- **3 Months to 2 Weeks**: “On-Prem deployment and testing time reduced from 3 Months to 2 Weeks”
- **~30-40%**: “~30-40% Time saved in testing”
- **2-4**: “Small DevOps team (2-4) able to cater to 150+ Development team”

## What usedby checked

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

- Checked: the figure 6X is printed word for word on the page, near the name of Whatfix.
- Checked: the passage quoted above is copied word for word from the page, near the name of Whatfix.
- Checked: Whatfix uses TrueFoundry. 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/whatfix-truefoundry · How we check: https://www.usedby.ai/methodology
