Skip to main content
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.
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.

Architecture

What the diagram means


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 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


Outbound connectivity

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

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