Skip to main content
usedby

800K+ users

“800K+ users, seamless migration”

As published on harness.io, August 2026. Captured by usedby on Oct 7, 2026.

What happened

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.

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

WePay transitioned from bi-weekly releases to deploying new features as often as needed. This enhanced their ability to:

From the page. harness.io, captured Oct 7, 2026

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.

Chris Conrad, VP of Engineering, WePay. Source, captured Oct 7, 2026

What the story claims, and what we checked

We compared the story with its live page on Oct 7, 2026.

  • The figure: 800K+ usersCheckedPrinted word for word on the page, near the name of WePay.
  • The passage quoted aboveCheckedCopied word for word from the page, near the name of WePay.
  • The publication dateCheckedRead from the page’s own metadata, never guessed.
  • WePay uses HarnessCheckedConfirmed line. Latest check across sources: Oct 7, 2026.
  • The result itselfNot checkedWe quote it; we did not measure it.

Same company, same tool or same industry.

50%“a 50% decrease in overall production outages”Ancestry uses Harness. Another customer of Harness40%“Maintenance time cut by more than 40%, saving each QA engineer 2–3 hours per day previously spent on script fixes.”Gameopedia uses Harness. Another customer of Harness4x“4x improvement in delivery frequency and speed”Gentera uses Harness. Another customer of Harness