60 points by ashriv 1 day ago | 61 comments | View on ycombinator
kingefman1 about 4 hours ago |
chandureddyvari 1 day ago |
Let me explain my current setup. We have something like muse/instinct/dots equivalent built for our customers(GTM domain), so each of them gets an agent with a VM (sandbox - currently using daytona). The sessions and the context (skills, instructions, hooks etc.) are synced to R2. Daytona(2GB ram, 3GB disk, 1vcpu) is working out good for us, cold starts are <500ms, whereas warm ones (non-archived sanboxes) are much lesser. Current problems we are facing is around agent swarms or sub-agents or multiple sessions from same customer (teams trying to interact) - we needed to manage the daytona sandbox sizing on this.
If I were to use maritime, what'd be different for me? Would I be paying $1/mo per customer agent? I can just move my harness to maritime and stop managing sandboxes, R2 sync etc.?
Another company I wanted to checkout is Omnara(another YC company), but Maritime felt closer to my task.
ATechGuy2 1 day 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.
hmokiguess 1 day 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
tobiaszander about 21 hours ago |
alexkubit about 14 hours ago |
agent_yard 1 day ago |
binsquare 1 day ago |
I think it’s the right kind of innovation sort of like ec2, serverless functions, and etc in the age of ai
bill10 1 day ago |
bitlad 1 day ago |
Also, digitalocean offers this now.
volkk 1 day 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
MisterMunchkin 1 day ago |
sgtwompwomp 1 day ago |
ansh25lehri 1 day ago |
ianberdin 1 day ago |
aqibkhan026 1 day ago |
cidd 1 day ago |
stevelacey 1 day ago |
taherchhabra 1 day ago |
jen729w 1 day ago |
momojo 1 day ago |
fvrshaibu 1 day ago |
vasco 1 day ago |
0x0000F8 1 day 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.
Junzzzhu 1 day ago |
The two failure modes I would want a managed platform to handle by default are (1) an injected instruction in a fetched page or a customer email telling the agent to send data somewhere, and (2) a long-lived provider key sitting inside the VM where the agent, or anything it runs, can read it. Two patterns that seem to hold up: an egress allowlist enforced outside the VM rather than in the agent's own config, and giving the VM a scoped, revocable token that a proxy exchanges for the real key, so a leaked token has a spend cap and a kill switch.
Do you do either of those today, or is that left to the customer's harness?