The Twelve-Factor App: 12 Rules Your App Is Probably Breaking Right Now

Last Updated on July 27, 2026 by Editorial Team Author(s): Rohan Mistry Originally published on Towards AI. Written in 2011. Older than Docker. Still the checklist every cloud-native app is quietly judged against. In 2011, Adam Wiggins, co-founder of Heroku, noticed something while running thousands of apps on his platform. After that opening, the article walks through the “Twelve-Factor App” guidelines, explaining why each factor matters for building cloud-native software: a single codebase deployed across environments, explicit and isolated dependencies, configuration provided via the environment (not code), external backing services treated as swappable resources, and a strict build/release/run pipeline with immutable releases. It also covers stateless processes for reliable horizontal scaling, port binding so the app is truly self-contained, concurrency via scaling out processes, and disposability with fast startup plus graceful shutdown. Further, it emphasizes dev/prod parity to reduce “works locally” surprises, logs emitted as event streams to integrate with the observability stack, and admin tasks executed as one-off processes in the same environment as the app. The piece concludes with an update noting what evolved since 2011—more emphasis on observability beyond logs, richer configuration and secrets management, and the fact that security and API concerns aren’t explicitly covered in the original list. Read the full blog for free on Medium. Join thousands of data leaders on the AI newsletter. Join over 80,000 subscribers and keep up to date with the latest developments in AI. From research to projects and ideas. If you are building an AI startup, an AI-related product, or a service, we invite you to consider becoming a sponsor. Published via Towards AI