# Steel

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 open source and self-hosted, installable on Unraid.

Canonical page: https://ourlocalhost.com/app/3345/steel

## Description

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.

## Health score

78/100 (Good), based on 3 of 4 factors.
- Maintained: 100 (last commit 0 days ago)
- Popular: 78 (7,999 GitHub stars)
- Easy to install: 35 (1 install platform, install notes, Docker image)

## Links

- Official website: https://steel.dev/
- Unraid: https://ca.unraid.net/apps/steel-1e2ac841v26b7s?q=Steel
- GitHub: https://github.com/steel-dev/steel-browser
- Documentation: https://docs.steel.dev/

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/3345/steel), the self-hosted and open-source app directory.
