Skip to main content
usedby
Search tools, companies

How Swedbank uses Harness

50+

teams using feature flags

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

What happened

Swedbank uses Split feature flags (now part of Harness) to standardize release management across its frontend, backend, and mobile development teams. This lets teams deploy independently, roll out features gradually with canary releases, and toggle features off if problems arise.

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

By integrating Split across 50+ teams—ranging from mobile to backend—Swedbank was able to standardize feature flag management and introduce safer, more frequent releases.

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

Split’s platform has been key to us achieving faster releases with less risk. As we continue to grow and scale, it will remain a vital part of our software development process.

Markus Backman, Head Architect of Digital Banking at Swedbank, Swedbank. 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: 50+CheckedThe figure is on the page; its label is our wording.
  • The passage quoted aboveCheckedCopied word for word from the page, near the name of Swedbank.
  • The publication dateCheckedRead from the page’s own metadata, never guessed.
  • Swedbank 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