Real Chrome. Real macOS. Real Apple hardware. Mac sessions are now GA on Anchor.

Today, Mac sessions are generally available on Anchor Browser. Each Mac session runs Anchor’s hardened Chrome on dedicated Apple hardware: macOS on a Mac Mini, with its own GPU and display. It is delivered through the same API our customers already use.

Anchor’s Linux sessions already present as macOS. Our patched Chrome reproduces a Mac’s platform, GPU, fonts and screen characteristics. For most workloads, that remains the fastest and most scalable way to run browser agents. Mac sessions are for the workloads where an accurate presentation is not enough and the environment itself has to be real.

From Mac presentation to Mac hardware

A Mac session keeps the browser and replaces the machine underneath it. On Linux, Anchor’s patches supply the Mac presentation. On a Mac session, every signal a site can observe originates from genuine Apple hardware.

After a beta period, Mac sessions are generally available starting today, with access enabled by the Anchor team. Linux sessions remain the default for high-volume, latency-sensitive workloads. Mac sessions extend the platform to the workflows that require more.

Built for the workflows that fail everywhere else

Detection systems increasingly evaluate the environment around the browser, not only the browser itself. When the environment does not hold up, the failures follow a consistent pattern:

  • Authentication that succeeds locally and fails in production
  • Verification challenges that appear only on automated runs
  • Intermittent failures concentrated on the highest-value accounts

Mac sessions are built for the workflows where those failures cost the most:

Financial and account portals. Banking, payments, and benefits portals often evaluate the full device environment at login, not only the browser. An agent that signs in on behalf of users needs that environment to hold up on every attempt, because a failed login can mean a locked account or another round of verification.

High-value, low-tolerance accounts. Some workflows run against a small number of accounts that matter a great deal. A success rate that is acceptable at scale is not acceptable when a single failure blocks a customer or breaks a business process. Running on real hardware removes one of the variables behind those intermittent failures.

Workflows that require macOS itself. Some applications and portals are built for, supported on, or behave differently on macOS. For these workflows, the requirement is not only passing detection. The agent needs a real Mac environment to complete the task as a user would.

In each of these, the agent and the model can be working exactly as intended. The constraint is the machine beneath the browser.

An infrastructure problem, not a hardware purchase

Running Chrome on a single Mac Mini is straightforward. Delivering Mac sessions reliably, at scale, for production agents is a different problem. It has two parts.

Operating a fleet. Every machine must stay awake, stay updated, and stay fully isolated between sessions and between customers. Desktop hardware sleeps, hangs, fills its disk, and changes behavior after OS updates. Each of those failures has to be caught and handled before it reaches a customer’s agent. Capacity has to be planned ahead, because physical hardware cannot be provisioned in seconds. All of this has to run around the clock.

Running Anchor’s browser. Our stealth capabilities are compiled into Anchor’s Chrome binary. They cannot be enabled through configuration on stock Chrome. Every new Chrome release requires recompiling those patches and revalidating the browser end to end.

Mac sessions deliver both parts as a single managed service: Anchor’s browser, on hardware Anchor operates.

How it works

Mac sessions run on the same Anchor API and the same CDP connection as every other Anchor session. Existing agent code runs unmodified.

Full details are in the Mac sessions documentation.

The full Anchor platform carries over:

  • Live view and AI-powered browser tasks
  • Persistent browser profiles
  • Residential proxies and sticky IPs
  • The stealth capabilities compiled into Anchor’s Chrome

Availability

Mac sessions are available today. Access is enabled per account by the Anchor team.

To get access, talk to our sales team via this scheduling link.

Bring the workflows that keep failing in cloud environments. We will assess whether Mac sessions are the right fit and enable access for your team.

Real hardware. Cloud simplicity.

Watch the launch video here.

Recent articles

See all
No posts found

Stay ahead in browser automation

We respect your inbox. Privacy policy

Welcome aboard! Thanks for signing up
Oops! Something went wrong while submitting the form.