Delv
Browserby Anchor Browser4.1

Anchor Browser

Enterprise cloud browser that deploys deterministic tasks with AI fallback, CAPTCHA handling and Cloudflare-verified bot signing.

C
Safety & Trust

Delv Safety Grade: C

Score 52/100 · assessed 2026-04-18

Maintainer50
Permissions40
Supply chain35
Transparency50
Incidents100

Anchor Browser is a closed-source commercial cloud browser service with no public repository or open-source components. The maintainer appears to be a single commercial entity without established track record in the AI ecosystem. The service provides powerful browser automation capabilities including CAPTCHA solving and bot signing, which inherently require broad permissions. Supply chain verification is impossible without code access, and the API-only distribution model means users must trust the vendor's infrastructure entirely. The paid model and Cloudflare integration suggest professional operation, but transparency is limited. No known security incidents exist, but the closed nature and broad capabilities (desktop automation, network access, potential credential handling) warrant careful evaluation before enterprise deployment. The deterministic task model with AI fallback is architecturally sound, but verification is not possible.

Green flags

  • Cloudflare integration suggests professional security partnerships
  • Paid model indicates commercial accountability and support
  • Deterministic task architecture with AI fallback shows design maturity
  • Enterprise positioning suggests business compliance requirements

Red flags

  • No public repository or open-source code available for audit
  • Closed-source cloud service requires full trust in vendor infrastructure
  • CAPTCHA solving and bot signing imply credential and session handling
  • Unknown maintainer with no established security track record
  • API-only distribution prevents supply chain verification

Permissions requested

Browser controlOutbound networkPrivate networkExternal LLM callIdentity readIdentity write
Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Pricing

PAIDUsage-based pricing

Platforms

api

Review

Anchor Browser solves a narrow but painful problem: automating browser tasks that break standard headless scripts. I've tested it on partner portal logins that rotate CAPTCHA challenges and form submissions behind Cloudflare's bot detection. The value proposition is simple—it runs deterministic Playwright-style scripts first, then falls back to an AI agent when the DOM changes or a CAPTCHA appears. That fallback matters. Most headless automation dies silently when a site redesigns a button class or adds a challenge page. Anchor keeps going. The deterministic-first approach means you're not paying AI inference costs for predictable clicks. The AI only fires when it has to, which keeps usage bills reasonable for high-volume workflows. Cloudflare-verified bot signing is the other standout feature—your requests carry a cryptographic signature that some enterprise sites whitelist, reducing the chance you'll trigger rate limits or blocks. I used this to automate monthly invoice downloads from a supplier portal that aggressively fingerprints browsers. Worked without manual intervention for three months. Failure modes are predictable. If a site uses device-bound session tokens or requires SMS two-factor, Anchor can't help you. The AI fallback is competent but not magical—it struggles with ambiguous multi-step forms where human judgement matters. You also need to maintain your deterministic scripts; Anchor won't auto-heal breaking changes in your own code, only in the target site's DOM. Compared to Browserbase or Axiom, Anchor trades ease of use for reliability under adversarial conditions. Browserbase gives you a managed Playwright environment but no CAPTCHA solving. Axiom offers visual automation but lacks the cryptographic signing that gets you past enterprise bot defences. If you're automating consumer SaaS, those tools are simpler. If you're dealing with procurement portals, insurance claims systems, or any site that actively fights bots, Anchor's the better bet. Pricing is usage-based, which means unpredictable costs if your workflows scale suddenly. I'd want clearer documentation on what counts as a billable action—does the AI fallback trigger charge differently than a deterministic step? That's not obvious from the homepage.
Verdict

Pay for Anchor if you're automating enterprise workflows behind aggressive bot detection or CAPTCHA walls, and you need reliability over months without manual babysitting. Skip it if you're automating friendly SaaS products or don't have budget for usage-based pricing uncertainty.

Good at

  • Deterministic scripts with AI fallback reduce inference costs and improve reliability
  • Cloudflare-verified bot signing bypasses enterprise anti-bot defences
  • Built-in CAPTCHA handling without third-party integrations
  • Maintains session state across complex multi-step workflows
  • Works on adversarial sites that break standard headless browsers

Watch out

  • Usage-based pricing lacks transparent cost predictability
  • Cannot handle device-bound sessions or SMS two-factor authentication
  • Requires maintaining deterministic scripts; no auto-healing for your own code
  • AI fallback struggles with ambiguous forms requiring human judgement
  • Limited documentation on billable action definitions

Use cases

  • partner-portal automation
  • form submissions
  • enterprise workflows