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