infrastructure service like DataDog, Vercel, Superbase. Uh, all of these services run into the same problems. You start off with a shiny piece of software. And this piece of software can service a single customer pretty well. Um, maybe it's running on your machine. If you're working for NLB, it should be a load balancer, right? If you're working for AWS Lambda, it'd be some sort of serverless runtime. But, uh, it needs to actually run somewhere. So, if you're infrastructure engineer, next step is you get into resource provisioning. Um, and this is already where the single node sandbox starts breaking down. How do you provision resources within a single sandbox? You can't exactly simulate something like EC2 or Cloud Run, right? Um, so you get into this host provisioning. Uh, it also includes provisioning of other resources like VPCs, subnets, security groups. Um, and you need to expose this through some sort of API because your customers are going to want to do things like, "Oh, give me this shiny piece of software." Or, "I don't want it anymore. It cost too much. I'm going bankrupt. Delete it, please." Um, and so you're going to need some sort of front-end API. And if you have enterprise grade customers who really care about quality, then you're going to have to meet certain bars like throttling, authentication, authorization. You can't really like go without these things, right? Uh, if you're AWS, then that's CloudTrail, too. Um, and then beyond this, uh, software is living. People forget this all the time, especially like investors, right? Like they'll be like, "Oh, you wrote it. You're done." Um, but software is living and you probably need some sort of software deployment component as well. Uh something whenever you have an update to roll out roll it out. Um and God forbid something goes wrong, roll it back. Uh you need to manage all the different versions and make sure your deployments are gradual to limit your blast radius. And we're just kind of getting started with this. There's all sorts of things that you need to think about like health monitoring with awareness for network partitions. Uh and then how do you communicate with your host so you can change configs on the fly. Um maybe your customer actually wants to call your endpoint, so you need DNS and cert management. And then, you know, your our service grows a bunch, you need to keep track of all your resources, what's going on, fraud and stuff, then you need admin consoles, uh telemetry, billing if you're making money, um all sorts of things. And with all of this, I think there's like one more slide for is it scheduling? Yeah. Um >> I think the point is fairly clear at this point. Beyond beyond a certain threshold, there is a critical mass at which sandboxing on a single node uh can only get you so far. And that's why we envision the the