Something that’s been frustrating me about building agentic systems lately: the deployment gap is way bigger than people talk about. We’re at a point where an agent can build a genuinely useful app; backend, frontend, database schema, the works. But the moment it needs to actually run somewhere, you’re back to babysitting it. Spinning up infrastructure yourself, configuring DNS, writing Dockerfiles, navigating AWS consoles. The agent did the creative work. You’re doing the IT admin. And the gap is more specific than just “agents can’t deploy.” It’s that agents can’t own any of it. They can’t spin up their own database, purchase their own domain, create their own infrastructure, set up their own checkout flow, or deploy their own app. Every one of those steps requires a human to go click something somewhere. I’ve been digging into this problem and honestly the solutions out there right now are bad. Give your agent broad cloud credentials and pray. Build brittle wrappers around infra APIs. Accept that deploy is always a manual step. None of it is satisfying if you actually want full autonomy. The one thing I’ve found that’s genuinely thinking about this differently is BuildWithLocus, it’s a PaaS built specifically for agents as the primary user. No Dockerfiles, no AWS console, just an API your agent calls to deploy services, provision Postgres or Redis, buy and attach domains, the whole thing. Agents can even self-register and fund their own workspace. It’s early but it’s the first thing I’ve seen that takes the “agent as operator” model seriously rather than treating it as an afterthought. Curious if anyone else is hitting this wall or has found other approaches worth looking at. submitted by /u/IAmDreTheKid
Originally posted by u/IAmDreTheKid on r/ArtificialInteligence
You must log in or # to comment.