Remix.run Logo
Show HN: Fortress – Give your agents unlimited access to the web
9 points by armanluthra_ 11 hours ago | 4 comments

i personally believe that the internet is the best thing we've ever built, and arguably, nothing we made before comes close. now agents can use it too, but the web treats them as second-class. every agent works for a person, so whatever it keeps from agents it keeps from us. we believe that if we let them in, each of us gets the whole of what we built, a thousand times over.

and to add to that, democratization of tools that allow this is essential, despite the fact that there will always be bad actors.

so, we built fortress, which is an open-source stealth chromium engine. it is a recompiled fork that corrects the browser fingerprint from inside the engine: the surfaces bot detectors read, canvas, webgl, audio, fonts, navigator, and about thirty more, are patched in chromium's c++, with no javascript layer sitting on top for a page to catch.

it beats the hardest bot detectors on the planet, works fully locally and is open source for y'all to see the patches we've made. and it comes with an mcp, so you can use it with your agents without having to do any major setup or code changes. do give it a try here!

https://github.com/tiliondev/fortress

sightspinner 4 hours ago | parent | next [-]

All for OSS and all but seems like one of two things will happen: A. This repo becomes really popular and useful for a lot of projects, cloudflare or someone else hears of it, looks a the code, finds a way to block it. B. It doesn’t become popular

armanluthra_ 4 hours ago | parent [-]

we believe there is a third option too, and that's what we are working towards. more info on that soon hopefully

zhaodc 10 hours ago | parent | prev | next [-]

To be honest, I just got banned by Reddit's network security system. Using an exclusive static IP and anti detection browser, it was still recognized. The core issue is not whether the fingerprint forgery at the JavaScript layer is good enough, but rather the type of IP itself - data center IP vs residential ISP IP, which triggers detection before your browser fingerprint.

I would like to ask a technical question: How does Fortress handle lower level detection such as WebRTC leakage of real IP and TCP/IP protocol stack fingerprints (TTL, window size, and other OS level features) after fixing fingerprints at the C++layer? Because the actual situation I encountered is that even if the browser fingerprint is perfect, the features of the network layer are not consistent and will still be marked.

kfhfardin 10 hours ago | parent | prev [-]

Remember some discussion about this before in HN. I think democratization is definitely useful, and it's a good first step in building it out in the open. Still, I think there is a broader discussion needed in the industry about dealing with bad actors, which would also be useful, but it's a cool project to herald in the agentic world for everyone and not just Big Tech.