Skip to main content
Anchor Browser supports on-premise deployment for organizations that require full control over their browser infrastructure. Choose from three deployment options based on your security, compliance, and operational requirements.

Deployment options

Self-hosted

Full Anchor deployment on your AWS infrastructure

Containerized

Deploy on your end customer’s premise

Browser container only

Run Anchor’s browser container on your own infrastructure

Option 1: Self-hosted on your premise

Deploy the complete Anchor Browser platform on your own AWS infrastructure using CloudFormation or role-based access.

What gets deployed

The deployment provisions the following resources in your AWS account:
  • EKS cluster — Manages browser container orchestration and scaling
  • Database instance — Stores task definitions, session metadata, and configuration
  • S3 bucket — Handles file storage for session recordings and artifacts
  • Secrets Manager — Securely stores credentials and API keys

Deployment methods

Deploy using a CloudFormation template that provisions all required resources automatically.

SDK usage

Once deployed, point your SDK to the on-premise endpoint:

Option 2: Containerized deployment on your end customer’s premise

Deploy the full Anchor Browser platform on your end customer’s infrastructure. This option uses the same deployment method as Option 1 — AWS CloudFormation or role-based access — but targets your customer’s AWS account.

What gets deployed

Identical to Option 1, the deployment creates:
  • EKS cluster for browser orchestration
  • Database instance for metadata and configuration
  • S3 bucket for file storage
  • Secrets Manager for credential management

How it works

1

Prepare the customer environment

Ensure the customer’s AWS account meets the minimum requirements (VPC, subnets, IAM permissions).
2

Deploy via CloudFormation or role-based access

Use either deployment method to provision resources in the customer’s account.
3

Configure network access

Set up VPC peering or private endpoints to connect your application layer to the customer’s Anchor deployment.
4

Validate the deployment

Verify the deployment is operational using the health check endpoint.

Option 3: Browser container only

Deploy Anchor’s browser container on infrastructure you manage, while keeping the management layer separate. This is the most flexible option — you control where and how browser sessions run.
With this option, the Anchor management plane is not deployed on your infrastructure. You define browser tasks using custom scripts or direct requests to the browser’s agent.

Use cases

  • You have existing orchestration infrastructure and want to add Anchor’s browser capabilities
  • You need to deploy browser containers on non-AWS infrastructure
  • You want to run browser tasks on a customer’s premise without deploying the full platform

Task definition methods

Choose how you define and execute browser tasks:
Write Playwright scripts that connect to the Anchor browser container directly.
Send task instructions directly to the Anchor browser agent via its API.
Build and test your automation on the Anchor platform, then export and deploy the task to the customer’s premise.

Container deployment

Deploy the Anchor browser container using Docker or Kubernetes:

Comparison

Get started

Contact the Anchor team at support@anchorbrowser.io to discuss which deployment option fits your requirements and to receive access to deployment templates.