Launch HN: Agent37 (YC F26) – Low-cost agent sandboxes for running agents
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!
- ghm2180 - 181 sekunder sedanCongrats on the launch. What's your turn around time to sign a BAA?
- mparis - 14862 sekunder sedanCongrats on the launch! Very exciting!
You guys are operating in a very competitive space. This stuff is fun to build, so a lot of engineers will end up building it. Not to discourage you, but I suspect it will be difficult to capture much value selling this offering as its going to be race to the bottom against very well funded alternatives that can sell these features at a loss in order to get you to use their databases and other offerings that are higher margin and stickier.
As you guys learn more about how to take this sort of technology to market, you may consider trying to get closer to the actual work that people actually need these agents to do. What can you do better because you have this technology? For example, I work in healthcare administration and we have built our own agent sandbox infrastructure on top of firecracker microvms that solve similar use cases as Agent37. We will never sell it. It's part of our competitive advantage for doing healthcare tasks.
Food for thought! Good luck!
- alasano - 15625 sekunder sedanI've been looking at offloading local work from my MacBook Pro (M1 Pro / 32 GB) specifically because I've been working with a lot of Android apps and emulation is killing me on top of everything else that I'm running.
Got a bunch of Daytona credits which are close to useless given their restrictions until you hit tier 3.
You seem like you're actually slightly cheaper than https://boat.dev/ but with less storage? That's the closest to your pricing unless I'm mistaken. Any other insight as to differences between you two?
Also I'll add you to a list I've been maintaining of sandbox providers, congrats on the launch!
- MikhailTal - 13735 sekunder sedanSandboxes look a bit commoditized. You cannot 10x on basically what's just a VM with a few agent-friendly features in 2026. Hence competing on purely price as a new startup is a bad idea imo. As you mentioned hyperscalers have insane margins, but if this turns out to be a real market, they will lower cost, even just eat the loss if they want and take you out of business. Without any hardware innovation, it's tough for me to see this working. If you are going with a customization angle, again, no moat and plenty of competitors
- talkarimli - 2537 sekunder sedancongrats on the launch.
i think the sandbox part is getting commoditized, like others said. the harder part is what the agent can touch inside it.
you connect google, the agent gets access to everything. sandbox protects the host. it does not protect your tokens.
scoped, short lived credentials per task. that i would pay more for. is it on your roadmap?
- stillpointlab - 11515 sekunder sedanTangentially, I've been investigating the last few days on how to setup a separate Linux box as an agent "playground". I got a mac mini to use as my own personal driver and now my Linux box is free, so I want to have a local setup where I keep my personal machine a bit stricter while giving near free-reign for agents on the Linux machine.
It is like a locally-hosted version of these commercial projects. But I'm doing it ad-hoc. This seems like a space that should be filled by open source. What are the options that exist now? I have pro plans for both Codex and Claude Code and enough credits to run a couple instances of each. I want to control them from the mac mini over a tailnet. What options exists now?
- pgcosta - 6555 sekunder sedanHow do cronjobs work? IE: If I ask an agent to setup a cronjob to check on my email once a day, how does the sandbox behave?
Does it have a layer that intercepts Cronjob creation, and setups up a reminder on the supervisor to wake the VM to run the agent job?
- rajangdavis - 15973 sekunder sedanI have been using your service for a few months… super easy to set up and use. I signed up after my bank would not let me process a payment to Hetzner :)
My use case was to play around with hermes. I was using it for a while but I didn’t like how it ended up (the whole set up became overran with files and was a mess, my fault).
I still haven’t 100% figured out how I may want to use the service again, but I thought it was super easy to set up.
My only feedback is that some connectors for google’s integration were kind of privacy nightmare the last time I checked.
Google’s API for using AI has abominable UI and set up.
It would be nice to be able to bridge the gap of simplifying Google’s AI/Service integration while not having to hand over access to every Google service I use.
- olalonde - 14447 sekunder sedanPretty cool, trying it out. What LLM is it using in the free tier? I was surprised that it worked without supplying an API key. The model doesn't seem to know either: "This run is labeled agent37/default. That’s the configured model name I can see; it doesn’t reveal which underlying model/provider it maps to.".
- ATechGuy2 - 15673 sekunder sedanThis is cool; pricing is certainly appealing. At the same time, there are a ton of sandboxing providers.
> When you look at agent harnesses, ... CPU/RAM utilization we could lower the cost.
How does it work today? Is the harness (assuming it means the agentic loop) located in a separate VM and each loop-run invokes a separate sandboxing VM?
- christoff12 - 16391 sekunder sedanI have yet to use sandboxes though have some experimentation planned for a new gig I'm starting in a week.
How would you compare what you do to fly.io's Sprites (which is currently atop my To Try list)?
- bitlad - 16854 sekunder sedanI had ran into another yc startup from the same batch doing the same thing recently. I think it was called maritime.
YC batch are becoming more like hunger games.
I know a few companies where this is just a feature like digitalocean it is just a feature.
- invalidOrTaken - 16782 sekunder sedanThis is freaking great. Thank you for posting!
- pranshuchittora - 11610 sekunder sedanJust use EC2 t4g.nano
- colesantiago - 15896 sekunder sedanHi, Vishnu, congrats on the launch.
There is another even cheaper sandbox which is in YC (boat.dev)
How do you compare to them and how are you cheaper then they are?
Nördnytt! 🤓