Pricing reference, verified June 16, 2026

CloudCruise pricing: the three tiers, and the one unit that decides whether they apply to you.

The literal answer is below in a callout you can copy into a budget sheet. The part the listing sites skip is what CloudCruise actually meters: browser hours. That single billing unit quietly tells you where the tool can run and where it cannot, which is the number that matters more than the dollar figure if any of your workflow lives in a desktop application.

Matthew Diakonov, Written with AI

Published June 16, 20266 min

Direct answer · verified June 16, 2026 against cloudcruise.com/pricing

Free

$0/mo

3 workflows · 2 browser hours / month

Versioning and rollbacks
Maintenance agent

Self-serve

Starter

$60/mo

Unlimited workflows · 20 browser hours, then $3/hour

Everything in Free
Workspaces and teams
Business associate agreement

Self-serve

Scale

Custom

Volume-discounted browser hours · negotiated

SSO, priority support, private browser instances
Data processing agreement, custom retention, custom SLAs
Implementation support

Demo required

Every tier includes versioning, rollbacks, and a maintenance agent. The variable cost on all of them is browser hours. Source: cloudcruise.com/pricing. Re-check it before you budget; the tier names are stable, the dollar figures are the part most likely to move.

What a “browser hour” costs per minute, and why that number is a trap if you read it alone.

Starter is $60 for 20 browser hours, then $3 per hour after that. Divide the overage rate by 60 and you get the unit cost of a minute of CloudCruise runtime:

CloudCruise Starter overage, per minute of browser runtime

$0/min

$3/hour ÷ 60 = $0.05 per minute. Our arithmetic from the published $3/hour rate, not a CloudCruise-quoted figure.

Five cents a minute is cheap, and on its own it makes CloudCruise look far less expensive than Mediar's $0.75 per minute of runtime. But the two numbers buy different things. A CloudCruise minute is a minute of a cloud browser doing browser work. A Mediar minute is a minute of an agent driving a thick-client Windows desktop application that has no browser and no DOM to point a browser tool at. You cannot run a SAP GUI data-entry step on CloudCruise at any price, because there is no browser session for the meter to count.

So the honest way to use the per-minute figures is as a sizing tool for the parts of your process each tool can actually reach, not as a head-to-head rate war. Take one real workflow, count the minutes spent in a browser tab versus the minutes spent in a desktop window, and price each segment with the tool that runs it.

The billing unit is a scoping test you can run before you sign anything.

Here is the practical move. Before you evaluate CloudCruise on price, evaluate it on whether the meter even ticks for your work. Open the workflow you most want to automate and label every step as one of two kinds: a step that happens inside a browser tab, or a step that happens inside a desktop application window. Add up the time in each bucket.

Mostly browser minutes (logging into a payer portal, downloading a remittance PDF, filling a SaaS form): CloudCruise's browser-hours pricing applies cleanly, and the per-minute math above is real.
Mostly desktop minutes (keying a claim into a desktop SAP B1 screen, posting to an Oracle EBS form, updating a chart in Cerner PowerChart): there are zero browser hours to bill, because CloudCruise cannot open those windows. The pricing question is moot; the reach question is the whole ballgame.
A mix (most real enterprise workflows): you will end up running the browser segments on a browser tool and the desktop segments on a desktop tool, and the combined cost is what you should compare, not either list price in isolation.

This is why the pricing page is more useful than it looks. A vendor that meters browser hours is telling you, in the structure of its invoice, exactly which half of your process it was built for.

Same idea, different surface, different invoice

CloudCruise and Mediar both let an AI author a workflow once and replay it. They bill in different units because they drive different things.

Feature	CloudCruise	Mediar
What the meter counts	Browser hours (time a cloud Chromium session is open)	Runtime minutes (time the agent is actually driving an app)
Published entry price	$0 free tier, $60/mo Starter	$0.75/min runtime, no per-seat licensing
Up-front commitment	None on Free/Starter; Scale is negotiated	$10,000 turn-key program fee that converts to credits
Where it runs	Inside a browser (web apps, payer portals, SaaS forms)	Windows desktop apps via the accessibility tree (SAP GUI, Oracle EBS, Epic, Cerner, Jack Henry, mainframe terminals)
What costs zero because it cannot run there	Any step inside a thick-client desktop window	Any step inside a pure browser tab (use the browser tool for that)

CloudCruise figures verified June 16, 2026 at cloudcruise.com/pricing. Mediar figures from mediar.ai pricing: $0.75/min runtime, $10,000 turn-key program fee converting to credits. Per-minute browser cost ($0.05) is our arithmetic from the published $3/hour overage.

What the desktop minutes are worth when you do automate them.

The reason a $0.75-per-minute desktop runtime can be worth more than a $0.05-per-minute browser runtime is that the desktop minutes are usually the expensive, manual ones nobody else can touch. The clearest example we have is insurance claims intake.

$750K/yr

“Claims intake at one mid-market carrier went from 30 minutes per claim to 2 minutes. That is the AP-team headcount math, not a press-release number.”

Mediar deployment, mid-market insurance carrier

That workflow lives in a desktop claims system, not a browser. No number of browser hours would have automated it, because the data never touches a DOM. When the bottleneck is a thick-client desktop app, the per-minute rate matters far less than whether anything can reach the screen at all, and whether it keeps working when the vendor reshuffles the UI. Mediar drives those screens through the Windows accessibility tree rather than pixel matching, so a moved button or a renamed field does not break the automation the way a brittle selector would.

Priced out a browser tool and found half your workflow is in a desktop app?

Bring one real workflow. We will split it into browser minutes and desktop minutes with you, price the desktop half at $0.75/min, and show you whether the boundary in your stack lines up with ours.

Frequently asked questions

How much does CloudCruise cost?

As of June 16, 2026, cloudcruise.com/pricing lists three tiers. Free is $0/month and includes 3 workflows and 2 browser hours per month. Starter is $60/month with unlimited workflows and 20 browser hours per month, then $3 per browser hour beyond that. Scale is custom pricing and requires a demo request; it adds SSO, private browser instances, a data processing agreement, custom retention, custom SLAs, and implementation support. All tiers include versioning, rollbacks, and a maintenance agent.

What is a 'browser hour' in CloudCruise pricing?

A browser hour is one hour of wall-clock time that a CloudCruise cloud browser session is open and running your workflow. It is the core billing unit on every tier: Free caps you at 2 per month, Starter includes 20 and then bills $3 each, and Scale negotiates a volume rate. The important consequence is that the meter only ticks while a browser is doing the work. A step that opens a desktop application instead of a web page is not a browser hour, because CloudCruise drives the browser, not the Windows desktop.

Is there a free version of CloudCruise?

Yes. The Free tier is $0/month and gives you 3 workflows and 2 browser hours per month, plus versioning, rollbacks, and the maintenance agent. It is enough to prototype a single short browser workflow. Two browser hours per month is roughly four minutes of runtime per day, so it is a trial allowance, not a production budget. The first production tier is Starter at $60/month.

Does CloudCruise charge per workflow or per seat?

Neither, on the published tiers. Free caps the number of workflows at 3, but Starter and Scale make workflows unlimited. There is no per-seat license on the public page. The variable cost is browser hours: $3 per hour on Starter past the included 20, and a negotiated rate on Scale. So your bill scales with how long your automations run in the cloud browser, not with how many people use the account or how many workflows you build.

How does CloudCruise pricing compare to Mediar pricing?

They are priced in different units because they automate different surfaces. CloudCruise bills browser hours ($60/month for 20 hours, then $3/hour, which works out to about $0.05 per browser minute). Mediar bills $0.75 per minute of runtime with no per-seat licensing, plus a $10,000 turn-key program fee that converts to usage credits. Per raw minute CloudCruise is cheaper, but the comparison is not apples to apples: CloudCruise's minutes only exist inside a browser, and Mediar's minutes are spent driving thick-client Windows desktop apps that have no browser to meter. The right question is not which per-minute rate is lower, it is which surface your workflow actually lives on.

When does CloudCruise's pricing not apply to my workflow at all?

When the workflow runs in a desktop application rather than a browser. CloudCruise automates web apps by driving a cloud browser; if your process opens SAP GUI, Oracle EBS, Oracle Forms, Epic Hyperspace, Cerner PowerChart, a Jack Henry or Fiserv or FIS client, or a mainframe terminal, there is no DOM and no browser session to bill. The browser-hours meter never ticks because the tool cannot reach those screens. That is the boundary Mediar sits on the other side of: it reads the Windows UI Automation accessibility tree, the same interface screen readers use, so it can act on controls in any running desktop process.

Is CloudCruise HIPAA compliant, and does that cost extra?

CloudCruise offers a business associate agreement on the Starter tier and above, and a data processing agreement on Scale. A BAA is the contract a covered entity needs before a vendor can handle protected health information, so HIPAA-adjacent use is gated to paid tiers rather than priced as a separate line item. The Free tier does not include a BAA. Mediar is SOC 2 Type II certified and HIPAA compliant and can deploy on-prem or in the cloud, which matters when the desktop app holding the PHI is an EHR like Epic or Cerner.

Where did these CloudCruise prices come from, and how do I re-check them?

Directly from cloudcruise.com/pricing, read on June 16, 2026. Pricing pages change, so open that URL yourself before you budget against these numbers. The tier names (Free, Starter, Scale) and the browser-hours model are the stable part; the dollar figures are the part most likely to move. Scale has never shown a public number; it has always been demo-gated.

Related on CloudCruise and the desktop boundary