What is Twelve-Factor App?
The Twelve-Factor App methodology (by Adam Wiggins/Heroku) defines 12 principles for building scalable, maintainable cloud-native applications: 1.
The Twelve-Factor App methodology (by Adam Wiggins/Heroku) defines 12 principles for building scalable, maintainable cloud-native applications:
1. Codebase (one codebase tracked in VCS, many deploys) 2. Dependencies (explicitly declare and isolate) 3. Config (store in environment variables) 4. Backing services (treat as attached resources) 5. Build, release, run (strictly separate stages) 6. Processes (stateless, share-nothing) 7. Port binding (export services via port binding) 8. Concurrency (scale out via process model) 9. Disposability (fast startup, graceful shutdown) 10. Dev/prod parity (keep environments similar) 11. Logs (treat as event streams) 12. Admin processes (run as one-off processes)
These principles are the foundation of modern cloud-native development. Applications that follow twelve-factor principles deploy easily to any cloud platform.
Why It Matters
Twelve-factor is the minimum bar for cloud-native applications. Violating these principles creates deployment friction, scaling limitations, and operational complexity.
Frequently Asked Questions
What is a twelve-factor app?
12 principles for building scalable, portable cloud-native applications: one codebase, explicit dependencies, config in env vars, stateless processes, disposability, dev/prod parity, and more.
Is twelve-factor still relevant?
Absolutely. While the methodology is from 2012, the principles are foundational for Kubernetes, serverless, and container-based architectures. They remain the minimum bar for cloud-native development.
Related Terms
Need Expert Help?
Richard Ewing is a Product Economist and AI Capital Auditor. He helps companies translate technical complexity into financial clarity.
Book Advisory Call →