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.
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 box running my claude code 24/7. 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
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?
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.
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.
It’s been cool to see the evolution from vms to serverless agents.
I think it’s the right kind of innovation sort of like ec2, serverless functions, and etc in the age of ai
Is this similar or using CNCF's agent-substrate open source platform?
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
Fair! What did you build on AWS? What was the most time consuming part?
its basically a box running my claude code 24/7. 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
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?
How do you compare yourself with https://www.agent37.com/
Also, digitalocean offers this now.
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.
There are a lot of alternatives in the market for this.
Better landing page animation, of course.
Right now I'm using Grains.run -- it has toolbox, x402, custom tools, fs, memory, and more
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.
Is it bring your own FS?
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.