Skip to content
Qase logo

Qase

Test management system that stores manual and automated test cases, runs test plans and collects results from CI and test frameworks.

Free plan · From $42/user/moActively maintained

At a glanceswept Oct 14, 2026

≈ 6.5kvisits/mo

Emerging · estimate, read Oct 14, 2026

For
QA and engineering teams organizing manual and automated testing for software releases.
Activity
Actively maintainedrelease 5 days ago · site updated 5 days ago
Company
Qase Inc · since 2018terms of service · per Wikidata
Used for
  • organize and track manual and automated test cases
  • report CI and framework results into test runs
  • trace requirements to test results before a release
read off qase.io on Oct 15, 2026
Worth knowingcomputed from what we read · each with its source
  • Used more than 90% of the 1,854 tools on its shelfINITE Atlas →
  • On the web since 2018, older than 89% of its shelfINITE Atlas
  • Has an MCP server (1 in the registry)public registry →
  • Publishes llms.txt, a file written for AI assistantsqase.io ↗
Pricingpricing page, read Oct 15, 2026

Free plan · From $42/user/mo

Trial & discounts 14-day free trial · student discount

The companyeach fact with its source · read Oct 16, 2026
Your datawhat they publish, each line with its page · read Oct 15, 2026

These are Qase's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.

How a program reaches itfound, not claimed · read Oct 15, 2026
  • MCP serverio.qase/mcp-serververified in the MCP registry
  • Stateanswers, requires sign-inchecked 2026-10-15
  • Address to connectmcp.qase.io/mcp
  • API docsdevelopers.qase.iothe vendor's page ↗
  • MCP docsqase.io/mcp-model-context-protocolthe vendor's page ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare Qase with

Pick up to two.

All 10 alternatives to Qase →

All Developer tools tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Qase for?

Sign in to leave a note
Questions this page answers
  • What is Qase?

    Test management system that stores manual and automated test cases, runs test plans and collects results from CI and test frameworks. It is listed in the Atlas under Developer tools and made by Qase Inc.

  • Who is Qase for?

    QA and engineering teams organizing manual and automated testing for software releases.

  • How much does Qase cost?

    Qase has a free plan; paid plans start at $42/user/mo, per its pricing page on 2026-10-15.

  • Is Qase free?

    Yes, Qase has a free plan, per its pricing page on 2026-10-15.

  • Do people use Qase?

    Emerging: ≈ 6.5k visits/mo · estimate, 2026-10.

  • Is Qase still maintained?

    Actively maintained: release 5 days ago · site updated 5 days ago.

  • Who owns Qase?

    Qase is run by Qase Inc, per its terms of service (2026-10-15).

  • Is Qase safe?

    We do not audit vendors. What Qase publishes, read 2026-10-15: GDPR stated on its privacy policy.

  • Does Qase have a free trial?

    Yes, a 14-day free trial, per its pricing page (2026-10-15).

  • Does Qase have a student discount?

    Yes, its pricing page names a discount for students (2026-10-15).

  • Does Qase give refunds?

    In its own words (terms of service, 2026-10-15): “Fees are non-refundable, including during any committed term.”

  • What are alternatives to Qase?

    In Developer tools, by use: Postman, Testsigma Agentic Test Automation Tool, Jam, Reflect AI, Incident IO, Bugster.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk