Skip to content

Where your tests actually run.

testrelic studio

Ostra models built for testing, the memory they read, and the harness that runs them in Studio, your terminal, any MCP client and the API.

What it does

One infrastructure target, picked once

Two defaults, zero setup

"This computer" is Local mode's default — nothing provisioned. "TestRelic Cloud" is Cloud mode's default. Both are already selected; you only reach into the catalog when you need something else.

Your own AWS, Azure, or GCP

Provision machines directly inside your own cloud account when a test needs more than your laptop — your infra, your spend, your network boundary, not a shared pool.

A hosted device grid

Point a session at BrowserStack for real browsers and real devices, or TestMu AI for the same plus a grid that heals flaky selectors while your tests run.

Chosen once, from Studio

The target lives in Studio's Infrastructure pane — pick it there and every session, local or cloud, runs against it. No per-test configuration to keep in sync.

Supported platforms

Every target, at a glance

Two built-in defaults, three cloud accounts, two hosted device grids — the full catalog Studio's Infrastructure pane offers, nothing held back for a crop.

Built in

Selected automatically — nothing to provision.

This computer

Local mode's default — nothing provisioned

TestRelic Cloud

Cloud mode's default

Your own cloud

Studio provisions machines directly inside the account you already have.

AWS

Run tests on machines in your own AWS account

Azure

Run tests on machines in your own Azure subscription

GCP

Run tests on machines in your own Google Cloud project

Hosted device grid

Real browsers and real devices, hosted for you.

BrowserStack

Real browsers and real devices, hosted by BrowserStack

TestMu AI

An AI grid that heals flaky selectors while your tests run

Inside Studio

The same catalog, in the app

Every group above is one pane in Studio — pick a target and every session, local or cloud, runs against it.

Built in

"This computer" and "TestRelic Cloud" — the two defaults, already selected for Local and Cloud mode. Nothing to provision.

InfrastructureBuilt in
This computerLocal mode's default — nothing provisionedYou're here
TestRelic CloudCloud mode's default

Nothing to provision

Local mode → this computer

Cloud mode → TestRelic Cloud

Your own cloud

AWS, Azure, or GCP — Studio provisions machines directly inside the account you already have, so the workload counts toward spend you already committed to.

InfrastructureYour account
AWSRun tests on machines in your own AWS account
AzureRun tests on machines in your own Azure subscription
GCPRun tests on machines in your own Google Cloud project

Provisioned by Studio

Your infra · your spend · your network

Credentialsnever leave your machine

A hosted device grid

BrowserStack for real browsers and real devices, or TestMu AI for the same plus selector healing while your tests run.

InfrastructureHosted grid
BrowserStackReal browsers and real devices, hosted by BrowserStack
TestMu AIAn AI grid that heals flaky selectors while your tests run

Real browsers, real devices

Point a session at the grid, run as usual

TestMu AIheals flaky selectors live

FAQ

Common questions

It can be, but it isn't only that. Studio's Infrastructure pane provisions real machines directly in your own AWS account the same way AWS Device Farm does — Studio creates the network and the machine, installs the browsers, and connects it, so you only pick a size. The difference is you aren't limited to AWS: the same pane also connects a hosted device grid (BrowserStack or TestMu AI) or just uses your own computer, and every session — local or cloud — runs against whichever target you picked, from one place instead of three separate accounts.

Yes. Studio creates the network, machine, and browsers in your own account and connects it — you only pick a size. On AWS that ranges from a t3.medium (2 vCPU, 4 GB, $0.0416/hour) for a small suite up to a c6i.4xlarge (16 vCPU, 32 GB, $0.68/hour) for nightly regression, with Azure and GCP offering equivalent tiers. Studio only ever creates a private network and machines tagged for it — no IAM users, no changes to anything else already in your account — and the machine accepts no inbound traffic until a run actually starts.

Yes, both as connectable targets in Studio's Infrastructure pane and, separately, as Cloud Farms integrations on the platform for pulling in build data. LambdaTest rebranded to TestMu AI in January 2026 — same product, same API, same account, new name. Once connected, a target from either shows real browsers and real devices as a hosted grid option; TestMu AI's grid additionally heals flaky selectors while a run is in progress.

Each mode has its own default target, set independently. Local mode defaults to "This computer" — nothing provisioned, results never leave your machine. Cloud mode defaults to "TestRelic Cloud" — results upload and sync to your team. Either default can be swapped for a provisioned AWS/Azure/GCP machine or a hosted device grid; the choice is made once per mode in Studio's Infrastructure pane and every session in that mode runs against it, though a single run can still target something else from the chat box without changing the default.

Two separate costs. TestRelic itself charges nothing extra for Infrastructure beyond the Studio-inclusive Pro plan ($99/month, $79/month billed annually) — provisioning, connecting, and switching targets is part of that plan. Your cloud provider bills you directly and only for what actually runs: an AWS t3.large used for testing runs about $0.0832/hour, so a team running 4 test-hours a day lands around $7-8/month in AWS spend. There is no markup and no TestRelic-managed compute in between.

No. "This computer" and "TestRelic Cloud" are built-in defaults, already selected for Local and Cloud mode respectively — nothing to provision, nothing to connect. You only open the Infrastructure pane and add a target when a suite outgrows a laptop: more parallel runners than one machine can give you, or real devices you don't personally own. Most teams run entirely on the two defaults for weeks before their first AWS machine or BrowserStack connection.

Stop hard-coding where your tests run.

Infrastructure lives inside Studio, which is included in the Pro plan, from $99/month.