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

# Network and Identity

> Configure browser identity, networking, and proxy behavior for self-hosted deployments

## Overview

Rusty Browser does not depend on a managed proxy network. Open-source deployments use the network path and infrastructure you configure, which can be a direct connection, your own proxy pool, or a third-party provider you choose.

The browser identity layer is handled by Rusty Browser components such as [rustenium-identity](https://github.com/dashn9/rustenium-identity), while network routing remains under your control.

## Key Capabilities

### Bring Your Own Network

* Run browsers through your host network for local automation
* Route traffic through proxies you operate or contract separately
* Keep network policy, geography, and compliance decisions in your own infrastructure

### Browser Identity

Rusty Browser can apply browser identity and fingerprint settings through its open-source identity layer. The exact profile you use should match your workload, target sites, and compliance requirements.

### Optional Third-Party Services

If your workflow needs residential proxies, captcha solving, or specialized routing, configure those providers explicitly in your deployment. Rusty Browser keeps that network choice under your control.

## How It Works

Every browser created via `PUT /browsers/` runs through the server and agent configuration you provide:

1. `rusty-server` receives the browser request
2. Flux starts or assigns a browser agent
3. The agent launches Chromium with the configured identity and network settings
4. Commands execute against that isolated browser until you close it

This keeps browser automation, networking, and infrastructure ownership in your hands.