WebdriverIO vs Leapwork

Free and open source

Quote on request

Free and open source. You pay in engineering time and CI minutes.

Enterprise quote-based licensing, typically annual and sized by concurrent runners plus authoring seats.

Everything, self-hosted

Free trial.

Widely used

OpenJS Foundation · since 2015

Emerging

Leapwork · since 2015

• One API for web and native mobile, which is rare and genuinely useful if you ship both.
• Vendor-neutral: swap between local, grid and any device cloud by changing config.
• Mature plugin ecosystem for reporting, visual testing and accessibility.

• Genuinely usable by non-technical staff — the flowchart model is easier than any script-behind-a-recorder approach.
• Covers Citrix, virtual desktop and mainframe environments that most tools cannot touch.
• Doubles as an RPA platform, which can consolidate two budgets.

• Configuration-heavy compared to Playwright; the wdio.conf.js file becomes a project of its own.
• Inherits WebDriver's flakiness characteristics when used in WebDriver mode.
• Smaller community than Playwright or Cypress, so obscure problems take longer to solve.

• Flowcharts do not diff or merge, so version control is essentially unusable.
• Complex logic becomes an unreadable sprawl of blocks.
• Enterprise pricing with no small-team entry point.

JavaScript teams that need one framework covering both web and native mobile.

Enterprises where business users must own automation and Citrix or mainframe is in scope.