congrats 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?
Hi, 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?
What about Maritime.sh (which is also in YC)? I swear everybody in SF is building the same stuff. Lol
Thank you!
Yeah, this seems like a niche where multiple startups are coming in. But if I remember correctly, we're about 3X cheaper than boat. We did a detailed comparison of all sandbox companies and where we stand across vendors here
Funny I just asked that too but in my quick check boat was slightly more expensive albeit with more storage space.
This 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?
That's right each harness runs in it's own sandbox. Really the harness itself is just a docker template with some pre-installed harness (say openclaw, hermes, claude code, opencode, pi, grok etc) that runs.
For convenience and cross-harness unified API we also built open source Gateway API - https://github.com/agent37-platform/gateway
Think of it as open router for Agent harnesses. So in our default templates we also run this and expose the APIs. So that makes using any harness easy as they all speak a single OpenAI responses API schema.
This is freaking great. Thank you for posting!
glad to hear it, thank you!
How 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?
Great question!
Cron jobs were a big problem, especially if you want agents that must auto-sleep to save on costs. Since you cannot put the cron jobs within the sandbox container anymore, we eventually created our own cron API to wake up the sandbox and execute the cron
I 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)?
Similar to Sprites in capability, so if you can use sprites you can use agent37. We're also about 94% lower cost than them.
Fly certainly has great branding since they've been around for a while now. So they have a distribution advantage. But I think at some point they will also need to own some niche rather than just being a generic sandbox company, given how competitive the space is.
Just use EC2 t4g.nano
Interesting, I looked into this. So The t4g.nano is 2 vCPU but only 0.5 GB RAM, so there's that trade off.
And from what I can tell as you bump more RAM, agent37 is around 5x cheaper: our 2 vCPU / 4 GB box is $4.94/mo (2/4/6 GB disk), vs AWS t4g.medium (the actual 2 vCPU / 4 GB Graviton box) at ~$24.50/mo
I 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.
Thank you, that's so great to hear !
For connectors we do offer managed MCPs like Composio, BraveSearch, and even an LLM gateway (which routes to openrouter). So what we have is simply a pass through for now and we're not looking to do more there. Since most of our early customers were just launching personal agents like Hermes, OpenClaw, Claude Code and wanted an easy white label setup.
Although now it's expanded to just sandbox usecases.
I'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!
Boat is a great company too! As far as pricing goes our default sandboxes are about 2.8X cheaper than boat.
We did some detailed pricing analysis here https://www.agent37.com/pricing#sources
For storage you can request more storage if your use case needs it. And yes would appreciate it if you can include us.
Tangentially, 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?
Agent Substrate from google if you wanna go hardcore, although it adds quite a bit of complexity and management that you probably don't want if it's just a personal setup - https://github.com/agent-substrate/substrate
Docker with tailnet is probably good enough for your usecase.
I did some investigation into podman since I'm on Fedora and my limited understanding is that it is a bit more lightweight and less tied to the commercial Docker offering. My conclusion was that even that was a bit more than is actually needed. Both Opus 5.5 and Sol 6.1 suggested just to set up a single `agents` user on the box that both use and put things like shared dev credentials into a ~/.config/agents subfolder.
But there are many tiny details to the whole setup. Like, making sure services start at boot instead of login. And adding isolation to dev resources (I mostly use Postgres and Redis) to avoid agents stepping on each other. There's also things like setting up GitHub Apps so that attribution works well. And then there are the "remote control" features of Claude vs. a persistent tmux I can ssh into. I've could go on, but I think most people will get the point.
I'm actually surprised I don't see more discussion about this from devs.
Use smolvm, support for tailscale in each VM.
A self-hosted cloud offering is very close to what I was thinking of from a commercial offer. It is also the least documented, which makes sense. I'm guessing what I am trying to do is the niche case and most devs will either want to run on their local machine and/or a cloud. Therefore a commercial offering is obviously going to want to support local while providing a low-friction on-ramp to their commercial cloud product.
https://pleasedonotescape.com/
I recommend "byre" from that list, because I built it. You can inject credentials you want into it, but it can't touch the host. I run all my coding harnesses inside it. At the end of the day, it's a flexible and reusable way of spinning up Docker containers designed for agents.
Thank you for the resource, this kind of aggregation is very useful.
On a quick skim you have categories: Local, vendor-managed, Hybrid. I am looking for something in-between local and vendor-managed. In a sense, I want the separate box to be the sandbox, rather than have a sandbox on my local machine isolated using a container or VM. That is a bit different of a setup with its own constraints that things like VMs or containers don't directly address.
Pretty 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.".
We use OpenAI Luna for the agent37/default model for that.
Yeah in addition to sandbox we also have managed MCPs and our own LLM gateway to make building hosting agent harnesses easier. Most of our customers host hermes, opencode, claude code etc. and needed an easier setup so we ended up offering our own LLM gateway for it, ready to use with the sandbox
Also, curious if this is intended or a bug:
> I still can’t retrieve the page from the link: the public-web reader is out of quota, and my direct fetch isn’t available in this session.
I wanted the QM agent to read my website but it says I'm out of quota. Seems a bit odd to have a quota on that. Plan usage explains that there is a quota on searches, which makes sense, but it does not mention that there is one on fetching URLs directly.
edit: Tried again but with Hermes agent and it worked. It was my first time using QM so maybe it's a capability I had to configure.
So the QM agent is a bit different than a typical harness. It sometimes for tasks that it needs to do more research, launches a separate sandbox per user where it does all the hard tasks.
And so for that it needs workspace credits so that it can spawn new sandboxes for such tasks. Especially if you just started with the free agent.
Congrats 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!
Thank you ! And agreed, it's an extremely competitive space. In our YC batch alone there's probably 5+ companies doing something similar. Interestingly enough though atleast for now we're all rapidly growing, so that's promising.
But eventually I see us all moving in slightly different spaces as we specialize.
Great to hear you are growing! Take this as you might grains of salt.
The promise of really cheap AI sounds amazing and is amazing. People will happily accept and engage with "free stuff"; but, I presume you are not starting a business to give away free stuff. Unless you have some model that let's you capture value some other way. e.g. Meta just gave everyone a small computer for free with Muse. Or have some sustainable price advantage on the underlying compute e.g. you are nvidia and make it yourself at scale.
I think you deserve to be compensated for your work! It's hard to make a sustainable business when selling something that costs $5 a month to developers (just seeing your calculator). There aren't that many of us, and AWS/GCP/Azure/Cloudflare have our credit cards already. If it were me, I'd be trying to figure out how to charge more and sell the value of the work you are enabling your customers to accomplish, not the cost of the underlying electrons.
Keep it up!
thank you, yeah we still have a lot to figure out.
I 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.
hahaha, I suppose it is becoming a bit like hunger games, haha. I was genuinely surprised to see how much overlap there was in the batch across startups.
I'd be curious to see stats on overlap among startups by batch historically. My impression is that this has always been a thing. Based on where the market/technology horizon currently is, there are some buckets that are very "startup shaped". Founders who are iterating on ideas using similar criteria will often end up in the same proximity, especially in an accelerator environment. But it would be extremely interesting to see if this has become more prevalent over time, or at least since the explosion in the AI market.
It is also funny to see folks and friends of the startup commenting and trying to boost this post which is against the guidelines, but thats ok.
Yeah its a race to the bottom as ai can vibe code any infra now
hahaha, I think it's the same thing as what's happening with LLMs and token cost.
Bruh, that's lack of understanding and insight as well as naivety. It is not a race to the bottom. LLM is the winner-takes-all market. Competitors are pricing against each other to come out on top.
Once there is a winner, there will be a price correction.
In your case, positioning yourself as a cheap provider is inherently a bad idea.
> Once there is a winner, there will be a price correction.
Only if there is some form of lock in or the others go out of business. Both of those are low probability. I'd put a friendly wager on the (lack of) increase of token costs in the next 2 years.
This hasn't happened in the sandbox space though. For example Modal was early to it, and yet you see Daytona, E2b and many others doing quite well.
The switching cost is not trivial unlike LLMs
Sandboxes 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
There's a talk from Travis Kalanick recently on a podcast about this. It talks about the advantages of a startup vs an incumbent. My read is if a startup competes on price, the incumbent has no choice but to first let them gain a bunch of market share. It's too expensive for the incumbents to compete on price because a no-name startup is doing it. So they'd have to let you get relevant enough for it to make sense to compete on that axis.
I view it as a wedge to gain market share and later compete on something else.
This isn't commoditized because an incumbent has the market share, it's commoditized because there are dozens of providers in a crowded market. So what is likely going to happen is there will be a race to the bottom in terms of price.
PS - This is why I loathe advice from prominent software co operators. It's not one size fits all. Uber's strategy is going to be very different than Tesla's strategy which is going to be very different from Amazon's strategy.
unless the startup has gobs of free money how can they do this against an incumbent? note: nobody has gobs of free money anymore, except the incumbents. Startups competing on price is typically not a winning strategy, unless they have some technical advantage that shifts the price curve; subsidizing a move on it doesn't work.
It's the latter for us. We have healthy margins even at this price point. So we don't actually need a lot of money to do this against incumbents.
.. Don't you think it suspicious/sounds too good to be true? A newly created product space with insane margins, and easy to compete in?
Easy to compete+huge margins -> lots of competitors who compete on price -> commotidization -> lower margins -> not good
haha, the inevitable cycle of capitalism.