> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anchorbrowser.io/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Anchor Browser is cloud browser infrastructure for AI agents and automation: browser sessions you control over CDP or REST, natural-language web tasks, versioned automation tasks, managed authentication into third-party web apps (identities with MFA), persistent volumes and profiles, recordings, live view, batch sessions, webhooks, and network options including residential proxies, extra stealth, and captcha solving for sites that block standard browsers. AI agents should start at https://docs.anchorbrowser.io/for-agents, then create an API key at https://app.anchorbrowser.io/api-keys. Read the for-agents page before authentication or API calls.

# Container image deployment

> Run Anchor Browser as a container image inside your environment. You own the control plane; Anchor provides and maintains the browser container image.

Deploy the **Anchor Browser container image** on infrastructure you control. In this model:

* **You** provide and operate the control plane: orchestration, scheduling, scaling, networking, secrets, and access.
* **Anchor** provides and maintains the browser container image and related release artifacts.
* **Anchor does not need access to your premises** to install, operate, or update the deployment.
* **Recordings are not available** on the container image deployment, by design.
* **Anchor does not provide logging** for this deployment. The only data sent to Anchor is **usage metering** for billing.

> [!NOTE]
>
> This page covers the container image deployment only. It is delivered as **container images**, not a Helm chart, and it is not the full self-hosted Anchor platform described in [On-premise deployment](https://docs.anchorbrowser.io/advanced/on-premise-deployment).

***

## Architecture

```mermaid theme={null}
flowchart TB
  subgraph CustomerEnv["Customer environment (you operate)"]
    CP["Customer control plane<br/>orchestration · scheduling · scaling<br/>network · secrets · access"]
    IMG["Anchor Browser container image<br/>(runtime only)"]
    SECRETS["Your secrets store"]
    CP -->|starts / stops / configures| IMG
    IMG --> SECRETS
    APP["Your apps / agents<br/>CDP · Playwright · APIs you expose"]
    APP <-->|session traffic you initiate| IMG
  end

  subgraph External["External endpoints (depending on configuration)"]
    S3["Anchor release bucket (S3)<br/>image updates — customer pull"]
    METER["Anchor usage metering<br/>billing totals only"]
    CAPTCHA["Optional: Anchor CAPTCHA solving<br/>(Anchor premises) — toggle on/off"]
    TARGET["Target websites"]
  end

  CP -->|pull / pin / roll out| S3
  IMG -->|usage metering for billing| METER
  IMG -.->|only if CAPTCHA solving is enabled| CAPTCHA
  IMG -->|browsing| TARGET
```

### What the diagram means

| Boundary | Who owns it | What it does |
| - | - | - |
| Customer control plane | **You** | Start and stop sessions, schedule and scale containers, network policy, secrets, access control, upgrades |
| Anchor Browser container image | **Anchor builds, you run** | Browser runtime for your sessions inside your hosts |
| Release artifacts (S3) | **Anchor publishes, you pull** | Versioned images you choose when to adopt |
| Usage metering | **Outbound from you to Anchor** | Billing totals only |
| CAPTCHA solving (optional) | **Anchor premises, when enabled** | Solves challenges when you turn the feature on |
| Recordings and Anchor logging | **Not offered in this model** | No recordings by design, no Anchor logging |
| Premises access | **None required** | No standing Anchor credentials into your environment |

***

## Responsibility split

### You operate the control plane

* Container orchestration (Docker, Kubernetes, or your own scheduler)
* Scaling, scheduling, and capacity planning
* Network policy, egress allowlists, and proxy routing
* Secrets, TLS, and identity for the runtime
* Access control for your operators
* When to pull, pin, stage, and roll out new image versions

### Anchor provides the container image

* The browser container image and related release artifacts
* Regular Chromium and image updates
* Optional CAPTCHA solving hosted on Anchor premises, which you can turn on or off
* Usage metering for billing
* Release distribution via S3, which you pull from

### What Anchor does not do in this model

* Operate a control plane inside your environment
* Offer session recordings
* Provide logging for this deployment
* Require standing VPN, cluster admin, or long-lived credentials into your premises
* Push image updates into your environment

***

## Data flows

### Session data stays with you

Page content, DOM, screenshots, cookies, and credentials remain in **your** environment. No session or application data is sent to Anchor.

### Usage metering

For billing, the runtime sends **usage metering** to Anchor. Metering covers usage totals, such as browser time and traffic volume. It does **not** include page content, screenshots, cookies, credentials, recordings, or logs.

The exact metering fields, cadence, and destination are provided with your deployment package.

### Optional CAPTCHA solving

Anchor can solve CAPTCHAs on **Anchor premises**. The feature is opt-in and can be turned on or off.

* **Off:** no CAPTCHA challenge material leaves your environment.
* **On:** the challenge material needed to solve a CAPTCHA is sent to Anchor for solving. This is a separate data path from usage metering.

Contact [support@anchorbrowser.io](mailto:support@anchorbrowser.io) for details on what is sent and how long it is kept.

***

## Updates via S3

Anchor publishes updated container images to **S3**. You decide when to adopt them:

**1. Get release access**

Anchor gives you access to the S3 release location for your deployment.

**2. Pull the version you want**

You pull images on your schedule. Anchor never pushes into your network.

**3. Mirror (optional)**

Optionally copy the image into your private registry.

**4. Pin and roll out**

Pin, stage, and roll out the version on your own schedule.

Bucket access, verification, and rollback steps are provided with your deployment package.

***

## Access model

| Requirement | Position |
| - | - |
| Standing Anchor access to your premises | **Not required** |
| Inbound connections from Anchor for normal operation | **None** |
| Updates | You **pull** from S3 |
| Support | Works without standing credentials into your environment |

***

## Outbound connectivity

The exact hostnames and ports for each destination are provided with your deployment package, based on the features you enable.

| Destination | Direction | Required? | Purpose | Data carried |
| - | - | - | - | - |
| Anchor S3 release bucket | Outbound (you pull) | For updates | Fetch container images | Release artifacts |
| Anchor usage metering | Outbound | Yes, for billing | Billing totals | Usage totals such as browser time and traffic, **not** page content or logs |
| Anchor CAPTCHA solving | Outbound | Only if CAPTCHA solving is on | Solve challenges | Challenge material only |
| Target websites | Outbound | Yes, for browsing | Your automation | Whatever your sessions do |

***

## Prerequisites

* A container runtime or orchestrator you operate (for example Docker or Kubernetes)
* An egress policy that allows the destinations you enable
* A secrets store for runtime configuration
* Access to the Anchor S3 release location, or a mirror you maintain

Your Anchor contact provides sizing guidance and the supported runtime requirements.

***

## Shared security responsibilities

| Area | Customer | Anchor |
| - | - | - |
| Host and runtime hardening | Yes | — |
| Network allowlists and egress | Yes | Provides the destinations needed for the features you enable |
| Secrets | Yes | — |
| Image pinning, rollout, and rollback | Yes | Publishes releases via S3 |
| Session data residency | Yes, data stays in your environment | Receives usage metering, and CAPTCHA material only if enabled |
| Image vulnerability response | You apply the updates you pull | Ships image updates regularly |
| Premises access | You control any access you grant | No standing access required |
| Recordings and Anchor logging | Not applicable | Not offered on this deployment |

***

## Related

* [On-premise deployment](https://docs.anchorbrowser.io/advanced/on-premise-deployment)
* For deployment packaging and S3 release access, contact [support@anchorbrowser.io](mailto:support@anchorbrowser.io)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.