The use case: how WePay deploys Harness
WePay uses Harness feature flagging (Split) to decouple feature rollouts from code deployments, release features gradually to select customer segments, and run old and new systems side by side while migrating from a PHP monolith to microservices. Control groups are also used to isolate issues after a release.
In the customer’s words
Tying feature accessibility to releasing code makes a lot of bad things happen, like releasing code at midnight to match a press release. Split lets us decouple these processes and release features with the click of a button.Harness users in Fintech & Payments
Companies in the same sector, with public evidence.
See all Harness customersGo straight to the source
Based on Harness’s published case study. We check the public evidence; the results are reported by the vendor.
harness.io- Source published
- Aug 5, 2026
- Last checked
- Oct 7, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 800K+ usersChecked
Printed word for word on the page, near the name of WePay.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of WePay.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- WePay uses HarnessChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
WePay transitioned from bi-weekly releases to deploying new features as often as needed. This enhanced their ability to:





