News for hackers. Stuff that matters.

ashriv

Spend caps are enforced by us returning a 429 when a model provider is called, you can elect to have some sort of loop detection but that comes down to harness engineering - we don't touch what runs inside of the VM.

In-progress tool calls are kept upon sleep/wake, however, open connections aren't (since typically the other side usually times out either way)

Thanks!
We're not racing to the bottom because sandboxes are a small part of our offering. Every company is going to be running thousands of agents sooner or later, and they'll all need custom environments. More agents = more $
We sell primarily to startups that run agents, rather than directly to individuals. E.g. healthcare agent companies, personal assistants, products with embedded agents, etc.
You'd define the tools in the agent harness, and you can set up env variables through us. You can also connect to on prem databases using things like our connect module.
We are headless! We spent a lot of time fleshing out our CLI so our customers' coding agents can deal with things themselves. That said, a lot of customers want some sort of visual basis to see what's going on, especially if they have a lot of users.
I think the primary distinction here is we let each agent get its own isolated VM. Agent substrate lets you run many agents on shared workers. Plus we run the whole thing for you :)
Thank you! I think this is where things are headed too
Thank you! And yes I agree that getting VMs up is quite trivial, patching hosts and guest kernels after CVEs is part of what we mean by "managed" - we don't want our customers having to continuously maintain things.

As for latency, we've noticed that since most agent runs take >10s, a couple extra ms of latency isn't a huge problem for a lot of companies. That said, we're planning on getting more edge hosts, and BYOC.

Most are focused on providing commoditized compute, there's a lot more nuance when building an agent company.
Fair! What did you build on AWS? What was the most time consuming part?
No. We mount an individual /data volume to every VM that persists, but if you have data that's in S3 or R2 you can hook those up as well.
Up to you, we have support for BYOK, AI subs, or pass-through where you can top up our LLM gateway and we take care of spending caps per user, etc. Whatever fits your use case best. What are you building?
Agent37 is great if you want plain, cheap sandboxes. But you still have to build and manage a lot of the infra to sell agents to customers, we manage the entirety so that you don't think about cloud runtime at all and can focus on other things. We also provide you with ongoing support, an infra partner if you may.

DigitalOcean is focusing on coding agent sessions in the cloud, rather than managing the things necessary to sell long living agents to customers.

Launch HN: Maritime (YC F26) – The managed cloud for production AI agents

Hi HN, we're Ary and Maria, co-founders of Maritime (https://maritime.sh). We're building an agent-native cloud that handles everything from custom environments to lifecycle management for AI agents.Demo: https://www.youtube.com/watch?v=lCWMdBQ96rYThere’s been an explosion of sandbox companies coming out of SF, but sandboxes solve maybe 10% of the infrastructure problem for AI agents. The...

( Read More... | 41 comments | 2 points | on HN )