Steel

Steel is an open-source browser API that provides REST control of headless browsers with session management, proxy support, and anti-detection features.

  • AI
  • Cloud
  • Development
  • Other
  • Productivity
  • Tools & Utilities
Steel is an open-source browser API that provides REST control of headless browsers with session management, proxy support, and anti-detection features. It is purpose-built for web automation, scraping, and AI agents that need to interact with the web.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

78/100 Good

Maintained
100last commit 0 days ago
Popular
787,999 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 18 days ago

GitHub stars
7,999
Open issues
89
Last commit
2026-11-21
Latest release
v0.5.5-beta
License
Apache-2.0
Activity
rising

Checked today - source: GitHub (steel-dev/steel-browser)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Copy .env.example to .env and fill keys Before running any Steel example, make a .env file from .env.example and add your STEEL_API_KEY plus the example's AI provider key, like OPENAI_API_KEY or ANTHROPIC_API_KEY. If these are missing or wrong, the example can't reach Steel or the AI model and will error out. source
  • Install Chromium for Playwright examples For examples that use Playwright, run the Playwright Chromium install command shown for that example, such as npx playwright install chromium. This downloads the actual browser the code controls; without it, the browser automation step fails even if the keys are correct. source
  • For Convex, create the dev deployment first In the Convex price-watch example, run npx convex dev on first run to create the Convex dev deployment, then set STEEL_API_KEY in Convex with npx convex env set. Skipping this leaves the app with nowhere to store or send job state, so the example won't work end to end. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I run Steel locally?

The README recommends running the pre-built Docker image. It bundles the API and UI into one local deployment.

Which port serves the self-hosted API documentation?

The local API serves its Swagger UI on port 3000 at the documentation path.

What environment variables are required for the Steel examples?

Copy the example environment file to .env and set STEEL_API_KEY plus the AI provider key needed by the example. Missing or incorrect keys cause the example to fail to reach Steel or the model.

Why do Playwright-based examples fail even when the API keys are correct?

You must install the Playwright Chromium browser for the example, such as with the npx playwright install chromium command. Without that browser, the browser automation step fails.

Answers sourced from docs.steel.dev, docs.steel.dev, github.com

Community

Collected 49 days ago - public community threads