Launch Week v3: everything we shipped
Launch Week v3: everything we shipped
Launch Week v3: everything we shipped
/
/
San Francisco
San Francisco
/
/
Nikola Balic
Nikola Balic
Launch Week v3 is done. Five days, five releases.
Shipping all of it on a tight, self-imposed schedule was not easy. We loved it anyway. By the looks of it, you did too: signups rose 26%, sessions rose 18%, and resurrected organizations rose 28%. Thank you for making our calendar look slightly less unreasonable.
Agents are workloads now. A demo succeeds once. A workload has to succeed on Monday and again on Tuesday, with the same identity, inside the same budget. You see what it spent.
This week shipped those parts.
Stealth Browser, a Chromium built for agents
On Day 1, we shipped Stealth Browser, our fork of Chromium for agents that run the web, not just click through it. The profile loads inside the browser process at startup, before page JavaScript reads navigator, screen, WebGL, fonts, and the rest.
It also cuts stock-Chromium code a headless agent never touches. Available now for enterprise customers on request.
Dedicated IPs, a fixed home for browser agents
On Day 2, we launched Dedicated IPs, a stable network origin for production agents. Lease a stable IP, attach it to a profile, and let the agent return as the same signed-in visitor every run.
They are self-serve on Scale at $5 per IP per month, with custom Enterprise pricing. Reserve up to 25. Pin one to a session, or let Steel write one from your pool to the profile.
Rust and Go SDKs, native clients in four languages
On Day 3, we added native Rust and Go SDKs, so you can drive Steel from the stack your agents already run in. Steel now has native clients alongside TypeScript and Python.
The session flow stays the same: create a session, set profile and proxy options, hand the WebSocket URL to your CDP tool, then release the session from that client. Rust is async-first. Go is context-first.
Atlas, a deep research harness you can own
On Day 4, we open-sourced Atlas, a deep research harness (@steel-dev/atlas) with your models, sources, and domain tools. It runs a research loop, not a single prompt: plan, gather evidence, synthesize, audit, patch gaps, then ground citations.
The ledger sits outside the model's context window. Atlas can use Steel for JS-rendered or login-gated pages. EDGAR, PubMed, arXiv, or internal docs can come in through researchTool.
Find Atlas on GitHub.
Simpler pricing, built for how agents run
On Day 5, we rebuilt pricing for how agents actually run, with metered rates and visible usage. The three plans are Launch ($0 + usage), Scale ($250 + usage), and Enterprise (custom). Launch includes a one-time $30 usage credit. Scale includes $100 each month.
The dashboard shows spend by meter. Existing customers can keep their legacy plan.
What it adds up to
Together they are what an agent needs after the demo: a place to run that does not drift, the same identity each time, a stack you build in, output you check, and cost you can see before the bill lands.
That is the week. Agents run like workloads now, and the way you pay for them matches.
What's next
We are already working on the next set of improvements for agents. If there is a feature, workflow, or rough edge you want us to prioritize, send it our way.
Join us in Discord, tag us on X @steeldotdev, or reply with the feature request you want Steel to build next.
See the full week at steel.dev/launch-week.
Launch Week v3 is done. Five days, five releases.
Shipping all of it on a tight, self-imposed schedule was not easy. We loved it anyway. By the looks of it, you did too: signups rose 26%, sessions rose 18%, and resurrected organizations rose 28%. Thank you for making our calendar look slightly less unreasonable.
Agents are workloads now. A demo succeeds once. A workload has to succeed on Monday and again on Tuesday, with the same identity, inside the same budget. You see what it spent.
This week shipped those parts.
Stealth Browser, a Chromium built for agents
On Day 1, we shipped Stealth Browser, our fork of Chromium for agents that run the web, not just click through it. The profile loads inside the browser process at startup, before page JavaScript reads navigator, screen, WebGL, fonts, and the rest.
It also cuts stock-Chromium code a headless agent never touches. Available now for enterprise customers on request.
Dedicated IPs, a fixed home for browser agents
On Day 2, we launched Dedicated IPs, a stable network origin for production agents. Lease a stable IP, attach it to a profile, and let the agent return as the same signed-in visitor every run.
They are self-serve on Scale at $5 per IP per month, with custom Enterprise pricing. Reserve up to 25. Pin one to a session, or let Steel write one from your pool to the profile.
Rust and Go SDKs, native clients in four languages
On Day 3, we added native Rust and Go SDKs, so you can drive Steel from the stack your agents already run in. Steel now has native clients alongside TypeScript and Python.
The session flow stays the same: create a session, set profile and proxy options, hand the WebSocket URL to your CDP tool, then release the session from that client. Rust is async-first. Go is context-first.
Atlas, a deep research harness you can own
On Day 4, we open-sourced Atlas, a deep research harness (@steel-dev/atlas) with your models, sources, and domain tools. It runs a research loop, not a single prompt: plan, gather evidence, synthesize, audit, patch gaps, then ground citations.
The ledger sits outside the model's context window. Atlas can use Steel for JS-rendered or login-gated pages. EDGAR, PubMed, arXiv, or internal docs can come in through researchTool.
Find Atlas on GitHub.
Simpler pricing, built for how agents run
On Day 5, we rebuilt pricing for how agents actually run, with metered rates and visible usage. The three plans are Launch ($0 + usage), Scale ($250 + usage), and Enterprise (custom). Launch includes a one-time $30 usage credit. Scale includes $100 each month.
The dashboard shows spend by meter. Existing customers can keep their legacy plan.
What it adds up to
Together they are what an agent needs after the demo: a place to run that does not drift, the same identity each time, a stack you build in, output you check, and cost you can see before the bill lands.
That is the week. Agents run like workloads now, and the way you pay for them matches.
What's next
We are already working on the next set of improvements for agents. If there is a feature, workflow, or rough edge you want us to prioritize, send it our way.
Join us in Discord, tag us on X @steeldotdev, or reply with the feature request you want Steel to build next.
See the full week at steel.dev/launch-week.
All Systems Operational