Tools that can't update themselves
UFT, TestComplete, Katalon, Robot Framework and internal harnesses look for the driver at a fixed path and fail when the browser moves ahead on its own.
Selenium updates its own drivers. RPA bots in WebDriver mode, UFT, TestComplete, Katalon, internal harnesses and legacy tools don't. DriverSphere keeps the correct Edge, Chrome and Firefox driver on disk for all of them.
One dashboard, one click, or one .bat file in your pipeline. No scripts to maintain, no packages to install, no admin rights required on the machine.
Edge is treated as a first-class target with exact version locking — not as an afterthought behind Chrome.
The Standalone Edition covers one Windows machine with internet access: workstation, server, VM or cloud instance. The Enterprise Edition, with a central repository and distribution to offline nodes, is in development.
Recent Selenium releases update their own drivers. Everything else that drives a browser — commercial test tools, internal harnesses, legacy applications — still expects the correct binary sitting on disk, and has no way to get one.
UFT, TestComplete, Katalon, Robot Framework and internal harnesses look for the driver at a fixed path and fail when the browser moves ahead on its own.
Locked-down Windows workstations with no package manager, no admin rights and a proxy in the way rule out most of the usual solutions.
The driver is tied to the browser version. When Edge or Chrome update — often on their own, without notice — the driver in use stops working and has to be replaced on every machine that relies on it.
DriverSphere places the correct driver at a fixed path on disk. Anything that reads it works: RPA bots in WebDriver mode, commercial test tools, CI/CD pipelines, internal harnesses, legacy applications.
Every downloaded version stays archived on the machine, together with the browser version it was matched to. You can show which driver was deployed, and when — which matters where that has to be demonstrated.
Generate .bat files for scheduling, CI/CD pipelines, Jenkins jobs and bot-driven runs. The environment check happens as a pre-flight step, so a mismatch fails immediately instead of halfway through a suite.
Standalone covers one Windows machine with internet access and is already in production use. Enterprise — a central repository distributing approved drivers to offline nodes — is being built alongside a small group of early access organisations.
One Windows PC, server, VM or cloud instance with internet access. DriverSphere checks the installed browser version, downloads the matching driver and deploys it to a fixed path.
Direct annual license for one machine. VAT is calculated at checkout.
Want to try it first? Request a free 14-day trial.
Buy NowOne central machine with internet access maintains the repository of approved drivers and distributes them to offline or controlled target machines.
In development. A limited number of organisations are shaping the transfer mechanism, the approval workflow and the licensing model against their own real constraints. Early access places include influence on the roadmap and on launch pricing.
Join Enterprise early accessIf Selenium is your only test automation tool and your machines reach the internet without restriction, Selenium Manager already handles driver resolution, it is built in, and it is free. DriverSphere covers the cases that fall outside it.
Most driver resolvers live inside a single framework. DriverSphere sits outside all of them: it maintains the correct binary at a known path on the Windows machine, and lets every tool on that machine simply use it.