Note for buyers
Device and browser clouds named in cases, and what that implies for your bill
Research desk, testautomationvendors.com · published 2026-11-12 · data as of 2026-11-12 · 79 records
- 79
- cases name a cloud
- 12
- distinct clouds
79 of 263 verified cases name a device or browser cloud: BrowserStack (48), AWS (14), LambdaTest (6), Sauce Labs (5), AWS Device Farm (4) and Azure (4). When a vendor's case runs on a hosted cloud, the cloud subscription is a cost line separate from the vendor's rate.
Counts come from verified records. A baseline is the before value a vendor states for a metric; quoted claims carry their grade and baseline flag.
- baseline:
- The measured value before the work started, against which a later value is compared. source
Clouds named
Names as written in the case.
Table view
| Item | Count |
|---|---|
| BrowserStack | 48 |
| AWS | 14 |
| LambdaTest | 6 |
| Sauce Labs | 5 |
| AWS Device Farm | 4 |
| Azure | 4 |
| BlazeMeter | 3 |
| Device Farm | 1 |
| Google Cloud | 1 |
| Kobiton | 1 |
| TestDroid | 1 |
| TestingBot | 1 |
| Total | 89 |
Billing questions
Ask who holds the cloud subscription, how many parallel sessions the suite needs and whether the vendor's quote includes it.
Questions
How many cases name a device cloud?
79 of 263.
Does the site rank clouds?
No.
Is the cloud cost in the vendor rate?
The cases do not say; ask the vendor.
What is a device cloud?
A hosted pool of real or virtual phones, tablets and browsers that tests run on remotely.
Records used
This post reads 79 records; the newest verifiedOn date among them sets the data-as-of date.
Show record ids
a1qa-2, a1qa-4, a1qa-7, a1qa-8, a1qa-9, a1qa-10, a1qa-15, a1qa-16, a1qa-18, a1qa-21, a1qa-23, a1qa-24, a1qa-33, a1qa-34, a1qa-37, a1qa-41, a1qa-42, a1qa-44, a1qa-62, a1qa-64, a1qa-65, a1qa-66, a1qa-71, a1qa-73, abstracta-1, abstracta-2, codoid-1, codoid-5, codoid-13, codoid-15, codoid-23, codoid-25, codoid-39, deviqa-3, deviqa-5, deviqa-9, deviqa-13, deviqa-14, deviqa-15, deviqa-16, deviqa-17, deviqa-24, deviqa-25, deviqa-27, deviqa-28, deviqa-32, deviqa-35, deviqa-37, deviqa-38, deviqa-41, deviqa-46, deviqa-48, deviqa-51, qawerk-1, qawerk-2, qawerk-4, qawerk-6, qawerk-7, qualitest-12, testdevlab-3, testfort-1, testfort-2, testfort-3, testfort-7, testfort-8, testfort-11, testfort-17, testfort-19, testfort-24, testfort-26, testingxperts-3, testrig-1, testrig-6, testrig-7, testrig-8, testrig-10, thinksys-9, zuci-systems-1, zuci-systems-7
More from the blog
Note for buyers
How to read a test automation case study: the fields that are usually missing
222 of 263cases omit start year
Field by field, how often 263 verified automation cases leave out team size, duration, baseline, client name and CI.
data as of 2026-11-12 · 263 records
Note for buyers
Why a percentage without a baseline is a claim, not a result
246percentage claims
246 percentage claims in verified automation cases, and how many state the starting value.
data as of 2026-11-12 · 126 records
Note for buyers
What an automation coverage figure can mean: the denominators seen in published cases
88coverage claims
88 coverage claims sorted by what they measure: test cases, regression effort, features or code.
data as of 2026-11-12 · 76 records
Related pages
Scores and grades describe published evidence as of the verifiedOn date on each item. They do not measure service quality. Verify with the vendor before contracting.