StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Continuous Deployment
  4. Server Configuration And Automation
  5. Metamon vs Terraform

Metamon vs Terraform

OverviewDecisionsComparisonAlternatives

Overview

Terraform
Terraform
Stacks22.9K
Followers14.7K
Votes344
GitHub Stars47.0K
Forks10.1K
Metamon
Metamon
Stacks0
Followers3
Votes0
GitHub Stars337
Forks15

Metamon vs Terraform: What are the differences?

Metamon: A Vagrant/Ansible toolkit for kickstarting Django apps. Metamon is a Vagrantfile combined with a set of Ansible Playbooks which can be used to quickly start a new Django project. Although Metamon is easily extensible by adding new Ansible roles, it is a better fit for people who use Django + Gunicorn + Nginx + PostgreSQL; Terraform: Describe your complete infrastructure as code and build resources across providers. With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.

Metamon and Terraform can be categorized as "Infrastructure Build" tools.

Some of the features offered by Metamon are:

  • Create an Ubuntu 14.04 machine.
  • Set-up basic Operating system dependencies.
  • Set-up a Virtualenv and automatically install dependencies.

On the other hand, Terraform provides the following key features:

  • Infrastructure as Code: Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and treated as you would any other code. Additionally, infrastructure can be shared and re-used.
  • Execution Plans: Terraform has a "planning" step where it generates an execution plan. The execution plan shows what Terraform will do when you call apply. This lets you avoid any surprises when Terraform manipulates infrastructure.
  • Resource Graph: Terraform builds a graph of all your resources, and parallelizes the creation and modification of any non-dependent resources. Because of this, Terraform builds infrastructure as efficiently as possible, and operators get insight into dependencies in their infrastructure.

Metamon and Terraform are both open source tools. Terraform with 17.7K GitHub stars and 4.83K forks on GitHub appears to be more popular than Metamon with 348 GitHub stars and 15 GitHub forks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Terraform, Metamon

Sung Won
Sung Won

Nov 4, 2019

DecidedonGoogle Cloud IoT CoreGoogle Cloud IoT CoreTerraformTerraformPythonPython

Context: I wanted to create an end to end IoT data pipeline simulation in Google Cloud IoT Core and other GCP services. I never touched Terraform meaningfully until working on this project, and it's one of the best explorations in my development career. The documentation and syntax is incredibly human-readable and friendly. I'm used to building infrastructure through the google apis via Python , but I'm so glad past Sung did not make that decision. I was tempted to use Google Cloud Deployment Manager, but the templates were a bit convoluted by first impression. I'm glad past Sung did not make this decision either.

Solution: Leveraging Google Cloud Build Google Cloud Run Google Cloud Bigtable Google BigQuery Google Cloud Storage Google Compute Engine along with some other fun tools, I can deploy over 40 GCP resources using Terraform!

Check Out My Architecture: CLICK ME

Check out the GitHub repo attached

2.25M views2.25M
Comments
Timothy
Timothy

SRE

Mar 20, 2020

Decided

I personally am not a huge fan of vendor lock in for multiple reasons:

  • I've seen cost saving moves to the cloud end up costing a fortune and trapping companies due to over utilization of cloud specific features.
  • I've seen S3 failures nearly take down half the internet.
  • I've seen companies get stuck in the cloud because they aren't built cloud agnostic.

I choose to use terraform for my cloud provisioning for these reasons:

  • It's cloud agnostic so I can use it no matter where I am.
  • It isn't difficult to use and uses a relatively easy to read language.
  • It tests infrastructure before running it, and enables me to see and keep changes up to date.
  • It runs from the same CLI I do most of my CM work from.
385k views385k
Comments
Hendrik
Hendrik

CEO at Forward H

Dec 13, 2021

Decided

Terraform provides a cloud-provider agnostic way of provisioning cloud infrastructure while AWS CloudFormation is limited to AWS.

Pulumi is a great tool that provides similar features as Terraform, including advanced features like policy and cost management.

We see that Terraform has great support in the cloud community. For most cloud services we use, there is an official Terraform provider. We also believe in the declarative model of HCL, which is why we chose Terraform over Pulumi. However, we still keep an eye on Pulumi's progress.

Ansible is great for provisioning software and configuration within virtual machines, but we don't think that Ansible is the right tool for provisioning cloud infrastructure since it's built around the assumption that there is an inventory of remote machines. Terraform also supports more services that we use than Ansible.

22.2k views22.2k
Comments

Detailed Comparison

Terraform
Terraform
Metamon
Metamon

With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.

Metamon is a Vagrantfile combined with a set of Ansible Playbooks which can be used to quickly start a new Django project. Although Metamon is easily extensible by adding new Ansible roles, it is a better fit for people who use Django + Gunicorn + Nginx + PostgreSQL.

Infrastructure as Code: Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and treated as you would any other code. Additionally, infrastructure can be shared and re-used.;Execution Plans: Terraform has a "planning" step where it generates an execution plan. The execution plan shows what Terraform will do when you call apply. This lets you avoid any surprises when Terraform manipulates infrastructure.;Resource Graph: Terraform builds a graph of all your resources, and parallelizes the creation and modification of any non-dependent resources. Because of this, Terraform builds infrastructure as efficiently as possible, and operators get insight into dependencies in their infrastructure.;Change Automation: Complex changesets can be applied to your infrastructure with minimal human interaction. With the previously mentioned execution plan and resource graph, you know exactly what Terraform will change and in what order, avoiding many possible human errors
Create an Ubuntu 14.04 machine.;Set-up basic Operating system dependencies.;Set-up a Virtualenv and automatically install dependencies.;Set-up Supervisor, PostgreSQL 9.3, Gunicorn and Nginx.;Start a new Django project if it's needed.;Automatically activate a virtualenv and cd to the project's directory when logging in during development.;Use separate requirements files for faster deploys.;Separate settings file for unit testing with coverage and customized settings to make testing faster.
Statistics
GitHub Stars
47.0K
GitHub Stars
337
GitHub Forks
10.1K
GitHub Forks
15
Stacks
22.9K
Stacks
0
Followers
14.7K
Followers
3
Votes
344
Votes
0
Pros & Cons
Pros
  • 121
    Infrastructure as code
  • 73
    Declarative syntax
  • 45
    Planning
  • 28
    Simple
  • 24
    Parallelism
Cons
  • 1
    Doesn't have full support to GKE
No community feedback yet
Integrations
Heroku
Heroku
Amazon EC2
Amazon EC2
CloudFlare
CloudFlare
DNSimple
DNSimple
Microsoft Azure
Microsoft Azure
Consul
Consul
Equinix Metal
Equinix Metal
DigitalOcean
DigitalOcean
OpenStack
OpenStack
Google Compute Engine
Google Compute Engine
Ansible
Ansible
Django
Django
Vagrant
Vagrant
VirtualBox
VirtualBox

What are some alternatives to Terraform, Metamon?

Ansible

Ansible

Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.

Chef

Chef

Chef enables you to manage and scale cloud infrastructure with no downtime or interruptions. Freely move applications and configurations from one cloud to another. Chef is integrated with all major cloud providers including Amazon EC2, VMWare, IBM Smartcloud, Rackspace, OpenStack, Windows Azure, HP Cloud, Google Compute Engine, Joyent Cloud and others.

Capistrano

Capistrano

Capistrano is a remote server automation tool. It supports the scripting and execution of arbitrary tasks, and includes a set of sane-default deployment workflows.

Puppet Labs

Puppet Labs

Puppet is an automated administrative engine for your Linux, Unix, and Windows systems and performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.

Salt

Salt

Salt is a new approach to infrastructure management. Easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in seconds. Salt delivers a dynamic communication bus for infrastructures that can be used for orchestration, remote execution, configuration management and much more.

AWS CloudFormation

AWS CloudFormation

You can use AWS CloudFormation’s sample templates or create your own templates to describe the AWS resources, and any associated dependencies or runtime parameters, required to run your application. You don’t need to figure out the order in which AWS services need to be provisioned or the subtleties of how to make those dependencies work.

Fabric

Fabric

Fabric is a Python (2.5-2.7) library and command-line tool for streamlining the use of SSH for application deployment or systems administration tasks. It provides a basic suite of operations for executing local or remote shell commands (normally or via sudo) and uploading/downloading files, as well as auxiliary functionality such as prompting the running user for input, or aborting execution.

AWS OpsWorks

AWS OpsWorks

Start from templates for common technologies like Ruby, Node.JS, PHP, and Java, or build your own using Chef recipes to install software packages and perform any task that you can script. AWS OpsWorks can scale your application using automatic load-based or time-based scaling and maintain the health of your application by detecting failed instances and replacing them. You have full control of deployments and automation of each component

Packer

Packer

Packer automates the creation of any type of machine image. It embraces modern configuration management by encouraging you to use automated scripts to install and configure the software within your Packer-made images.

Scalr

Scalr

Scalr is a remote state & operations backend for Terraform with access controls, policy as code, and many quality of life features.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana