We used the solution for automating authenticated workflows across third-party financial portals that do not expose reliable APIs. This included vendor onboarding, KYC/AML document retrieval, payment operations reconciliations, and back office data enrichment. These workflows were turned into production-grade automations that our product and operations teams can depend on.
Browser Automation Agent
Anchor BrowserReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
15 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Modern, Built-In Productivity Features That Keep Work Organized
What do you like best about the product?
I like that most productivity features are built in, so I don’t have to rely on external extensions nearly as much anymore. The browser feels modern without being overcomplicated, and it’s easy to get started. Workspaces are also straightforward to create and manage, which helps me keep things organized.
What do you dislike about the product?
Every so often, a page takes a second longer to load than it does in more mainstream browsers. It doesn’t happen often, but when it does, it’s noticeable.
What problems is the product solving and how is that benefiting you?
I used to rely on several tab-management extensions, but Anchor replaces most of that with its native features. As a result, my workflow feels cleaner, more streamlined, and less fragile overall.
Clean Interface and Workspace Setup That Keeps Client Projects Organized
What do you like best about the product?
The workspace setup is the biggest win for me. I can keep client projects separated without mixing all my tabs together, which helps me stay organized throughout the day and spend less time searching for what I need. The interface is also very clean, and that makes long work sessions a lot easier on the eyes.
What do you dislike about the product?
Sometimes it takes a little time to get used to new updates. A few extensions I rely on needed some manual adjustments at first. It wasn’t anything major, but there was a small learning curve during the first week.
What problems is the product solving and how is that benefiting you?
Before using Anchor Browser, my tabs were always out of control. Now everything is grouped by project, which makes it much easier to stay focused and get through my work faster. It’s genuinely reduced the day-to-day friction for me.
Anchor Browser Restores Your Workspace Seamlessly—even After a Crash
What do you like best about the product?
Anchor browser restores my entire workspace, including tab groups, even after a crash. This is a feature I really like.
What do you dislike about the product?
The export options are pretty basic, but I haven’t run into any other issues.
What problems is the product solving and how is that benefiting you?
This consolidates my research notes with the source pages, making it easier to keep everything in context.
Anchor’s Anti-Tracking and Sandboxed Tabs Inspire Confidence on Sensitive Systems
What do you like best about the product?
Anchor’s anti-tracking features and the sandboxed tabs gave me more confidence when accessing client portals and other sensitive systems.
What do you dislike about the product?
Some corporate intranet pages are triggering the security blocks.
What problems is the product solving and how is that benefiting you?
This reduces exposure to data leaks and risky tracking during sensitive tasks.
Automated authenticated financial workflows have replaced brittle scripts and reduce manual effort
What is our primary use case?
How has it helped my organization?
We operate in an environment where many critical workflows still require interaction with legacy web UIs, often behind MFA, bot detection, and changing front ends. Anchor Browser allowed us to productionize browser-based automation without building and maintaining our own fleet of brittle headless scripts. The biggest impact was on reliability and engineering time. We moved from fragile Playwright jobs and constant break-fix issues to a setup where sessions, authentication state, scaling, and failure recovery are handled as infrastructure. This reduced incident noise and freed engineers to focus on product work instead of babysitting automations. We also improved turnaround times for operational workflows such as data pulls, confirmations, and document gathering, and made it feasible to automate longer multi-step tasks end-to-end.
What is most valuable?
The managed browser infrastructure at scale was invaluable as we did not want to run and patch our own browser farm. Anchor made it feel like an API. Authentication and session handling, with persistent sessions and re-authentication patterns, made authenticated automation less fragile. Reliability tooling provided better observability into failures, retries, and what changed when a flow breaks. Bot detection mitigation and realism, through headful, human-like execution patterns, helped in portals that aggressively block automation. The self-healing approach, when the UI changes, provided a materially better recovery story than traditional scripts.
What needs improvement?
I believe the solution could benefit from supporting even more types of legacy browsers.
For how long have I used the solution?
I have used this solution for 14 months.
Which solution did I use previously and why did I switch?
We started with in-house Playwright plus a couple of generic RPA-style approaches. They were fine for demos but became expensive to maintain in production. We made the switch when we needed higher reliability, scaling, and a more robust approach to authenticated portals and bot defenses, without turning browser automation into a dedicated platform team.
What's my experience with pricing, setup cost, and licensing?
Price it against the fully loaded cost of building and operating this yourself, including infrastructure, on-call, break-fix churn, and missed SLAs, not against the cost of running a script. For us, the ROI was clear once the workflows became business-critical. Start small with one to two high-value workflows, measure success rate and time saved, then scale. Also, ask for pricing that aligns with your usage pattern, as concurrency and successful runs matter more than raw seat counts.
Which other solutions did I evaluate?
We looked at a few 'browser automation infrastructure' vendors and a couple of automation agent frameworks, and we also considered continuing in-house. Anchor stood out for production readiness for authenticated workflows, reliability, and the fact it felt built for engineering teams rather than being an RPA tool.
What other advice do I have?
If your workflows touch regulated systems, treat browser automation like production software by versioning workflows, monitoring them, and setting expectations around authentication policy changes. Anchor works best when you invest a bit in defining 'golden paths' and instrumentation, then you can trust it for the long haul. Overall, this is the first time browser automation felt like reliable infrastructure rather than a pile of scripts.
showing 11 - 15