Open-source browser API for AI agents and applications that need live browser automation.
Launch in your Sealos workspace.
Start with the resources defined by the Steel Browser template. Review CPU, memory, persistent storage, and network allocations for every service in Canvas. Capacity needs depend on your data and workload; monitor usage as they grow.
Template configuration and setupUse the application URL or connection details shown in Canvas. Follow the deployment guide for first-time account setup or client configuration, and keep generated credentials available for that step.
Sealos monthly plans include compute, memory, storage, and traffic. Size your plan for all deployed services. Software licenses and external AI or API services may have separate terms and charges. Confirm the applicable plan and optional charges in Cost Center.
Compare Sealos resource plansFor current cloud charges, refer to Sealos plan pricing. Upstream documentation may reference earlier billing models.
Steel Browser is an open-source browser API for AI agents and applications. This template deploys the combined Steel Browser API and UI container on Sealos Cloud with persistent browser file and cache storage.
Steel Browser exposes a REST API, Swagger documentation, a session debugging UI, and Chrome DevTools Protocol connectivity for browser automation. The template runs the official combined image so the API and web UI are served from one workload.
Sealos provisions HTTPS ingress, persistent volumes for generated files and browser cache data, and a public URL automatically. The browser debugger port stays internal to the Kubernetes service boundary.
The Sealos template includes the Steel Browser runtime container, persistent volumes, internal service discovery, and HTTPS ingress.
Architecture Components:
ghcr.io/steel-dev/steel-browser image digest from the template. The workload keeps the official 4 GB memory recommendation available as the container limit because each session starts a real Chromium runtime./files./app/.cache.3000 with Sealos-managed TLS.Configuration:
The public endpoint serves the UI at /ui, the health response at the generated Sealos base URL, API session metadata under /v1/sessions, and Swagger documentation at /documentation/. The container also exposes an internal debugger port, while user traffic goes through the HTTPS ingress.
The template sets SKIP_FINGERPRINT_INJECTION=true by default. This keeps self-hosted Sealos sessions reliable when the upstream fingerprint generator cannot produce a matching desktop Chrome fingerprint for the bundled browser runtime. Session creation, screenshots, PDF export, and automation APIs continue to work with the browser's native fingerprint.
License Information:
Steel Browser is licensed under the Apache License 2.0.
Sealos is an AI-assisted Cloud Operating System built on Kubernetes that unifies the entire application lifecycle, from development in cloud IDEs to production deployment and management. It is perfect for building and scaling modern AI applications, SaaS platforms, and complex microservice architectures. By deploying Steel Browser on Sealos, you get:
Deploy Steel Browser on Sealos and focus on agent workflows instead of browser infrastructure.
/ui on the generated URL.baseURL./documentation/ on the generated URL, or use the upstream API reference.Steel Browser does not require an initial admin account. API clients can connect to the generated Sealos URL as the baseURL. For public deployments, put Steel Browser behind an authentication layer such as a private network, gateway, or authenticated reverse proxy before sharing the endpoint with other users. Fingerprint injection is disabled by default for reliable self-hosted browser startup; advanced users can re-enable it from the StatefulSet environment variables after confirming their target image supports the requested fingerprint profile.
Steel Browser is stateful because browser sessions and file outputs use local persistent volumes. Start with one replica and increase CPU, memory, or volume size as session concurrency and generated artifacts grow.
SKIP_FINGERPRINT_INJECTION=true, then create sessions through the API or UI.This Sealos template is provided under the Apache License 2.0. Steel Browser itself is licensed under the Apache License 2.0.
A shorter path from an app you want to an app you can run. Sealos brings deployment and ongoing operations into one place.
Start with a ready-made template. Review its configuration and launch from the Sealos console.
Run on managed infrastructure with built-in workload scheduling and recovery.
Give your application a public HTTPS endpoint with certificates managed for you.
Keep application data on persistent volumes across container restarts.
Adjust CPU, memory, and replicas from the console as your workload changes.
Sealos provisions the resources defined by your template and brings them together in your workspace.
Container workloads with configurable CPU, memory, and replicas.
An address for your app, with managed TLS certificates.
A database provisioned alongside your app when the template calls for one.
Storage for the files and data your application needs to keep.
Application settings and secrets configured in one place.
Inspect container logs and resource usage from the console.
Resources and their configuration vary by template. Review the deployment form for this app’s exact setup.
Explore more production-ready templates.
Build production-ready ai templates with Sealos.
Open Design is a local-first, open-source AI design workspace for generating prototypes, decks, images, videos, and design-system-driven artifacts.
Build production-ready ai templates with Sealos.
Host OpenClaw's AI agent gateway on Sealos with a browser control panel, token authentication, and persistent storage for configuration and workspaces.
Build production-ready ai templates with Sealos.
Open-source AI model gateway compatible with the OpenAI API, with multi-provider routing, quota management, channel orchestration, and an admin dashboard.