Ferrum
Ferrum: A focused, open-source Ruby interface for Chromium automation through CDP. Ranked #59 of 62 in Browser Automation Tools by our editors (3.0/10); pricing: Open source; best for ruby CDP control of Chromium.
At a glance
- Editor score3.0 / 10
- PricingOpen source
- Best forRuby CDP control of Chromium
- Paid fromFree
- Facts checked20 Sep 2026
Where it wins
- Controls Chrome and Chromium through CDP without Selenium or ChromeDriver
- Covers navigation, screenshots, JavaScript, network inspection, and input
- Supports multiple pages, contexts, and thread-safe execution
Where it doesn't
- Supports one browser engine: Chrome and Chromium
- Requires Ruby and a Chromium-based browser environment
- No official paid pricing or hosted execution plan
Our verdict on Ferrum
Ferrum is an open-source Ruby library for controlling Chrome and Chromium through the Chrome DevTools Protocol. It is aimed at developers building browser automation, testing, scraping, screenshots, JavaScript execution, network inspection, and interactive page control. The library runs headless by default and also supports headful operation, while avoiding Selenium, WebDriver, and ChromeDriver. It is distributed as a Ruby gem and can work with Capybara through the related Cuprite driver.
The pricing model is straightforward: Ferrum is open source, with no paid tiers to compare. That makes the product a fit for teams seeking a Ruby-based library they can incorporate into their own environment rather than a hosted browser execution service. Its setup model centers on the Ruby gem and a Chrome or Chromium browser, with CDP providing the control layer. Capybara users also have a related Cuprite path for browser-driven application workflows.
Ferrum’s strongest distinction is the breadth of control available within one engine. Developers can manage pages and browser sessions, take screenshots, evaluate or inject JavaScript, inspect network traffic, intercept requests, automate mouse and keyboard input, and work with multiple pages and contexts. Thread-safe execution extends that control to concurrent Ruby workflows. The trade-off is scope: Ferrum focuses on Chrome and Chromium rather than multiple browser engines. Ruby teams that want direct CDP control of Chromium should choose it; teams requiring broader engine coverage should consider an alternative.
Your product? Our editors can test Ferrum in depth and publish a review, labelled as paid · from $149/mo →
Ferrum pricing
Ferrum fact sheet
| Free plan | Not verified |
|---|---|
| Paid from | Free |
| Browser engines | One |
| Language support | Not verified |
| Cloud execution | Not verified |
| Self-hosted option | Yes |
| Parallel runs | Not verified |
| Monthly run limit | Not verified |
| Deployment | Self-hosted |
| Support | Docs, Community |
| Built for | Solo, Small business, Mid-market, Enterprise (editorial estimate) |
| Pricing | Open source |
| Website | ferrum.rubycdp.com |
| Facts checked | 20 Sep 2026 |
Alternatives to Ferrum
- PlaywrightA free, open-source framework for cross-browser testing, automation, and API checks.9.4
- SeleniumA mature, standards-based choice for cross-browser web automation at no paid-plan cost.9.2
- BrowserStack AutomateA broad browser and real-device testing platform for enterprise QA teams.9.1
Used Ferrum? Be the first to review it
The editor score above is our own research. What this page doesn't have yet is a reader's view — what you used Ferrum for, what worked and what didn't. No stars are seeded and no review is paid for; an editor reads every one before it appears.
Write a reviewTwo minutes · verified accounts only · read by an editor before it appears
Featured on iTechGuides
Ferrum is listed in our Browser Automation Tools directory. Add the badge to your site — it links back to this page.
<a href="https://www.itechguides.com/products/ferrum/"><img src="https://www.itechguides.com/best/badge/ferrum.svg" alt="Featured on iTechGuides" width="230" height="46"></a>
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update