| ▲ | ATechGuy2 41 minutes ago | |
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. | ||
| ▲ | ashriv 29 minutes ago | parent [-] | |
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. | ||