---
site: steel.dev
collection: docs
canonical_url: https://steel.dev/docs/get-started/about-steel
markdown_url: https://steel.dev/docs/get-started/about-steel.md
content_signal: ai-input=yes, ai-train=yes, search=yes
title: About Steel
description: Learn how the Steel API, sessions and connections fit together, from the request that creates a browser to the recording that it leaves.
summary: Learn how the Steel API, sessions and connections fit together, from the request that creates a browser to the recording that it leaves.
type: concept
reviewed: 2026-11-12
prerequisites: []
related:
  - https://steel.dev/docs/get-started/agent-setup.md
  - https://steel.dev/docs/get-started/code.md
  - https://steel.dev/docs/get-started/build-your-first-steel-automation.md
agent_setup: https://setup.steel.dev/install.md
docs_index: https://steel.dev/docs/sitemap.md
---

# About Steel

Steel runs browsers in the cloud and gives you an API to create, control, watch and release them. Each browser is a session. Your code or agent decides what the browser does. Steel runs the machine, browser, connection and live view, and keeps each run's records.

## The parts

```text nocopy
 your code or agent
   |
   |  HTTPS to api.steel.dev: create, Commands, Quick actions, release
   |  WebSocket to connect.steel.dev: CDP for Playwright and Puppeteer
   v
 session: one browser in its own virtual machine  ----->  the web
   |
   +-- live view: the session viewer, while the session runs
   +-- after it ends: recording, logs, agent traces, signals, files
```

| Part | What it is |
| - | - |
| API | The HTTP API at `https://api.steel.dev`. Every request carries your API key in the `steel-api-key` header. The Steel SDK, the Steel CLI and the MCP server all call it. |
| Session | One browser that Steel runs for you. It has an `id`, a status and a timeout. |
| Connection | The way your code drives the browser: over CDP with Playwright or Puppeteer, or over HTTP with Commands or Computer actions. [Control interfaces](https://steel.dev/docs/control) compares them. |
| Live view | The browser in real time: in the Steel dashboard at `sessionViewerUrl`, or by itself at `debugUrl`, which you can embed in your app. [Live view](https://steel.dev/docs/observability/live-view) shows both. |
| Recording | A video of the session that you can replay after it ends. |

## What happens when you create a session

You send `POST /v1/sessions`, or call `sessions.create` in the SDK. The request can set [options](https://steel.dev/docs/sessions/configuration) such as the timeout, a proxy or a profile. Steel starts a browser with those options and returns the session.

The response holds what you need to use the session:

- `id`: the session's ID. Steel generates it.
- `status`: `live` once the browser runs.
- `websocketUrl`: the CDP URL for Playwright or Puppeteer.
- `sessionViewerUrl`: the session viewer in the Steel dashboard.

From then on, the session runs until you release it or a timeout ends it. [Session lifecycle](https://steel.dev/docs/sessions/lifecycle) explains how a session ends.

Each live session counts toward the number of concurrent sessions that your plan allows. [Limits](https://steel.dev/docs/platform/limits) has the number for each plan.

## Sessions are isolated

Each session is one browser in its own virtual machine. Two sessions share no cookies or storage. To start a session with an earlier session's state, load a profile or a session context. [Browser state](https://steel.dev/docs/logins/browser-state) compares the ways to do it.

## What a session leaves behind

When a session ends, the browser stops, but Steel keeps the run's records:

| Record | What it holds |
| - | - |
| [Recording](https://steel.dev/docs/observability/recordings) | The session's screen, to replay. Sessions record by default. Set `recording` to `false` to turn it off. |
| [Logs](https://steel.dev/docs/observability/logs) | The session's browser events. |
| [Agent traces](https://steel.dev/docs/observability/agent-traces) | A timeline of the clicks, typing, scrolls and navigations in the session. |
| [Signals](https://steel.dev/docs/observability/signals) | Labels for events that Steel saw, such as a CAPTCHA or a bot block. Steel adds them a few seconds after the session ends. |
| [Files](https://steel.dev/docs/sessions/files) | The files that you uploaded to the session and the files that it downloaded. |
| [Session cost](https://steel.dev/docs/production/session-cost) | The session's final cost, once it is released. |

If the session saved a [profile](https://steel.dev/docs/logins/profiles), the profile also stays, for the next session to load.

Steel keeps a session's records for your data retention period. [Data retention](https://steel.dev/docs/platform/limits#data-retention) has the period for each plan.
