Launch HN:Agent37 (YC F26) – 运行智能体(agents)的低成本沙箱
Launch HN: Agent37 (YC F26) – Low-cost agent sandboxes for running agents
我们发现了什么
方向观察:Launch HN:Agent37 (YC F26) – 运行智能体(agents)的低成本沙箱。原文包含第三方或历史项目线索,暂不能归属于本产品,需核对完整来源。
- 来源:Hacker News(发现于 2026-10-13)
- 证据等级:D · 包含历史项目、第三方案例或未来计划;不能作为当前项目收入证据。
- 商业模式:待核验
- 主题:AI Agent
- 初筛评分:31.4/100 · 收录 1 次
证据,比故事更重要。
规则清洗与初筛,未经人工商业核验。原文语境、实际客户和付费情况仍需自行验证。
引用与数字披露
来源类型(原作者自述/第三方测算/媒体转引)需采集端标注,本版尚未落字段。
- 作者
- 未标注
- 抓取日期
- 来源类型
- 未标注
- 币种
- 未标注
- 口径
- 未标注
- 披露主体
- 未标注
- 披露日期
- 未标注
中文辅助译文(全文)
HN 大家好,我是 Vishnu,来自 Agent37(https://agent37.com )。我们构建用于运行 AI 智能体的沙箱,成本低于大多数沙箱提供商的 10%。我们的客户平均每个沙箱每月花费 0.37 美元。你可以在这里观看产品的视频演示:https://youtu.be/DK5ISR2tbNo
我们最初就是一家 OpenClaw 套壳公司,时间是今年二月(没错……你可以尽情嘲笑)。后来我们逐渐加入了越来越多的智能体框架。当时我的目标之一是向用户提供免费计划,以获取更大的市场份额。但立刻这么做成本太高了,特别是因为我们是自筹资金,服务器一直靠我的个人积蓄在支撑。由于此后的各项优化,我们今天终于能够提供免费计划了。我们超过 90% 的新注册用户都是免费计划用户,他们在我们云上托管自己的 Hermes、Openclaw、Claude Code 等等。免费沙箱的基础设施成本平均每位用户每月约为 0.05 至 0.10 美元。以下是一些有效降低成本的方法:
- 当你观察智能体框架时,它们在 CPU 和 RAM 的使用方式上有一些特定模式。它们在初始化或执行某些任务时需要 CPU 突发资源,但除此之外,通常并不会达到峰值。它们在浏览器和计算机操作(computer-use)等任务中需要更多 RAM。任务完成后,使用率通常又会降下来。这是降低成本的一个关键洞见——通过高效管理 CPU/RAM 的利用率,我们可以降低成本。
- 其次,租用宿主机时要跳过超大规模云厂商。我之前在 Amazon 工作过,他们 VM 业务的利润率高达 80-90%。所以一旦我看到价格,往下一层选择 Hetzner、OVH 这类厂商就成了一个显而易见的决定。仅这一步大概就是降低成本最大的杠杆之一。
- 第三,你还需要选择一个能够高效地在宿主机之间缓存和共享资源的技术栈。我们使用 gVisor 以获得更好的资源利用率和更快的启动时间。它让我们可以在所有沙箱之间共用宿主机上的可用内存,而不必为每个沙箱预留完整 VM 的内存。这其中也存在权衡:我们的 gVisor 沙箱并不支持像 Docker-in-Docker 或 Android 模拟器这类工作负载。
- 最后,你购买的主机的规模和配置形态也会带来很大差异。在成本上,瓶颈通常是 RAM 而不是 CPU。对于智能体框架工作负载尤其如此,因此在采购服务器时,我们优化方向是在一台宿主机里塞下尽可能多的 RAM。我们也提供完整的 VM 沙箱来支持那些需要它的工作负载,包括运行 Docker,价格会略高一些,但综合其它技术,整体仍然相当低。
总体而言,我的经验是:仅仅通过聚焦沙箱用例的一个细分领域并为之做优化,就能提供更好的成本/性能取舍。我此前曾担任 Amazon 的高级软件工程师,以及 Quantcast 的工程经理。我曾构建 Amazon 的内部 AI 聊天机器人 Diya,以及他们的内部编码框架 Ziya。如果你正在寻找用于运行智能体的沙箱供应商,欢迎来看看我们。我们尤其欢迎正在开发消息类智能体的开发者来试用他们的工作负载,挑战我们平台的极限和经济性。
谢谢!
https://agent37.com
译文由上游机器翻译生成,可能有误;判断请以英文原文为准。
英文原文(来源本站未改写)
Hey HN, I’m Vishnu from Agent37 ( https://agent37.com ).We build sandboxes for running AI agents at under 10% of the cost of most sandbox providers.Our customers spend an average of $0.37/month per sandbox.You can view a video walkthrough of the product here: https://youtu.be/DK5ISR2tbNo We started as one of those OpenClaw wrapper companies back in February (yup.. judge me).In time we added more and more harnesses.One of the goals I had at the time was to offer a free plan to users, so as to gain more market share.But it was too cost prohibitive to do it right away.Especially since we were bootstrapped and servers were running on my savings.
Today we’re actually able to offer the free plan thanks to the optimizations we’ve made since.Over 90% of the new signups we have are just free plan users and they host their personal Hermes/Openclaw/Claude Code etc on our cloud.Our infrastructure cost for the free sandboxes averages around $0.05 to $0.10 per user per month.Here are some techniques that have worked for lowering cost: * When you look at agent harnesses, they have certain patterns in the way they consume CPU and RAM.They need CPU in bursts when they’re initializing or performing certain tasks, but beyond that, they’re often not peaking.They need more RAM for things like browser and computer-use tasks.
Once the task is done, usage often comes back down.This is a key insight in lowering cost, so by efficiently managing the CPU/RAM utilization we could lower the cost. Secondly, you have to skip the hyperscalers when renting the Hosts.I worked at Amazon before and they have 80-90% margins on VMs.So it was an obvious choice once I looked at the prices to go one layer down to vendors like Hetzner and OVH.This alone was probably one of the biggest cost levers in reducing the cost. Thirdly, you also want to pick a technology stack that lets you efficiently cache and share resources across the host.We use gVisor for better utilization and fast boot times.
It lets us use available host memory across sandboxes without reserving a full VM’s memory for each one.There are tradeoffs: our gVisor sandboxes don’t support workloads like Docker-in-Docker or Android emulators. * And finally the size and shape of the hosts you buy also makes a big difference.RAM is typically the bottleneck when it comes to cost and not the CPU.This is specifically true for agent harness workloads, so when buying servers, we optimize for packing more RAM into a given host.We also host full VM sandboxes for workloads that need them, including running Docker at a slightly higher price, but they are still pretty low cost given the rest of the techniques.
Overall, my learning has been that just by focusing on a niche of sandbox usecases, and optimizing for it you can give a much better cost/performance tradeoff.I was previously a Senior Software Engineer at Amazon and an Engineering Manager at Quantcast.I built Amazon's internal AI chatbot, Diya, and their internal coding harness, Ziya.If you’re someone who’s looking to run agents on sandbox and are exploring a sandbox vendor, come check us out.We’re particularly looking for developers building messaging agents to try their workloads and challenge the limits and economics of our platform.Thanks!https://agent37.com
这条还缺什么证据?
下面每条都由本条已有字段推出(等级、理由、商业模式、来源次数、是否演示), 本站不生成推测性结论;通用验证方法放在方法论页。
- 可核验的收入或付费证据查官网定价页与付费口径;第三方数据源(如 GetLatka)只作旁证,需标注来源与时点。
- 商业模式未定确认按席位/按用量/授权还是开源托管版收费;开源项目另查 LICENSE 与是否存在付费版。
- 只有单一来源找一手站点或其他渠道是否重复出现同一产品;社区热帖数量不等于商业进展。
通用验证清单(谁有这个问题/谁愿意付费/一个人能交付哪一小步)见我们的筛选方法。