Leapwork vs Tricentis Tosca
Feature checklists rarely decide anything. What decides it is the pricing metric, who has to write the tests, and which limitation you can live with.
Entry price
Quote on request
Quote onlyQuote on request
Quote onlyWhat drives the bill
The metric that actually scales your invoice.
Enterprise quote-based licensing, typically annual and sized by concurrent runners plus authoring seats.
Enterprise licensing only, negotiated annually. Six-figure contracts are normal at scale.
Free tier
Free trial.
Open source
Self-hostable
No-code authoring
Languages
Platforms
Fits teams
Adoption
Emerging
Leapwork · since 2015
Widely used
Tricentis · since 2007
Strengths
- 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.
- Unmatched coverage of enterprise packaged software, especially SAP end-to-end processes.
- Model-based design means one change updates every affected test case.
- Risk-based prioritisation is a real answer to eight-hour regression packs.
Limitations
- 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.
- Expensive, and priced for organisations with a procurement department.
- Steep learning curve; most customers buy consulting alongside the licence.
- Heavy and slow compared to modern code-first tools for plain web applications.
Best for
Enterprises where business users must own automation and Citrix or mainframe is in scope.
Large enterprises running SAP or similar packaged systems where no open-source tool reaches.
All of these integrate with: Jira, Azure DevOps, Jenkins, SAP, Salesforce.
Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.