github.com/maheshbr/terraform@v0.3.1-0.20141020033300-deec7194a3ea/website/source/intro/vs/custom.html.markdown (about) 1 --- 2 layout: "intro" 3 page_title: "Terraform vs. Custom Solutions" 4 sidebar_current: "vs-other-custom" 5 --- 6 7 # Terraform vs. Custom Solutions 8 9 Most organizations start by manually managing infrastructure through 10 simple scripts or web-based interfaces. As the infrastructure grows, 11 any manual approach to management becomes both error-prone and tedious, 12 and many organizations begin to home-roll tooling to help 13 automate the mechanical processes involved. 14 15 These tools require time and resources to build and maintain. 16 As tools of necessity, they represent the minimum viable 17 features needed by an organization, being built to handle only 18 the immediate needs. As a result, they are often hard 19 to extend and difficult to maintain. Because the tooling must be 20 updated in lockstep with any new features or infrastructure, 21 it becomes the limiting factor for how quickly the infrastructure 22 can evolve. 23 24 Terraform is designed to tackle these challenges. It provides a simple, 25 unified syntax, allowing almost any resource to be managed without 26 learning new tooling. By capturing all the resources required, the 27 dependencies between them can be resolved automatically so that operators 28 do not need to remember and reason about them. Removing the burden 29 of building the tool allows operators to focus on their infrastructure 30 and not the tooling. 31 32 Furthermore, Terraform is an open source tool. In addition to 33 HashiCorp, the community around Terraform helps to extend its features, 34 fix bugs and document new use cases. Terraform helps solve a problem 35 that exists in every organization and provides a standard that can 36 be adopted to avoid reinventing the wheel between and within organizations. 37 Its open source nature ensures it will be around in the long term. 38