How Cantero Madera works

A profile is a persistent browser identity

Each Cantero Madera profile has its own app-owned Chrome user-data directory, proxy snapshot, browser persona, lifecycle state, run history, and—when supplied—billing and Amazon account secrets. Opening a profile starts a normal, visible Google Chrome Stable window with that persistent data.

Do not open the same profile through another Chrome process or manipulate its data directory while Cantero Madera is using it.

Catalog entries are templates

Proxies and Billing Profiles are reusable catalogs. Creating a profile causes Cantero Madera to validate the selected entries and copy them into profile-owned storage.

After that point:

• editing a saved proxy or Billing Profile affects only profiles created later;
• deleting an unassigned catalog entry does not alter existing profile snapshots; and
• secrets are not read back into the renderer for viewing or prefilling.

This is called snapshot-on-creation behavior.

Proxy protection has a defined boundary

Cantero Madera uses one profile-specific loopback broker and starts Chrome with the assigned proxy. The app validates the proxy and blocks duplicate sticky exit IPs among active profiles.

This is app-level enforcement for managed Chrome. It is not a VPN, operating-system network sandbox, or protection for unrelated applications on the computer.

Automation is serialized per profile

Only one browser authority controls a profile at a time. Interactive browser actions can be blocked while that profile has queued or running automation. The application may operate up to two eligible automation runs at once across different profiles; other work waits in the queue.