Skip to main content

Introducing O2 Cloud Agent: Your Tests, Executed on Our Infrastructure

Divya Manohar
Divya Manohar
Co-Founder and CEO, DevAssure

There's a number nobody puts in their testing ROI deck: the cost of keeping the test infrastructure alive.

Not writing tests. Running them. The Selenium grid that needs a Chrome bump every six weeks. The CI runners that queue for twenty minutes at 5 PM. The Docker image someone built in 2023 that nobody dares touch. Ask any engineering team where their automation effort actually goes, and "maintaining the thing that runs the tests" is quietly near the top.

Today we're shipping the fix: O2 Cloud Agent. Your tests execute in real browsers on infrastructure we run — nothing to install, nothing to configure, nothing to maintain.

O2 Cloud Agent dashboard — fleet, environments, test steps, and 30-day insights

What it does​

O2 already lets you write tests as plain-English steps:

Login to the app with valid creds
Ensure user is logged in
Log out
Login to the app with invalid creds
Ensure user is not logged in

With Cloud Agent, running that test is now the whole workflow: pick an environment, pick how many agents, hit run. Each agent spins up an isolated real browser session in the cloud and works through your steps the way a human tester would — navigating, clicking, verifying, capturing evidence at every step.

No grid. No runners. No local setup. Your first test executes in the cloud about a minute after sign-up.

Parallelism without the plumbing​

Scaling test execution used to mean scaling infrastructure — more nodes, more containers, more YAML. With Cloud Agent, it's a number field. Two agents run your suite in parallel. Four run it faster. Each agent is an isolated browser session, so tests don't trample each other's state.

The suite that took an afternoon on one machine finishes in minutes. And when something breaks, it doesn't just fail — it's scored, flagged, and captured per step, so you're reviewing evidence, not reproducing bugs.

Test sessions with 1, 2, or 4 Cloud Agents running in parallel

Schedule once, catch regressions forever​

Cloud Agent pairs with scheduled jobs: point a job at an environment, set a cadence — nightly, hourly, post-deploy via your pipeline — and O2 keeps executing without anyone remembering to press run.

Every run lands in the same place: session history, health score per environment, bugs by severity, full step-level detail. When Tuesday's deploy breaks login, you find out Tuesday night — not from a customer on Thursday.

Scheduled nightly regression job on Cloud Agent

Why this matters more in the AI-code era​

Teams are shipping more code than ever, because agents are writing a lot of it. The bottleneck has moved from writing code to verifying it — and verification can't run on infrastructure that itself needs babysitting.

We've been clear about our thesis: the author cannot be the examiner. A coding agent reviewing its own output will miss what it doesn't know it got wrong. O2 is the independent layer that actually exercises your application — and Cloud Agent removes the last excuse for not running that verification continuously. If the check is one click and zero setup, it runs. If it needs a grid, it eventually doesn't.

Pricing​

One flat price: $25 per agent, per month — unlimited test executions. No per-minute metering, no per-test charges, no surprise bill because your suite grew. Add agents when you want more parallelism; that's the whole model.

Try it​

Sign up, paste your first test in plain English, and watch it run in a real cloud browser — you'll be looking at results in about a minute.

Prefer to see it first? Watch the 60-second demo on the Cloud Agent page.

No. Cloud Agents run on fully managed, ephemeral infrastructure. You sign up, write test cases in plain English, and execute them — no local grid, no browser drivers, and no CI configuration required.

DevAssure​