Lineage
Lineage and prior art
The software factory is a fifty-year-old idea, and the last chapter before the agents arrived already contained the lesson: software factories only scaled on top of a shared infrastructure platform. This page tells that story and lists who already uses the words.
Lineage
The Department of Defense learned this before the agents arrived
The software factory is a fifty-year-old idea. Its most instructive chapter is the last one before the agents: the US Air Force built software factories, then discovered that they only scaled on top of a shared infrastructure platform.
- 1968
The term is coined
Bob Bemer proposes the "software factory".23
- 1975
The first one runs
System Development Corporation operates its Software Factory.23
- 2004
The book
Jack Greenfield and Keith Short publish Software Factories with Wiley and Microsoft.23
- 2017
Kessel Run
The US Air Force launches "DOD's first software factory".22
- Dec 2019
Platform One
Established to "assist software factories by helping them focus on building mission applications": DevSecOps as a service, Kubernetes, Iron Bank hardened images and the Big Bang tooling.22
It was called a software factory. It was an infrastructure platform.
- 2021
The lesson, stated
Air Force CIO Lauren Knausenberger: "starting with Kessel Run smuggling DevSecOps into the DOD, and continuing with Platform One leading the way to Kubernetes, a common repo, and a desire to bring the entire community together and leverage common enterprise services."22
- 2025 to 2026
The agentic software factory
Factory.ai's "Factory 2.0" (June 2026)1, BCG Platinion's "Agentic Software Factory" (March 2026)2, StrongDM's no-human rules (February 2026)3 and Uber's "Running a Software Factory Efficiently at Uber Scale" (August 2026)6. In Factory.ai's words, "the incremental units of this system are AI agents."
- 2026 →
The Infrastructure Factory
The platform the agentic software factory runs on, named as a production system of its own, with its own line and its own metrics.
Platform engineering was never about Kubernetes. It was about letting factories run.
Prior art
What already exists, and what this is not
The term is open. Many have said since mid-2025 that the bottleneck moved from code to infrastructure delivery, and a few projects already use the words. The cloud providers say it from their side too: at re:Invent 2025, AWS and Cisco were "not looking for platform teams that are just vending out Kubernetes clusters".19
Who uses the words
| Usage | Who | What it means | Relation |
|---|---|---|---|
| InfraFactory24 | MozeBaltyk, open source on GitHub | "A factory for building cloud infrastructure, provider-agnostic and modular": OpenTofu, cloud-init, K3s or RKE2 and Flux to stamp out VMs and clusters. | A vending line |
| C.I. Factory, Capability Infrastructure Factory24 | bonometti718, open source on GitHub | "Machine-native infrastructure for autonomous AI agents": small verifiable capabilities such as an "Agent Economic Action Gate". | Adjacent, tiny |
| AI Factory | NVIDIA, Presidio and others | Physical accelerated datacenters that "convert energy into tokens". | Different thing |
| Account Factory, Account Factory for Terraform24 | AWS Control Tower, with HashiCorp | A Terraform pipeline that vends and customizes governed AWS accounts inside a landing zone. | A vending line |
| Subscription vending24 | Microsoft Azure Architecture Center | Bicep and Terraform modules that create workload landing zones at scale. | A vending line |
| Project factory24 | Google Cloud Foundation Fabric | A Terraform module that vends GCP projects from YAML. | A vending line |
| "A factory with multiple production lines"24 | Cellenza, Azure consultancy | Industrialized landing-zone delivery. | Closest precedent |
| Platform One22 | US Air Force | A "software factory" that in practice provides DevSecOps as a service, Kubernetes, hardened images and tooling to other software factories. | Lineage |
The symmetry is explicit
Both factories have inputs, production lines, quality gates and a throughput number. Nobody has drawn the second line next to the first.
The queue is non-technical
Cost center, compliance owner, data classification, on-call owner. Agents cannot sign them, so the factory encodes them as defaults, delegations and policies.
Platform engineering was never about Kubernetes
It was about letting factories run. Platform One proved it before the agents arrived.