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.
Cool :) if I used Maritime to power my agent product, would my end users be able to sign in with their existing AI subs? Or would they have to enter their API key.
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?
there is no such thing as bringing AI subs, it's against TOS on Claude and OpenAI to use your subscription in third party tools. You have to use API key usage which is extra on top of your subscription
cool product. right now I just built my own version of this on AWS (which is likely far more expensive, but we have startup credits). I'll definitely check this out one day when the credits end/expire. I will say that startup credits would really help!
side note, this design aesthetic is so cool but now literally every SF AI startup uses it -- I'd almost prefer craigslist style where the information is to the point and direct. i.e how much money/time will this save me and is it secure. the two questions i only care to answer here. i think the aesthetic is meaningless at this point bc of how easy it is to vibe this template out
its basically a 24/7 box with claude code on it. I think the most time consuming part was not the box setup, but rather getting my local skills/workflows (that are fairly scattered) into something rebuildable/reusable. And as I work on my box, i realize there are missing dev pieces that I had on my local machine so I always have to keep remembering to update the docker image with the base level CLIs/MCPs/skills that i need. Wasn't too bad, but definitely annoying
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 :)
Congrats on launching! I think the lifecycle management and cost-optimization layers you're building on top of microVMs address some painful problems for teams deploying agents in production.
I work at a neocloud company, and from my experience, getting VMs up and running with Firecracker/KVM on bare-metal infrastructure is relatively straightforward and requires little operational overhead initially.
The real challenge is what comes afterward: continuously monitoring, patching, and responding to newly discovered CVEs. Falling behind on security updates can have serious consequences, and ultimately, it's your customers who bear the risk.
This is one reason I'd be cautious about choosing a smaller provider based solely on price. At the infrastructure level, many providers are essentially selling the same isolated VMs. The real differentiators should be security, reliability, and operational maturity, particularly with AI accelerating vulnerability discovery and expanding the attack surface. Saving a few dollars on compute might not be worth the trade-offs.
There's also the question of geography and latency. If your agents run in a big tech cloud, offloading sandbox execution to infrastructure on another continent isn't necessarily a great choice. The added network latency can significantly impact agent responsiveness, especially when agents need frequent interactions with external services or real-time applications.
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.
Forgive my naivety, but if it's built for agents then why should humans need to login, view a dashboard, care about it?
Thinking about product market fit, buyer personas, and right audiences here.
Would there be a future where maybe the agent can elevate to the human what the human needs to know when it wants to or requires it from what it has access and these platform-like UX constructs are more like a "just in time" construct similar to Claude Artifacts?
I expect the next cloud for AI to be fully headless, though maybe I'm wrong
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.
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.
Congratulations on the launch. Very interesting idea. I read your description, and it's striking: it's as if you described our infrastructure at Playcode (https://playcode.io/cloud). The similarity is just colossal, it's what we built for ourselves and for our clients.
Its like sandboxes are a popular space or something... who would've thought. its surprising people have similar infrastructure to playcode I truly can't believe it
How are you going to pay back the 500k if you’re charging $1/month and competing with a thousand other startups that are all racing towards the bottom?
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.
The point about sandboxes being only a small part of the problem makes sense. Lifecycle seems like where most of the custom code ends up. Two questions: how do spend caps work when an agent gets stuck in a loop mid-task, do you stop it hard or let it reach a checkpoint first? And when a VM sleeps and wakes, what state is kept beyond the disk, for example open connections or in-progress tool calls?
bitlad | 8 hours ago
Also, digitalocean offers this now.
demibabs | 7 hours ago
[OP] ashriv | 7 hours ago
DigitalOcean is focusing on coding agent sessions in the cloud, rather than managing the things necessary to sell long living agents to customers.
bitlad | 7 hours ago
[OP] ashriv | 7 hours ago
linuxamd64 | 5 hours ago
It is exactly the same offering.
[1] https://www.digitalocean.com/products/managed-agents
bravura | 3 hours ago
bitlad | 3 hours ago
[1] https://debarshibasak.github.io/awesome-paas/
sgtwompwomp | 8 hours ago
[OP] ashriv | 7 hours ago
asdev | 3 hours ago
momojo | 7 hours ago
[OP] ashriv | 7 hours ago
0x0000F8 | 7 hours ago
plus it basically plugs into everything out of the box (ides, sdks, apps, etc), I haven't even broken the free tier for all my loads thrown at it.
It's reliable enough we even use it in production systems.
volkk | 7 hours ago
side note, this design aesthetic is so cool but now literally every SF AI startup uses it -- I'd almost prefer craigslist style where the information is to the point and direct. i.e how much money/time will this save me and is it secure. the two questions i only care to answer here. i think the aesthetic is meaningless at this point bc of how easy it is to vibe this template out
[OP] ashriv | 7 hours ago
volkk | 7 hours ago
cidd | 7 hours ago
[OP] ashriv | 6 hours ago
binsquare | 7 hours ago
I think it’s the right kind of innovation sort of like ec2, serverless functions, and etc in the age of ai
[OP] ashriv | 6 hours ago
ATechGuy2 | 7 hours ago
I work at a neocloud company, and from my experience, getting VMs up and running with Firecracker/KVM on bare-metal infrastructure is relatively straightforward and requires little operational overhead initially.
The real challenge is what comes afterward: continuously monitoring, patching, and responding to newly discovered CVEs. Falling behind on security updates can have serious consequences, and ultimately, it's your customers who bear the risk.
This is one reason I'd be cautious about choosing a smaller provider based solely on price. At the infrastructure level, many providers are essentially selling the same isolated VMs. The real differentiators should be security, reliability, and operational maturity, particularly with AI accelerating vulnerability discovery and expanding the attack surface. Saving a few dollars on compute might not be worth the trade-offs.
There's also the question of geography and latency. If your agents run in a big tech cloud, offloading sandbox execution to infrastructure on another continent isn't necessarily a great choice. The added network latency can significantly impact agent responsiveness, especially when agents need frequent interactions with external services or real-time applications.
[OP] ashriv | 6 hours ago
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.
hmokiguess | 6 hours ago
Thinking about product market fit, buyer personas, and right audiences here.
Would there be a future where maybe the agent can elevate to the human what the human needs to know when it wants to or requires it from what it has access and these platform-like UX constructs are more like a "just in time" construct similar to Claude Artifacts?
I expect the next cloud for AI to be fully headless, though maybe I'm wrong
[OP] ashriv | 5 hours ago
taherchhabra | 6 hours ago
[OP] ashriv | 5 hours ago
ianberdin | 5 hours ago
samu123123 | 3 hours ago
MisterMunchkin | 3 hours ago
stevelacey | 2 hours ago
[OP] ashriv | an hour ago
green-frog-445 | an hour ago
agent_yard | 35 minutes ago