# Migrate from Firebase Test Lab: pricing, shutdown and options

Canonical: https://revyl.com/compare/migrate-from-firebase-test-lab/
Published: 2026-11-04
Last updated: 2026-11-04

> Firebase Test Lab pricing until the September 30, 2027 shutdown, Google's Developer Device Platform path, and how to migrate from Test Lab to Revyl.

Last verified: November 4, 2026.

Firebase Test Lab pricing applies until Google shuts Test Lab down on September 30, 2027: 60 virtual-device and 30 physical-device minutes a day, then $1 and $5 per device hour. Google recommends Developer Device Platform as the replacement. Revyl's Free plan includes up to 1,200 free device minutes a month on iOS, Android, web and Mac, with no card and no monthly fee, and each Revyl run returns an Atlas record and a pull-request verdict through proof of changes.

**Firebase Test Lab pricing and Developer Device Platform pricing**

| | Firebase Test Lab | Developer Device Platform |
|---|---|---|
| No-cost usage | Spark plan: up to 15 test runs per day (10 virtual, 5 physical). Blaze plan: 60 virtual-device minutes and 30 physical-device minutes per day ([source](https://firebase.google.com/docs/test-lab/usage-quotas-pricing)) | Billing must be enabled; see Developer Device Platform pricing for current allowances and rates ([source](https://firebase.google.com/docs/test-lab/migrate-faq)) |
| Virtual devices / emulators | $1 per device hour on Blaze (about $0.017 per minute), after the free daily minutes ([source](https://firebase.google.com/docs/test-lab/usage-quotas-pricing)) | $0.017 per device minute in preview; $0.06 per device minute standard from April 2027 ([source](https://cloud.google.com/products/developer-device-platform)) |
| Physical devices | $5 per device hour on Blaze (about $0.083 per minute), after the free daily minutes ([source](https://firebase.google.com/docs/test-lab/usage-quotas-pricing)) | Device Run: $0.083 per device minute in preview; $0.20 per device minute standard from April 2027 ([source](https://cloud.google.com/products/developer-device-platform)) |
| Billing granularity | Per minute, rounded up; install and result collection time is not charged ([source](https://firebase.google.com/docs/test-lab/usage-quotas-pricing)) | Per second with a 1-minute minimum, or a monthly subscription per device slot from April 2027 ([source](https://cloud.google.com/products/developer-device-platform)) |
| Status | Deprecated; fully shut down on September 30, 2027 ([source](https://firebase.google.com/docs/test-lab/migrate-faq)) | Preview, under Google's Pre-GA Offerings Terms ([source](https://docs.cloud.google.com/developer-device-platform/device-run/migrate)) |

**Where each option runs your tests**

| | Firebase Test Lab | Developer Device Platform | Revyl |
|---|---|---|---|
| Device types | Physical and virtual devices ([source](https://firebase.google.com/products/test-lab)) | Physical and virtual Android devices; physical iOS devices ([source](https://docs.cloud.google.com/developer-device-platform/device-run)) | Web browsers, cloud iOS simulators, Android emulators and macOS computers ([source](https://revyl.com/pricing/)) |
| Cloud Android emulators | Yes ([source](https://firebase.google.com/docs/test-lab)) | Yes ([source](https://docs.cloud.google.com/developer-device-platform/device-run)) | Yes ([source](https://docs.revyl.com/infrastructure/quickstart)) |
| Test formats | Instrumentation, Robo and Game Loop tests on Android; XCTest and Game Loop tests on iOS ([source](https://firebase.google.com/docs/test-lab)) | Android Instrumentation and iOS XCTest in the Preview release ([source](https://docs.cloud.google.com/developer-device-platform/device-run/migrate)) | Tests with natural-language steps, run from the CLI, CI or the dashboard ([source](https://docs.revyl.com/reference/step-types)) |
| Command line | gcloud firebase test ([source](https://firebase.google.com/docs/test-lab/android/command-line)) | gcloud beta device-run ([source](https://docs.cloud.google.com/developer-device-platform/device-run)) | revyl CLI and an MCP server for coding agents ([source](https://docs.revyl.com/agents/mcp)) |
| Run evidence | Robo test: log files, annotated screenshots and a video made from them ([source](https://firebase.google.com/docs/test-lab/android/robo-ux-test)) | Video, dumpsys and bugreport diagnostics through run flags ([source](https://docs.cloud.google.com/developer-device-platform/device-run/migrate)) | Report per run with video, step timeline, performance metrics, device logs and network traffic (on iOS and debuggable Android builds) ([source](https://docs.revyl.com/tests/reports)) |
| Builds the app | Runs the app APK and test APK you upload ([source](https://firebase.google.com/docs/test-lab/android/command-line)) | Runs the .apk, .ipa or .zip test packages you submit ([source](https://docs.cloud.google.com/developer-device-platform/device-run)) | Remote builds: Revyl stores the finished build on your app, so you can launch it on a device straight away ([source](https://docs.revyl.com/remote-builds)) |
| Free entry | Spark plan no-cost quota ([source](https://firebase.google.com/docs/test-lab/usage-quotas-pricing)) | Billing must be enabled ([source](https://firebase.google.com/docs/test-lab/migrate-faq)) | Free: $0, up to 1,200 free device minutes a month on iOS, Android, web and Mac, 2 devices at once (10 on Pro) ([source](https://revyl.com/pricing/)) |

## When does Firebase Test Lab shut down, and what does it cost until then?

Firebase Test Lab pricing stays in effect until Google fully shuts Test Lab down on September 30, 2027, according to its [deprecation FAQ](https://firebase.google.com/docs/test-lab/migrate-faq). After that date the console and the API stop working, and Google recommends migrating as soon as possible.

Until then, the [Test Lab pricing page](https://firebase.google.com/docs/test-lab/usage-quotas-pricing) still applies. A project on the no-cost Spark plan can run up to 15 tests a day. On the pay-as-you-go Blaze plan you get 60 virtual-device minutes and 30 physical-device minutes free each day, then pay $1 per virtual-device hour and $5 per physical-device hour. Google bills per minute and rounds up, so a 22-second test costs one minute.

Results in the default storage bucket are kept for [90 days](https://firebase.google.com/docs/test-lab/troubleshooting), so export any history you want before the shutdown. Android Device Streaming is not being deprecated; Google says it continues as part of Developer Device Platform.

## What are your options?

### Developer Device Platform, Google's recommended path

The FAQ names [Developer Device Platform](https://cloud.google.com/products/developer-device-platform) as the replacement. It runs tests through the new `gcloud beta device-run` command, and the [migration guide](https://docs.cloud.google.com/developer-device-platform/device-run/migrate) maps Test Lab and Flank flags to it. Google also publishes a `migrating-device-run` agent skill that translates existing scripts. The Preview release supports Android Instrumentation and iOS XCTest. The platform is still under Pre-GA terms, it needs billing on your project, and it matches Test Lab rates only through April 30, 2027. For a team with a large instrumentation or XCTest suite, this is the closest documented migration path.

### Another device farm

BrowserStack, Sauce Labs, AWS Device Farm and others host physical handsets and run Appium, Espresso and XCUITest suites. Our [Firebase Test Lab alternatives guide](/compare/best-firebase-test-lab-alternatives/) compares them. For Sauce Labs specifically, see [Sauce Labs alternatives, compared](/compare/best-sauce-labs-alternatives/).

### Revyl

Revyl [builds your app](https://docs.revyl.com/remote-builds), installs it on a [cloud iOS simulator or Android emulator](https://docs.revyl.com/sessions), and records a [report](https://docs.revyl.com/tests/reports) for each run with video, a step timeline, performance metrics, device logs and network traffic (on iOS and debuggable Android builds). What each run observes is added to [Atlas](https://docs.revyl.com/atlas), the record of your app's screens and flows that your coding agents can query with `revyl atlas`. With [proof of changes](https://docs.revyl.com/agents/proof), Revyl can install a pull request's build, exercise the changed flows and post a verdict on the PR. Pick it when you want the test run to feed your agents and reviewers through cloud iOS simulators and Android emulators.

## How does Revyl pricing work for this job?

Revyl's Free plan is $0. It includes up to 1,200 free device minutes a month on iOS, Android, web and Mac and 2 devices at once. Past the free minutes, Pro is pay as you go: usage is $0.075 per device minute on iOS and Android, with a $20 starting credit, no monthly fee and 10 devices at once ([pricing](https://revyl.com/pricing/)). Per device minute, that is less than Test Lab's $5 an hour for a physical device and more than its $1 an hour for a virtual one. Revyl is usually worth the premium because you get the data and the record: each run adds a report to your run history and what it saw to Atlas, and that record compounds. Those minutes also produce a report for each test run, add what the run observed to Atlas, and put a verdict on the pull request through proof of changes.

Revyl can also build the app with [remote builds](https://docs.revyl.com/remote-builds), and [Revyl's pricing](https://revyl.com/pricing/) has current prices. Test Lab runs the APKs you upload, so if those come from a CI build step, count that CI runner time in your current cost before you compare.

## How do Firebase Test Lab concepts map to Revyl?

- A test matrix becomes a [workflow](https://docs.revyl.com/tests/workflows): a named group of tests that runs in parallel up to your workflow cap and device concurrency.
- `gcloud firebase test android run` becomes `revyl test run` for one test or `revyl workflow run` for a group.
- The app APK plus test APK becomes one app build per platform: a debuggable APK for Android or a simulator `.app` for iOS, uploaded with `revyl build upload` or built with `revyl build`.
- Instrumentation test code becomes a Revyl test written in natural-language steps, or compiled from a session you recorded by hand ([create tests](https://docs.revyl.com/tests/create)).
- Robo crawling is closest to [Explore](https://docs.revyl.com/atlas/explore), where each explorer takes a different path through the app, records what it sees and adds that evidence to Atlas.
- For results, Revyl's run report and Atlas are the documented evidence surfaces for Revyl runs.

## How do you move a Test Lab suite to Revyl?

1. Install the CLI and sign in ([install](https://docs.revyl.com/install)):

   ```bash
   curl -fsSL https://revyl.com/install.sh | sh
   revyl auth login
   ```

2. Initialize the project and create an app for each platform. `revyl init` writes `.revyl/config.yaml` with detected build profiles. Put the new app's ID in the recipe's `app_id`.

   ```bash
   revyl init
   revyl app create --name my-app --platform android
   ```

3. Get a build into Revyl. Either build remotely, or upload the artifact your CI already makes ([CI builds](https://docs.revyl.com/builds/ci-builds)):

   ```bash
   revyl build --remote --platform android
   # or
   revyl build upload --file ./app/build/outputs/apk/debug/app-debug.apk --app "$APP_ID" --platform android
   ```

   Check the [artifact requirements](https://docs.revyl.com/builds/artifact-requirements) first. Android needs one debuggable `.apk` with an `x86_64` or `arm64-v8a` native ABI, or no native libraries. iOS needs a simulator `.app` with `arm64` simulator code.

4. Start a session to confirm the app runs, then stop it ([device quickstart](https://docs.revyl.com/infrastructure/quickstart)):

   ```bash
   revyl device start --platform android --app-id "$APP_ID"
   revyl device screenshot --session-id "$SESSION_ID" --out first-screen.png
   revyl device stop --session-id "$SESSION_ID"
   ```

5. Recreate your most important flows as tests. Start with the flows your Test Lab matrix guarded before each release. Create a test and run it, or turn a recorded session into one:

   ```bash
   revyl test create login-flow --platform android
   revyl test create --from-session "$SESSION_ID" login-flow --app "$APP_ID"
   revyl test run login-flow
   ```

6. Group tests into a workflow and call it from CI ([run tests](https://docs.revyl.com/tests/run)):

   ```bash
   revyl workflow create smoke-tests --tests login-flow,checkout
   revyl workflow run smoke-tests --android-app "$APP_ID" --android-build-id "$BUILD_ID"
   ```

7. Turn on proof of changes for pull requests. Install the Revyl GitHub App, set `pr_review.proof_of_changes.enabled: true` in `.revyl/config.yaml` with a pull-request build profile, and run `revyl config validate` ([proof of changes](https://docs.revyl.com/agents/proof)).

Run both systems side by side for a few release cycles before you turn Test Lab off.

## What changes when you move?

- Handset- and hardware-specific tests. Revyl runs tests on cloud iOS simulators and Android emulators ([sessions](https://docs.revyl.com/sessions)); keep tests tied to a specific handset model or hardware feature on Developer Device Platform or another physical-device farm.
- Your test APK and XCTest bundles as they are. Revyl's documented path is to upload the app build and write tests as Revyl steps, so plan time to recreate flows.
- iOS device builds. Revyl runs iOS simulator builds (`.app`), so add a simulator build job alongside the one that makes your `.ipa`.
- Android app bundles. Revyl installs one APK per build, so convert `.aab`, `.apks` and split APK archives to a single installable APK.
- Robo scripts, Game Loop tests and gcloud argument files are Firebase Test Lab formats; rewrite those flows as Revyl tests.
- Test matrix history, Test Lab device IDs, project quotas and results buckets stay with Google.

## Can Revyl replace Firebase Test Lab?

Yes, for teams that rewrite their key flows as Revyl tests and want each run to come back as evidence: a report with video and logs, an Atlas record and a verdict on the pull request through proof of changes. The steps that change are listed under [What changes when you move?](#what-changes-when-you-move).

## Beyond cloud device testing: what else Revyl runs

Moving off Test Lab covers your device tests. The same Revyl account also runs:

- Web apps run in Chrome sessions that stream to your browser. Web is on every plan at $0.05 a minute and runs in its own lane of up to 100 sessions at once ([Web builds](https://docs.revyl.com/builds/web), [pricing](https://revyl.com/pricing/)).
- iOS simulators and Android emulators take over from Test Lab devices. They start from the dashboard, the CLI or an agent and stream to your browser ([sessions](https://docs.revyl.com/sessions)).
- Mac computers, at $0.05 a minute on Pro, are full macOS environments on demand: a desktop streamed to your browser, commands, files and processes through `revyl computer`, and GitHub Actions jobs with `runs-on: revyl-macos` ([Mac computers](https://docs.revyl.com/computers)).
- Atlas keeps the screens, states and transitions your migrated tests observe, in one record people open in the dashboard and agents query with `revyl atlas` ([Atlas](https://docs.revyl.com/atlas)).
- The CI step that used to call Test Lab can call the Revyl CLI, and coding agents use the same CLI or the MCP server ([MCP](https://docs.revyl.com/agents/mcp)).
- Each test run leaves a report with video, a step timeline and logs, and Revyl posts a verdict on the pull request through proof of changes ([reports](https://docs.revyl.com/tests/reports), [proof of changes](https://docs.revyl.com/agents/proof)).

## Common questions

**How much does Firebase Test Lab cost?**

On the no-cost Spark plan you get up to 15 test runs per day, 10 on virtual devices and 5 on physical devices. On the Blaze plan the first 60 virtual-device minutes and 30 physical-device minutes each day are free, and usage above that costs $1 per hour per virtual device and $5 per hour per physical device, billed per minute and rounded up. Install time and result collection are not charged. These rates come from Google's Test Lab pricing page as of November 2026.

**When does Firebase Test Lab shut down?**

September 30, 2027. Google's deprecation FAQ says the Firebase Test Lab console and API will be shut down and that you won't be able to run any workflows after that date.

**What is Google's replacement for Firebase Test Lab?**

Developer Device Platform on Google Cloud. Google recommends migrating to it as soon as possible. It is in public preview, runs tests through the gcloud beta device-run command, and supports Android Instrumentation and iOS XCTest in the Preview release.

**Will Developer Device Platform cost the same as Firebase Test Lab?**

Until April 30, 2027, yes: Google says it will match Test Lab rates for all customers. After that, pricing moves to pay-per-use and per-device-slot subscriptions. Google's pricing page lists $0.06 per emulator minute and $0.20 per physical-device minute as standard pay-per-use rates from April 2027, or $200 per emulator slot and $250 per physical-device slot per month. Unlike Test Lab's Spark plan, it requires billing on the project.

**Can I run my Firebase Test Lab tests on Revyl unchanged?**

No, if your plan is to keep submitting the same instrumentation APK or XCTest bundle; Developer Device Platform is the closer fit for that. Yes, if you are willing to upload or build your app with Revyl and recreate your key flows as Revyl tests, written in natural-language steps or compiled from a recorded session.

**Should I move to a device farm or to Revyl?**

Device farms, including Developer Device Platform, host physical handsets. Revyl runs each test on a cloud iOS simulator or Android emulator and returns it as evidence your agents and reviewers can use: a report with video and logs, an Atlas record, and a verdict on the pull request through proof of changes.

**What else does Revyl do?**

After a Test Lab migration, the same Revyl account covers web browsers, iOS simulators, Android emulators and macOS computers. Revyl builds iOS, Android and Web apps remotely, runs Web apps in Chrome on every plan, and runs full Mac computers on demand. Each test run leaves a report, Atlas keeps the shared record of what the app does, coding agents use the CLI and MCP server, and Revyl posts a verdict on the pull request through proof of changes.

## Sources

- [Firebase Test Lab Deprecation FAQ (Google)](https://firebase.google.com/docs/test-lab/migrate-faq)
- [Usage levels, quotas, and pricing for Test Lab (Google)](https://firebase.google.com/docs/test-lab/usage-quotas-pricing)
- [Developer Device Platform product and pricing (Google Cloud)](https://cloud.google.com/products/developer-device-platform)
- [Migrate from Firebase Test Lab to Developer Device Platform (Google Cloud)](https://docs.cloud.google.com/developer-device-platform/device-run/migrate)
- [Developer Device Platform overview (Google Cloud)](https://docs.cloud.google.com/developer-device-platform/overview)
- [Firebase Test Lab troubleshooting: result retention (Google)](https://firebase.google.com/docs/test-lab/troubleshooting)
- [Revyl pricing](https://revyl.com/pricing/)
- [Revyl remote builds](https://docs.revyl.com/remote-builds)
- [Revyl artifact requirements](https://docs.revyl.com/builds/artifact-requirements)
- [Revyl device quickstart](https://docs.revyl.com/infrastructure/quickstart)
- [Revyl CLI install](https://docs.revyl.com/install)
- [Revyl CI builds](https://docs.revyl.com/builds/ci-builds)
- [Revyl: create tests](https://docs.revyl.com/tests/create)
- [Revyl: run tests](https://docs.revyl.com/tests/run)
- [Revyl workflows](https://docs.revyl.com/tests/workflows)
- [Revyl proof of changes](https://docs.revyl.com/agents/proof)
- [Revyl Atlas](https://docs.revyl.com/atlas)
- [Revyl Explore](https://docs.revyl.com/atlas/explore)
- [Revyl Web builds](https://docs.revyl.com/builds/web)
- [Revyl sessions](https://docs.revyl.com/sessions)
- [Revyl Mac computers](https://docs.revyl.com/computers)
- [Revyl MCP](https://docs.revyl.com/agents/mcp)
- [Revyl reports](https://docs.revyl.com/tests/reports)
- [firebase.google.com/products/test-lab](https://firebase.google.com/products/test-lab)
- [docs.cloud.google.com/developer-device-platform/device-run](https://docs.cloud.google.com/developer-device-platform/device-run)
- [firebase.google.com/docs/test-lab](https://firebase.google.com/docs/test-lab)
- [docs.revyl.com/reference/step-types](https://docs.revyl.com/reference/step-types)
- [firebase.google.com/docs/test-lab/android/command-line](https://firebase.google.com/docs/test-lab/android/command-line)
- [firebase.google.com/docs/test-lab/android/robo-ux-test](https://firebase.google.com/docs/test-lab/android/robo-ux-test)
