---
site: steel.dev
collection: docs
canonical_url: https://steel.dev/docs/production/checklist
markdown_url: https://steel.dev/docs/production/checklist.md
content_signal: ai-input=yes, ai-train=yes, search=yes
title: Prepare for production
description: "Check these items before you send real traffic through Steel: keys, timeouts, retries, limits, cost, security, and monitoring."
summary: "Check these items before you send real traffic through Steel: keys, timeouts, retries, limits, cost, security, and monitoring."
type: how-to
reviewed: 2026-11-12
prerequisites:
  - https://steel.dev/docs/production/projects-and-namespaces.md
related:
  - https://steel.dev/docs/production/run-sessions-at-scale.md
  - https://steel.dev/docs/production/make-sessions-faster-and-cheaper.md
  - https://steel.dev/docs/production/session-cost.md
  - https://steel.dev/docs/production/track-cost-per-customer.md
  - https://steel.dev/docs/production/projects-and-namespaces.md
agent_setup: https://setup.steel.dev/install.md
docs_index: https://steel.dev/docs/sitemap.md
---

# Prepare for production

Check your keys, timeouts, retries, limits, cost, security and monitoring before you send real traffic through Steel. These are the parts of an integration that usually go wrong when it moves from a test to real traffic. Go through the items before you go live, and again before a large increase in traffic. Most items link to the page that shows how.

## Keys and projects

- **Use one project for each environment.** Give development, staging and production each their own project and project key, so that a test key cannot reach production sessions. All projects in the organization share the concurrent session limit. See [Projects](https://steel.dev/docs/account/projects).
- **Keep keys out of the code.** Read the key from `STEEL_API_KEY` or a secret store, and never send it to a browser or a mobile app. See [API keys](https://steel.dev/docs/account/api-keys).

## Timeouts and release

- **Release every session.** Call `release` in a `finally` block, so that a session also ends when the task fails. Browser time counts until the session ends. See [Create a session](https://steel.dev/docs/sessions) and [Pricing](https://steel.dev/docs/platform/pricing).
- **Set `timeout` for the task.** A session cannot get more time after it starts. [Set timeouts](https://steel.dev/docs/sessions/timeouts) has the default and the limits.
- **Set `inactivityTimeout`.** Steel then releases a session when the code that drives it stops, for example after a crash, so a stopped worker costs minutes instead of the full timeout. Leave room for model calls and for people who work in the live view. See [Set timeouts](https://steel.dev/docs/sessions/timeouts).
- **Sweep for sessions that were left live.** Tag sessions with metadata, and release a job's live sessions when the job ends. See [Run sessions at scale](https://steel.dev/docs/production/run-sessions-at-scale#always-release-sessions).

## Retries

- **Retry only the errors that say they are retryable.** Most API errors have `retryable`, and some have `retryAfterSeconds`. The Steel SDK retries these errors for you. See [Run sessions at scale](https://steel.dev/docs/production/run-sessions-at-scale#retry-safely) and [Errors](https://steel.dev/docs/reference/errors).
- **Send an `Idempotency-Key` with Commands requests.** A retry with the same key returns the stored result and does not run the commands again. From version 0.23.0, the Steel SDK sends a key for you and keeps it across its retries. See [Commands](https://steel.dev/docs/control/commands).
- **Check before you repeat a step that has an effect.** A form that orders or pays may have gone through even when your code saw an error. Check the result on the site before you try again.

## Limits

- **Stay under your concurrent session limit.** Queue tasks in your own code, and run fewer workers than your limit. See [Limits](https://steel.dev/docs/platform/limits) and [Know your limits](https://steel.dev/docs/production/run-sessions-at-scale#know-your-limits).
- **Stay under your rate limits.** A `429` response with the code `rate_limited` means that you created too many sessions in a minute, or sent too many Quick action requests. Wait for the time in the `Retry-After` header. See [Limits](https://steel.dev/docs/platform/limits#rate-limits).
- **Check your plan's session length.** Split a task that needs more time than your plan allows into shorter sessions, or move to a plan with longer sessions. See [Limits](https://steel.dev/docs/platform/limits).

## Cost

- **Cut the bandwidth that your pages use.** With Steel proxies, you pay for the bandwidth that a session uses. Steel blocks ads by default. Block the images and media that the task does not need as well. See [Reduce bandwidth](https://steel.dev/docs/sessions/bandwidth).
- **Keep the balance up, and set a spending limit.** When the balance runs out, new sessions fail with `402` and `insufficient_funds`. When the organization reaches its monthly spending limit, they fail with `402` and `budget_exceeded`. Neither error is retryable, so alert on both. See [Billing and usage](https://steel.dev/docs/platform/billing-and-usage).
- **Measure cost by customer or by job.** Tag sessions with metadata and read each session's cost. See [Track cost per customer](https://steel.dev/docs/production/track-cost-per-customer).

## Security

- **Treat page content as untrusted input.** A page can hold text that tries to give your agent instructions. Do not let page content decide which tools the agent may use or where it sends data.
- **Let Steel hold the credentials that your agent uses.** Stored credentials fill the sign-in form inside the session, so the password does not pass through your code or the model. See [Credentials](https://steel.dev/docs/logins/credentials).
- **Protect the live view URL.** Anyone with a session's `debugUrl` can watch the session, and can control it while the view is interactive. Send it only to users that your app has checked. See [Embed a live browser in your app](https://steel.dev/docs/observability/embed-a-live-browser).
- **Protect saved state.** A session context holds a signed-in account's cookies. Store it like a password. See [Session context](https://steel.dev/docs/logins/session-context).
- **Keep secrets out of metadata.** Steel shows metadata in the dashboard. See [Add metadata](https://steel.dev/docs/sessions/metadata).
- **Review how Steel handles your data.** See [Security and compliance](https://steel.dev/docs/platform/security-and-compliance).

## Observability

- **Log the session ID with each job.** With the ID, you can find any run's recording, logs and cost. See [Debug a failed session](https://steel.dev/docs/observability/debug-a-failed-session).
- **Watch signals.** Count the sessions with `bot_detection_triggered`, `captcha_encountered` or `proxy_connection_failed` for each job, and alert when the count rises. See [Signals](https://steel.dev/docs/observability/signals).
- **Find failed and crashed sessions.** List sessions with `status` set to `failed` to find the ones whose browser did not start. A crash can end a session as `released`, so filter by `releaseReason` to find the runs that crashed (`browser_crashed`) or ran out of time (`timeout`). See [Debug a failed session](https://steel.dev/docs/observability/debug-a-failed-session).
- **Watch session cost.** Read each session's cost after release, to find the jobs that cost the most. See [Session cost](https://steel.dev/docs/production/session-cost).

## Next steps

- [Run sessions at scale](https://steel.dev/docs/production/run-sessions-at-scale): Queue work behind your concurrency limit, and retry and release sessions safely.
- [Make sessions faster and cheaper](https://steel.dev/docs/production/make-sessions-faster-and-cheaper): Release sessions on time, load less, and turn on paid features only where they help.
- [Debug a failed session](https://steel.dev/docs/observability/debug-a-failed-session): Find out why a session failed, starting from its ID.
- [Support](https://steel.dev/docs/support): Learn where to ask for help, and what to send with each question.
