展示HN：用于被不断封锁的AI代理的移动IP
嗨，HN。
过去一年我一直在构建自动化工具。一个问题不断出现：在本地一切正常，但一旦部署到AWS或其他云服务提供商，网站就开始封锁。
大多数AI代理都是从数据中心的IP地址运行，而这些IP地址已经被许多网站标记。
因此，我们决定为此构建一个解决方案。
Aluvia允许代理使用移动运营商的IP地址连接，而不是数据中心的IP地址。这个想法很简单：如果流量看起来更像真实的移动用户，就不容易被封锁。
我们将其打包为：
@aluvia/sdk
@aluvia/cli
@aluvia/mcp
它与Playwright、Puppeteer、Axios、Selenium等类似工具兼容。
我们并不想与大型代理公司竞争。我们只是想要一些对开发者更友好、集成更简单的工具，特别是针对AI开发者。
现在还处于早期阶段，因此我非常欢迎反馈。想知道这里的其他人是否遇到过同样的问题，或者以不同的方式解决了它。
网站： [https://www.aluvia.io](https://www.aluvia.io)
欢迎提出技术问题。
查看原文
Hi HN.<p>I've been building automation tools this past year. One problem kept happening. Everything works fine locally, but once deployed to AWS or other cloud providers, sites start blocking.<p>Most AI agents run from datacenter IPs, and those IPs are already flagged by many websites.<p>So we decided to build something for it.<p>Aluvia lets agents connect using mobile carrier IPs instead of datacenter IPs. The idea is simple. If traffic looks more like real mobile users, it gets blocked less often.<p>We packaged it as:
@aluvia/sdk
@aluvia/cli
@aluvia/mcp<p>It works with Playwright, Puppeteer, Axios, Selenium, and similar tools.<p>We're not trying to compete with the big proxy companies. We just wanted something more developer-friendly and easier to integrate, especially for AI builders.<p>It's still early, so I'd really appreciate feedback. Curious if others here faced the same issue, or solved it differently.<p>Website: <a href="https://www.aluvia.io/" rel="nofollow">https://www.aluvia.io/</a><p>Happy to answer technical questions.