The world of software development is undergoing a profound transformation, driven by the rise of coding agents and the shift towards multi-tenancy. The traditional approach of providing a per-developer environment is no longer sufficient as developers now run multiple agent sessions simultaneously, leading to a surge in changes in flight. This has led to a reevaluation of the concept of the tenant, with the focus shifting from the developer to the change itself. The new tenant is the change, not the agent, and this has significant implications for platform engineering and the software development lifecycle (SDLC).
The traditional approach of providing a per-developer environment is no longer sufficient as developers now run multiple agent sessions simultaneously, leading to a surge in changes in flight. This has led to a reevaluation of the concept of the tenant, with the focus shifting from the developer to the change itself. The new tenant is the change, not the agent, and this has significant implications for platform engineering and the software development lifecycle (SDLC).
The traditional approach of providing a per-developer environment is no longer sufficient as developers now run multiple agent sessions simultaneously, leading to a surge in changes in flight. This has led to a reevaluation of the concept of the tenant, with the focus shifting from the developer to the change itself. The new tenant is the change, not the agent, and this has significant implications for platform engineering and the software development lifecycle (SDLC).
The new tenant is the change, not the agent, and this has significant implications for platform engineering and the software development lifecycle (SDLC). The traditional approach of providing a per-developer environment is no longer sufficient as developers now run multiple agent sessions simultaneously, leading to a surge in changes in flight. This has led to a reevaluation of the concept of the tenant, with the focus shifting from the developer to the change itself.
The new tenant is the change, not the agent, and this has significant implications for platform engineering and the software development lifecycle (SDLC). The traditional approach of providing a per-developer environment is no longer sufficient as developers now run multiple agent sessions simultaneously, leading to a surge in changes in flight. This has led to a reevaluation of the concept of the tenant, with the focus shifting from the developer to the change itself.
The new tenant is the change, not the agent, and this has significant implications for platform engineering and the software development lifecycle (SDLC). The traditional approach of providing a per-developer environment is no longer sufficient as developers now run multiple agent sessions simultaneously, leading to a surge in changes in flight. This has led to a reevaluation of the concept of the tenant, with the focus shifting from the developer to the change itself.
The practical shift for platform teams starts with measurement. Count changes in flight at peak, not seats: open pull requests with activity in the last day is a fine proxy, and for most teams the number is already several times headcount. Then price the marginal tenant: What does one more concurrent change cost in dollars and in minutes of setup? If the answer is a full environment and tens of minutes, the platform is still doing person-level tenancy.
The tenant owns what changed and shares everything else. A SaaS tenant owns its data and configuration, never a copy of the application. A change tenant is sized the same way. It owns the one or two services it modified and an isolated database branch it can migrate and write against, and nothing else. Everything the change did not touch resolves against one shared stable environment, continuously deployed from main, so every tenant validates against real, current dependencies without owning a copy of them.
The durable unit is the change. It comes into existence when work on it starts. It accumulates state that no other tenant should see: a schema migration, test writes, new versions of one or two services, the messages it produced during validation. It needs to observe a version of the system that includes its own edits and nobody else’s. And it is torn down when it merges or is abandoned, taking all of that state with it.
The tenant comes into existence when work on the change starts and disappears when the change merges or is abandoned, with no ticket at the front and no cleanup script at the back. Offboarding is the half that platform teams underestimate. At person scale, an orphaned environment was a minor waste found in a quarterly cleanup. At change scale, orphans accumulate as fast as agents abandon experiments, and the leak outgrows the cleanup.
The tenant is the change, not the agent, and this has significant implications for platform engineering and the software development lifecycle (SDLC). The traditional approach of providing a per-developer environment is no longer sufficient as developers now run multiple agent sessions simultaneously, leading to a surge in changes in flight. This has led to a reevaluation of the concept of the tenant, with the focus shifting from the developer to the change itself.
The tenant is the change, not the agent, and this has significant implications for platform engineering and the software development lifecycle (SDLC). The traditional approach of providing a per-developer environment is no longer sufficient as developers now run multiple agent sessions simultaneously, leading to a surge in changes in flight. This has led to a reevaluation of the concept of the tenant, with the focus shifting from the developer to the change itself.
