Skip to content
testcritic

Zephyr Scale vs Xray

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

From $10 per month flat for up to 10 users ($100/year)

Paid

From $10 per month flat for up to 10 users ($100/year)

Paid

What drives the bill

The metric that actually scales your invoice.

Like Xray, priced per Jira user via the Marketplace, so it bills every Jira user rather than just testers. Beyond the 10-user flat tier expect about $5.68/user/month (e.g. $6,810/year for 100 users), dropping with volume. Zephyr Squad is a cheaper, lighter sibling product.

Priced through the Atlassian Marketplace by Jira user tier. Above the 10-user flat tier it works out around $6.07/user/month (e.g. $7,280/year for 100 users) and falls to roughly $3/user/month by 500 users. It bills for every Jira user, not just testers.

Free tier

30-day trial.

30-day trial via Atlassian Marketplace.

Open source

Self-hostable

No-code authoring

Languages

Codeless
Codeless

Platforms

WebAPI
WebAPI

Fits teams

Scale-up / mid-marketEnterprise
Scale-up / mid-marketEnterprise

Adoption

Widely used

SmartBear · since 2016

Category standard

Xblend / Xpand IT · since 2014

Strengths

  • Purpose-built case repository with parameterisation and shared steps that scale better than issue-based storage.
  • Cross-project reporting for programme-level quality visibility.
  • Version history on test cases, which matters for audit.
  • Complete requirement-to-test-to-defect traceability without leaving Jira.
  • No second tool for the team to learn or license separately.
  • Strong BDD support with Gherkin scenarios stored as Jira issues.

Limitations

  • Two similarly named products (Squad and Scale) cause genuine purchasing confusion.
  • Still bound to Jira's performance envelope.
  • Per-Jira-user pricing again inflates cost for large organisations.
  • Inherits Jira's performance characteristics; large test executions are slow.
  • Billing per Jira user means non-QA staff inflate the cost.
  • Test case authoring in Jira issue screens is clumsy compared to purpose-built editors.

Best for

Larger Jira organisations with test libraries big enough that reuse matters.

Organisations standardised on Jira that want a single system of record.

All of these integrate with: Jira, Jenkins, Cucumber, Azure DevOps, Selenium.

Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.