Sauce Labs review: pricing, alternatives and setup

For Selenium and Appium, Sauce Labs is a remote WebDriver endpoint: your test runs on your machine or CI agent and opens a session against ondemand.<region>.saucelabs.com, with a sauce:options capability carrying credentials, the job name, build and tunnel. Every command crosses the network. For Playwright, Cypress, TestCafe, Espresso and XCUITest, the saucectl CLI works differently: it bundles the files under rootDir, uploads them, installs any npm packages you list, and runs the framework itself on Sauce Labs machines, sending back results and artefacts. The second model avoids per-command latency, but your test code and its dependencies must work in an environment you do not control.

Sauce Labs sells two clouds. The Virtual Device Cloud provides desktop browsers on Windows and macOS virtual machines plus Android emulators and iOS simulators, which start quickly and suit most functional automation. The Real Device Cloud provides physical phones and tablets, for hardware-dependent behaviour, real performance and the exact device a customer reported. They are priced as separate plans. Your data centre matters here: the docs note that virtual device testing is not available in the US East 4 and Asia South 2 data centres, so the region you choose at sign-up shapes what you can run.

Each account works in one or more data centres: US West 1, US East 4, EU Central 1 and Asia South 2. The data centre decides where tests run and where artefacts are stored, which is the deciding factor for organisations with residency requirements. Self-service and trial users pick a data centre when they sign up; Enterprise customers agree theirs in the contract. Every client setting must agree on it: the WebDriver endpoint, the REST API host, saucectl’s region and the Sauce Connect region. A mismatch is a common reason for jobs that never appear or tunnels that tests cannot find.

Sauce Connect is a proxy you run inside your network. It opens an outbound connection to Sauce Labs and carries traffic from remote browsers and devices back to hosts they cannot otherwise reach, such as localhost or an internal staging server. Version 5 starts with sc run and requires both a tunnel name and a region. Tests opt in by naming the tunnel, through tunnelName in sauce:options or the tunnel settings in saucectl’s config. Shutting the proxy down waits for active jobs to finish, so a CI step can stop it cleanly after the tests.

saucectl reads .sauce/config.yml, uploads everything under rootDir that .sauceignore does not exclude, and runs each suite on the platform it names. Keep rootDir as small as possible and ignore node_modules, reports and build output, or every run uploads them. Pin the Playwright version to the one in package.json so the cloud matches your local runs, and set concurrency to your account’s allowance or below, since the docs warn that a higher value can lead to dropped jobs. Use shard: spec to spread a large suite across machines. Any params you set, such as browserName or workers, are passed to Playwright as command-line flags and override your playwright.config.

The official saucectl-run-action installs saucectl and runs your config, with credentials from repository secrets and options such as region, concurrency and tunnel name as inputs. Pass GITHUB_TOKEN in the environment, as the action’s README asks, or the action can hit GitHub’s API rate limit when it downloads saucectl. For an application that is not publicly reachable, start Sauce Connect 5 earlier in the job, for example with sauce-connect-action at v3, which supports only Sauce Connect 5, and pass the same tunnel name to saucectl. Keep the pull-request run to one or two suites and run the full matrix on a schedule, since every suite consumes concurrency for its duration.

Any pipeline still downloading the Sauce Connect 4 binary stopped working at the end of July 2026, when Sauce Labs stopped accepting its traffic. The migration is mostly command-line changes: start the tunnel with sc run instead of the bare binary, always pass a tunnel name and a region, and rename tunnelIdentifier to tunnelName in capabilities, since the old name is deprecated. Some SC4 features are gone, including the Selenium relay, the PID file and the readyfile, so scripts that waited on a readyfile need to watch for the Sauce Connect is up message or use the official action instead. The sc legacy command translates an old configuration file to the new format.

Give every job a name from the test, a build value from the CI run, and tags for the suite and team, so the dashboard can be filtered when something breaks at scale. Report the job result from every test. Keep sessions short: one test per session, no long sleeps, and sensible idleTimeout and maxDuration values so a hung test releases its slot. Concurrency is shared across the account, so agree a budget per pipeline and schedule large matrices outside working hours. Review the platform list against your analytics a few times a year, because every unused browser version in a matrix costs a parallel slot on every run.