Skip to content
Test Management · Automation · Performance

One AI agent for all of QA.

Requirements to test cases, automation to runs, coverage to reports: Ordel plans, executes, and remembers your entire QA. Drive it from your coding agent, or let it run on its own.

claude mcp add --transport http ordel https://ordel.io/api/mcp
Interaction model · pick your register per task
Manual
full control
Assisted
AI + human
Agent
autonomous
Integrates with the tools your team already lives in
PlaywrightJIRALinearGITHUBAzure DevOpsJENKINSClaudeOPENAIGeminiOLLAMAPlaywrightJIRALinearGITHUBAzure DevOpsJENKINSClaudeOPENAIGeminiOLLAMA
State of QA · observed across 200+ teams

Your QA stack costs more every quarter it survives.

01 · Tool fragmentation

Five vendors. Zero integration.

Jira for management. Selenium for automation. JMeter for load. Postman for APIs. Custom scripts for data. Five bills, five UIs, no single source of truth. Nothing trustworthy to show leadership.

Cost: 5 vendors · integration debt
02 · Maintenance tax

A 3-pixel button move breaks hundreds of tests.

40–60% of your automation budget is spent fixing tests that were passing yesterday. Before you write a single new test, you’re paying rent on the old ones.

Cost: 40–60% of budget · before net-new
03 · Copilot ceiling

AI that only writes the opening line.

Copilot drafts a test. Who runs it? Heals it next Tuesday? Classifies the failure? Files the defect? Writes the report? Code-generation copilots get you off the blank page, then stop.

Cost: 0% of lifecycle covered
04 · Headcount math

You need 10× the tests. You won’t get 10× the people.

Ship velocity is up and to the right. QA headcount is flat or down. Manual testing has a ceiling, and you’re standing on it. Performance testing alone eats 2–3 days per scenario.

Cost: 10× gap · 2–3 days per perf scenario
The agent · how it actually works

It does the work. You approve it.

Ordel is not a test tool with an AI button. It is an agent that maps your app, writes and runs the tests, heals them when the app changes, and files what it finds. Every action is recorded, every change is yours to approve, and every one is revertible.

One loop · six steps · one approval each

What the agent does, and what you do.

the agentyou
Explores the app and maps every page and elementaccept the map
Drafts test cases from a one-line requirementapprove the cases
Writes the script, grounded in the map it builtrun it
Detects the break when the app changes, proposes the fixapprove the heal
Files the defect with repro, logs and labelstriage
Writes the reportread it
How far you let it go · set per project
Manual
you drive
you own everything
Recorder
you click, it captures
you own the clicks
Agent
it acts, you approve
you own the approvals
Autonomous
your boundaries, its hands
you own the boundaries
MCP · bring the agent you already use

Claude Code and Cursor can test with it.

Ordel is an MCP server. Your coding agent can start cycles, read failures, propose fixes, file and close defects, and pull reports, through the same approval loop. One line to connect:

claude mcp add --transport http ordel https://ordel.io/api/mcp
claude→ordel.list_runs(status="failed")
ordel→3 failed · 2 with heal proposals
cursor→ordel.start_cycle("release-42")
ordel→214 tests queued · running
tools exposed50+
Connect your agent →
The loop · AI-driven

Generate. Execute. Heal.
Analyze. File.

Five beats of an AI-native test lifecycle. Every one used to be somebody's job title. Your team does the one part that matters: set the standard.

Beat 01

Generates.

A requirement goes in. Test cases come out.

Beat 02

Executes.

They run at scale, cloud or local, with a live feed.

Beat 03 · signature

Heals itself.

When the UI shifts, the tests fix themselves and keep running.

Beat 04

Analyzes.

You learn what broke and why, not just that it did.

Beat 05

Files defects.

A pre-filled defect lands in your tracker, ready to triage.

Test automation · the engine

Intent or code. Cloud or local. One engine.

Build tests by intent, by recording, by AI exploration, or in plain code. Run them in the cloud or on your own infrastructure. Every element and reusable module lives in one shared repository.

App Graph · centerpiece

A living map of your entire application.

Crawled by AI, shared across every test. The graph is the single source of truth: every element, page, and flow lives here.

Crawled pages
/login14 elements
/dashboard86 elements
/cart41 elements
/checkout53 elements
Nodes tracked2,847
Self-healing · signature

Three tries before we ask the AI.

CSS → a11y role → fuzzy match. If all fail, an LLM reads the live DOM against element history and proposes a heal, with a confidence score.

1
CSS selector
deterministic
0msFAIL
2
a11y role
semantic
12msFAIL
3
fuzzy match
heuristic
28msFAIL
★
LLM heal
reads DOM + graph
411ms0.94
Auto-heal rate · last 30 days99.2%
Modules · build once

Reusable like Lego.

Login, search, checkout: package any flow as a module. Drop it into any test. Maintained in one place, used everywhere.

Module library
Login
Search
AddToCart
Checkout
Logout
checkout-flow.spec
1.____
2.____
3.____
4.____
Performance · the same flows, under load

Your functional tests, now load tests.

Recorded flows convert to k6. AI correlates the tokens, you edit any request in the browser, and every run is judged by statistics, not vibes.

Performance · signature

Statistics decide pass/fail.

Each transaction is gated against a rolling baseline of your own previous runs. A static threshold can't tell drift from noise; the statistical gate can.

ConvertPlaywright flows + HAR captures → k6, open standard
Inspectedit every request · method, headers, body, params
CorrelateAI finds CSRF, session + dynamic values · you accept
Shaperamp, spike, stairs · open + closed models
Runcloud or your own agent · live p50 / p95 / p99
checkout · p95 412ms✓ within baseline
search · p95 +38% drift✗ breach
login · p95 188ms✓ within baseline
gate · Mann-Whitney U vs rolling baseline · p95 + error rate per transaction
peak vusers · last run10,423
Reports · run vs run vs run

Put your runs side by side.

Most load tools show you one run at a time. Ordel's comparison grid puts multiple runs side by side: every transaction a row, every run a column, every cell coloured by drift against the baseline you pick. Flip the metric (avg, p95, p99, throughput, error rate), and a trend sparkline per transaction shows where you're really heading. Promote any run to baseline with a click; the statistical gate re-judges against it.

transactionbaselinerun #412run #413run #414trend
checkout412ms418ms +1%421ms +2%498ms +21%
search188ms190ms +1%185ms −2%187ms 0%
login96ms95ms −1%101ms +5%97ms +1%
metric: p95 ▾ · cells clamp ±25%
Data · API · the layers under the ui

Validate the data. Test the pipes.

The data behind every screen gets checked at the source. The APIs underneath get their own suite. Same agent, same graph.

Data · any source, validated there

Compare anything to anything.

Postgres to Excel, MSSQL to an API response. AI reads both schemas and proposes the column mapping; tolerance rules decide what equal means: 2% drift on price is fine, one cent on tax is not. Or just type "ensure no null customer IDs" and the check builds itself. Runs on a Local Runner next to your databases, so data never leaves your network.

orders.xlsx ↔ postgres.orders · row 1042✓ match
unit_price · 1.7% drift✓ within 2% tolerance
tax_total · +£0.01✗ mismatch · zero tolerance
PostgresMySQLMSSQLOracleExcelCSVJSONAPI
triage · known mismatches baselined · verdicts human-approved
API · the layer under the ui

APIs are tests too.

Build requests by hand or import curl, OpenAPI, Postman collections, or HAR, including the captures your perf recorder already made. Assertions are visual (status, time, JSONPath, schema) with a code escape hatch. Auth profiles (OAuth2, SigV4, mTLS) attach anywhere; secrets live in a vault, never inline.

POST/api/orders/{{orderId}}/confirm
status = 200✓
time < 800ms✓
$.payment.state = "settled"✓
$.body.id → {{orderId}} · feeds the next step
api steps compose into the same test cases + cycles as ui steps

Performance, Data, and API testing are included in Pro. See pricing →

Test management · the ledger

Every artifact, linked.

From requirement to report, every artifact stays bound to the next, and the AI does the work at each step. Your team keeps the ledger honest.

Test cases · signature

Human intent. Machine steps.

One layer reads like a story for stakeholders. The other binds to real elements for the runner. Both stay in sync, automatically.

Human intent Machine steps
100% in sync
Layer 1
Given a valid email…
Layer 2
fill('#email',…)
The lifecycle · one chain

Requirement to report.

Requirements
Synced from Jira, GitHub, Linear, Azure DevOps. AI scores quality and binds them to UI.
Test cases
Human-readable intent over machine-bound steps, kept in sync.
Cycles
Hundreds run in parallel. AI retries flakes and files the real bugs.
Defects
Auto-filed with repro, logs and the right labels, pushed to your tracker.
Reports
Live dashboards with LLM-narrated executive summaries.
Admin · make it yours

Customize every layer.

Models, fields, rules, automation, infra. Every layer ships ready, and bends to how your team works.

Bring any model
AI infrastructure

Hosted to start. Your own keys when you want, routed per project.

ClaudeOpenAIGeminiOllama
Fields on everything
Custom fields

Any entity, any type. Wired into filters, reports and AI context.

Teach your standards
Guardrails · prompts · evals

Prompts, guardrails and evals. Tested in a sandbox before they go live.

sandbox-first
Runs itself
Auto modes

Schedule runs, or trigger on Jira tickets, PR merges and deploys.

croneventwebhook
Run on your infra
Local CI agents

CLI for Jenkins, GitHub Actions and GitLab CI. Your machines, your network.

$ ordel-agent connect
The landscape · where Ordel sits

Management tools don't execute.
Automation tools don't manage.

Rivals caught up on the basics. Only Ordel runs the whole cycle, plus the parts no one else ships.

Table stakes · everyone now
Where Ordel pulls ahead
Manage
Generate
Execute
Self-heal
Customize AI
BYO keys
Performance
Data
TestRail
mabl
Katalon
Testim
Ordel
has it caveat missinghover any dot for the detail
Table stakes · everyone now
Manage
TestRail mabl Katalon Testim Ordel
Generate
TestRail mabl Katalon Testim Ordel
Execute
TestRail mabl Katalon Testim Ordel
Self-heal
TestRail mabl Katalon Testim Ordel
Where Ordel pulls ahead
Customize AI
TestRail mabl Katalon Testim Ordel
BYO keys
TestRail mabl Katalon Testim Ordel
Performance
TestRail mabl Katalon Testim Ordel
Data
TestRail mabl Katalon Testim Ordel

Comparison reflects vendor documentation as of 2026-04. Competitors' AI features verified: TestRail Copilot, mabl Auto-generated tests, Katalon StudioAssist, Testim AI. A missing dot reflects a feature the vendor does not ship today.

Per user · 14-day free trial on every plan · cancel anytime

One price per person. The agent is included.

Management, automation, healing and the MCP server on every plan. Professional adds performance and data testing, and lets you bring your own models.

Tier 01
Starter
Teams starting out
$19/user/mo
or $190 /user/yr

The agent, the recorder, and the whole management ledger. Hosted AI included.

  • →Unlimited users
  • →Unlimited projects and test cases
  • →20 GB storage
  • →Cloud + local execution
  • →Self-healing · MCP · audit log
  • →Jira, Linear, GitHub, Azure DevOps
Recommended
Tier 02
Professional
The whole cycle
$49/user/mo
or $490 /user/yr

Everything in Starter, plus the layers under the UI and AI you control.

  • →Unlimited projects and test cases
  • →100 GB storage
  • →Performance testing
  • →Data and API testing
  • →Custom AI · prompts + guardrails
  • →Priority execution queue
Tier 03 · SSO/SAML
Enterprise
Regulated orgs at scale
Bespoke

Ordel governed for scale. On-prem, your own models, full compliance.

  • →Unlimited everything
  • →Everything in Professional
  • →SSO · SAML
  • →On-prem / custom LLM
  • →Dedicated SLA

Stop maintaining tests.
Start setting the standard.

Fourteen-day free trial on every plan, cancel anytime. Point it at your app, accept the map, and approve the first test it writes.

claude mcp add --transport http ordel https://ordel.io/api/mcp