Selenium WebDriver is the durable standard for controlling browsers locally or on remote machines. It has broad language support, a large ecosystem, and years of production use. OpenAdapt does not replace that browser-control layer. It adds demonstration-based compilation, cross-surface execution, and a governed result contract for repeated business work.
The companion article traces the maintenance and failure costs in more detail. Read the comparison article.
Every claim below names its public source. If a vendor doesn't publish a figure, we don't invent one.
OpenAdapt
A compiled workflow replays from retained evidence, re-resolves within its contract, proposes a governed repair, or halts.
Selenium
WebDriver runs explicit commands against selected elements. Changed locators or page behavior require waits, fallback logic, or code maintenance by the owner.
Source: Selenium WebDriver · OpenAdapt method
OpenAdapt
The MIT local runtime has no per-run license fee, and healthy compiled replay makes no model call.
Selenium
Selenium is open source and a normal WebDriver run makes no model call. Browser fleet, grid, and maintenance costs depend on the deployment.
Source: Selenium project · OpenAdapt MIT license · OpenAdapt method
OpenAdapt
An independent verifier can check the system of record before a consequential run returns VERIFIED, through whichever channel that system exposes: a read-only API, a database query, a file check, a second session, or reacquiring the persisted state.
Selenium
WebDriver returns browser command results. The automation author must add page assertions or a separate API, database, file, or service check for the business effect.
Source: Selenium WebDriver commands · OpenAdapt effect-verifier kit
OpenAdapt
The workflow refuses before actuation when identity, target, or policy checks fail. If delivery may have occurred but the effect cannot be proved, it returns RECONCILIATION_REQUIRED without a blind retry.
Selenium
Selenium supports explicit and implicit waits, then raises errors when conditions or commands fail. Retry, rollback, and reconciliation rules live in the surrounding test or application code.
Source: Selenium waits · OpenAdapt execution outcomes
OpenAdapt
Recordings, compiled bundles, and run evidence can remain on customer-controlled infrastructure.
Selenium
WebDriver can run locally or through a remote endpoint. The operator controls whether screenshots and browser data stay local or travel to a grid service.
OpenAdapt
The runtime covers browser, native desktop, and customer-qualified remote-window workflows, subject to the exact published qualification evidence.
Selenium
Selenium WebDriver drives major browsers locally or remotely. It does not provide native desktop or remote-window GUI automation.
Source: Selenium WebDriver · OpenAdapt qualification evidence
Source: W3C WebDriver Recommendation
Source: Selenium Grid
Source: Selenium downloads
Recording demonstrations, visual targeting, virtual desktop awareness, and selector repair are common. OpenAdapt binds independent effect verification and explicit outcomes to the workflow contract.
A run is judged by an out-of-band check of the system of record, such as a read-only API call, a SQL query, or re-reading the persisted record, not by the acting session declaring itself successful.
Every consequential run ends with a typed outcome and a preserved run report. VERIFIED requires independent proof. A refusal before actuation and uncertain delivery after possible actuation remain distinct, so an unconfirmed write cannot appear as success.
A compiled workflow replays deterministically with zero model calls on healthy runs. Model spend is reserved for compilation and reviewable repair.
For managed Citrix, RDP, and VDI estates, OpenAdapt can drive the local client window from outside the session, so nothing is installed inside the remote environment. The lane is qualified today against a deterministic stand-in and a real FreeRDP round trip; a real ICA/HDX environment is qualified per customer before consequential use.
Recordings, screenshots, and compiled bundles can stay inside your boundary. Local, self-hosted, and customer-controlled deployments are first-class, not an enterprise afterthought.
The compiler and governed runtime are MIT-licensed and inspectable. You can audit exactly what runs beside your systems of record.
Each execution surface ships with bounded, published acceptance evidence, counted effects, refusals, and halts, instead of an unbounded compatibility claim.
Per-surface acceptance results are published in the qualification evidence.
No. Selenium remains a strong browser-control layer. OpenAdapt adds demonstration-based authoring, cross-surface replay, independent effect verification, and explicit halt behavior.
Choose Selenium when you need standards-based browser control, already operate a Selenium fleet, or want explicit code and assertions for a web-only workflow.
Choose OpenAdapt when the job must be authored by demonstration, continue into desktop or remote applications, or finish only after an independent verifier proves the intended business effect.
A well-owned Selenium workflow should stay in place. OpenAdapt earns its keep when the work is broader than browser control or the missing parts are qualification, effect verification, and safe halting.
Bring one repeated, consequential workflow and measure authoring time, run time, intervention rate, and incorrect-success rate against your current approach. Or watch the governed-execution demo first. It shows result checks and safe stops against the retained event evidence.