If we hire an outside team to build a Robot Framework suite, will our own staff end up running it afterward, or does the vendor keep that role?

Neither is settled by the record. The catalog tags a company for working with Robot Framework without recording which side ends up running the resulting suite once it is written, and that detail sits outside the tracked fields entirely. One arrangement does point toward the client side by its own definition: three companies in this composition state staff augmentation as an engagement model, meaning individual testers join the client's own team and report inside the client's process. That single arrangement is the only field-level signal pointing toward client-side execution; every other engagement model recorded here stays silent on which side keeps the suite once it is delivered.

We want the vendor's own tests reviewed and signed off by our product stakeholders, beyond internal regression checks. Does building with Robot Framework already mean a company sells that as its own service?

No. The catalog's own definition names Robot Framework a framework built for acceptance testing. That describes the tool itself, not any single company's own sales list. Only four of the eleven companies working with Robot Framework in this composition separately list acceptance testing as a service of their own; the other seven work with the tool without naming that service at all. A company can use a keyword-driven tool built for sign-off style testing while still selling only automation or regression work under its own name. Ask whether the acceptance phase itself, with your own stakeholders reviewing the result, is written into the quoted scope of work.

A vendor's case study shows a big drop in regression time from automation work. How do I know that improvement came from Robot Framework specifically, and not some other tool the same company also runs?

You cannot, from the record alone. A published coverage or regression-time metric can support the Automation first tag without saying which framework in a company's stack produced it. Every company on this page that carries both Robot Framework and the Automation first tag also lists at least one other automation framework, such as Selenium, Tosca or Playwright, alongside it. None of them lists Robot Framework as its only tool. The published record ties the metric to a company's automation work as a whole; it does not single out Robot Framework separately within that stack.

Best Robot Framework QA companies in 2026

QA Rating is published independently, and its publisher owns no company listed in this catalog.

11 testing companies in this catalog list Robot Framework among the frameworks and tools they work with. They are grouped below by what each is best suited for, in 8 groups. 2 of them hold a certificate confirmed by a register entry and 7 publish a rate card. Composition and order last changed on September 3, 2026.

11 companies. Ordered by the number of verified reviews on external platforms, highest first. Companies with an equal count are ordered by name.

The companies

Robot Framework: 11 companies, grouped by what they are best suited for.
#	Company	Case studies	Published rates	Team size	Reviews
Nearshore for the EU At least one delivery location in the EU or the EEA, or in Ukraine, Georgia, Serbia or Moldova.
1	QA Madness	2	Blended $25-49/hclutch.co	51-200 people	44
2	Luxe Quality	2	Blended $25-49/hclutch.co	51-200 people	21
3	QATestLab	2	Blended $25-49/hclutch.co	501-1000 people	17
4	QAwerk	3	Blended $25-49/hclutch.co	51-200 people	13
5	andagon people GmbH	4	Blended $100-149/hclutch.co	51-200 people	0
6	appmatics GmbH	7	Not published	201-500 people	0
7	imbus AG	Not published	Not published	201-500 people	0
8	Qytera Quality GmbH	7	Not published	11-50 people	0
9	SQA Service	7	Not published	11-50 people	0
Automation first Test automation is offered as a service, and at least one published case study reports a coverage or regression time metric.
1	QA Madness	2	Blended $25-49/hclutch.co	51-200 people	44
2	Luxe Quality	2	Blended $25-49/hclutch.co	51-200 people	21
4	QAwerk	3	Blended $25-49/hclutch.co	51-200 people	13
5	andagon people GmbH	4	Blended $100-149/hclutch.co	51-200 people	0
6	appmatics GmbH	7	Not published	201-500 people	0
Embedded team model The dedicated team engagement model is offered, and at least one published case study.
1	QA Madness	2	Blended $25-49/hclutch.co	51-200 people	44
4	QAwerk	3	Blended $25-49/hclutch.co	51-200 people	13
6	appmatics GmbH	7	Not published	201-500 people	0
Security focus Security testing is offered, together with either penetration testing or a verified ISO/IEC 27001 certificate, and at least one published case study.
1	QA Madness	2	Blended $25-49/hclutch.co	51-200 people	44
3	QATestLab	2	Blended $25-49/hclutch.co	501-1000 people	17
4	QAwerk	3	Blended $25-49/hclutch.co	51-200 people	13
Nearshore for the USA At least one delivery location in Canada, Mexico, Central America or South America.
7	imbus AG	Not published	Not published	201-500 people	0
9	SQA Service	7	Not published	11-50 people	0
Performance engineering Performance testing is offered as a service, and at least one published case study reports a throughput or latency metric.
3	QATestLab	2	Blended $25-49/hclutch.co	501-1000 people	17
8	Qytera Quality GmbH	7	Not published	11-50 people	0
Device lab coverage A published device lab of 100 real devices or more, with a source.
3	QATestLab	2	Blended $25-49/hclutch.co	501-1000 people	17
Fast onboarding A published onboarding time of 14 days or less, with a source.
3	QATestLab	2	Blended $25-49/hclutch.co	501-1000 people	17
Other companies in this axis No applicability tag met its criterion for these profiles.
10	Testrig Technologies	Not published	Blended up to $25/hclutch.co	51-200 people	7
11	iBeta Quality Assurance	1	Blended $50-99/hclutch.co	51-200 people	4

Automation first sits entirely inside Nearshore for the EU

Automation first names five companies in this composition: QA Madness, Luxe Quality, QAwerk, andagon people GmbH and appmatics GmbH. Nearshore for the EU covers nine of the eleven companies on this page, and every one of the five Automation first companies is among those nine. The containment runs one way only. Four members of Nearshore for the EU stay outside Automation first. No company on this page carries Automation first without also carrying Nearshore for the EU.

Embedded team model inside Automation first, and where Security focus splits

Embedded team model names three companies: QA Madness, QAwerk and appmatics GmbH. All three also appear among the five Automation first companies above. Security focus names three companies of its own: QA Madness, QATestLab and QAwerk. QA Madness and QAwerk carry both Embedded team model and Security focus. appmatics GmbH carries Embedded team model without Security focus. QATestLab carries Security focus without Embedded team model.

Nearshore for the USA runs alongside Nearshore for the EU

Nearshore for the USA names two companies: imbus AG and SQA Service. Both also carry Nearshore for the EU, and neither carries Nearshore for the USA without it. Performance engineering names two companies as well, QATestLab and Qytera Quality GmbH, and both of these also carry Nearshore for the EU.

One company holds both single-member tags

Device lab coverage and Fast onboarding each name exactly one company on this page, and it is the same company in both cases: QATestLab. One tag reads a published device lab, the other a published onboarding time, and the two figures sit in separate places in a profile. QATestLab carries five tags in total: Fast onboarding, Device lab coverage, Performance engineering, Security focus and Nearshore for the EU. No other company on this page reaches more than four tags, a count reached by QA Madness and QAwerk.

Two companies outside every tag on this page

Testrig Technologies and iBeta Quality Assurance carry none of the eight tags used on this page. These are the same two companies missing from Nearshore for the EU, since that tag covers the other nine. Sitting outside every tag on this page records that no published, sourced fact matched a tag's criterion at the time of the check. The underlying capability is a separate question, and the record on this page does not answer it.

How this ranking was put together

Membership is computed from the profile, not chosen: companies appear here when they list Robot Framework among the frameworks and tools they work with, as their own profile states. Position in a ranking cannot be bought. Paid options are limited to the extended profile, labelled sponsor slots and lead forms, and none of them affect tags or order.

The table compares the fields that decide this axis: case studies, published rates, team size, plus the number of verified reviews on external platforms. Rates, minimum project size and onboarding time carry the source they came from next to the value.

Nearshore for the EU: At least one delivery location in the EU or the EEA, or in Ukraine, Georgia, Serbia or Moldova.
Automation first: Test automation is offered as a service, and at least one published case study reports a coverage or regression time metric.
Embedded team model: The dedicated team engagement model is offered, and at least one published case study.
Security focus: Security testing is offered, together with either penetration testing or a verified ISO/IEC 27001 certificate, and at least one published case study.
Nearshore for the USA: At least one delivery location in Canada, Mexico, Central America or South America.
Performance engineering: Performance testing is offered as a service, and at least one published case study reports a throughput or latency metric.
Device lab coverage: A published device lab of 100 real devices or more, with a source.
Fast onboarding: A published onboarding time of 14 days or less, with a source.

The criteria for this axis are on the methodology page, together with field definitions and the rule for editorial order. Changes of order are recorded in the changelog.

Questions

If we hire an outside team to build a Robot Framework suite, will our own staff end up running it afterward, or does the vendor keep that role?: Neither is settled by the record. The catalog tags a company for working with Robot Framework without recording which side ends up running the resulting suite once it is written, and that detail sits outside the tracked fields entirely. One arrangement does point toward the client side by its own definition: three companies in this composition state staff augmentation as an engagement model, meaning individual testers join the client's own team and report inside the client's process. That single arrangement is the only field-level signal pointing toward client-side execution; every other engagement model recorded here stays silent on which side keeps the suite once it is delivered.
We want the vendor's own tests reviewed and signed off by our product stakeholders, beyond internal regression checks. Does building with Robot Framework already mean a company sells that as its own service?: No. The catalog's own definition names Robot Framework a framework built for acceptance testing. That describes the tool itself, not any single company's own sales list. Only four of the eleven companies working with Robot Framework in this composition separately list acceptance testing as a service of their own; the other seven work with the tool without naming that service at all. A company can use a keyword-driven tool built for sign-off style testing while still selling only automation or regression work under its own name. Ask whether the acceptance phase itself, with your own stakeholders reviewing the result, is written into the quoted scope of work.
A vendor's case study shows a big drop in regression time from automation work. How do I know that improvement came from Robot Framework specifically, and not some other tool the same company also runs?: You cannot, from the record alone. A published coverage or regression-time metric can support the Automation first tag without saying which framework in a company's stack produced it. Every company on this page that carries both Robot Framework and the Automation first tag also lists at least one other automation framework, such as Selenium, Tosca or Playwright, alongside it. None of them lists Robot Framework as its only tool. The published record ties the metric to a company's automation work as a whole; it does not single out Robot Framework separately within that stack.

Other axes these companies appear on

Type of testing: Test automation 11 of these 11 companies also stand there
Delivery location: Europe 10 of these 11 companies also stand there
Delivery proximity: nearshore for a buyer in the EU 9 of these 11 companies also stand there
Industry: Ecommerce 8 of these 11 companies also stand there

How to choose a vendor on this axis

Published by QA RatingPublished on September 3, 2026Updated on September 3, 2026

Every fact about a company comes from a listed source. A field without a source stays empty. A certificate counts as confirmed only when a registry, certificate or auditor report backs it; a certificate the company only claims about itself is published separately, under that label. Vendors can request a correction at hello@qa-rating.com. A correction is applied when it comes with a public source.