CloudMapper vs. HashiCorp Vagrant

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
CloudMapper
Score 0.0 out of 10
N/A
CloudMapper helps users to analyze Amazon Web Services (AWS) environments. It is used to check for correct configuration, examine IAM policies to identify admin users and roles, or principals with specific privileges, and looked for unused resources, and view network visualizations.N/A
HashiCorp Vagrant
Score 10.0 out of 10
N/A
Vagrant is a tool designed to create and configure lightweight, reproducible, and portable development environments. It leverages a declarative configuration file which describes all software requirements, packages, operating system configuration, and users.N/A
Pricing
CloudMapperHashiCorp Vagrant
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
CloudMapperHashiCorp Vagrant
Free Trial
NoNo
Free/Freemium Version
YesYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
CloudMapperHashiCorp Vagrant
Considered Both Products
CloudMapper

No answer on this topic

HashiCorp Vagrant
Chose HashiCorp Vagrant
Docker has a few advantages, especially with the disk size bloat brought on by Vagrant's hosting an entire OS and project in a VM. It relies on native tools, however, and may not support every software.
Vagrant provides uniformity, efficiency and repeatability within team work …
Chose HashiCorp Vagrant
Fast[er] to implement than Docker. Even consuming a lot of resources, consume less resources than Docker. Cheaper than Azure, since [it] is free.
Chose HashiCorp Vagrant
I liked lando better because lando seemed extremely easy to setup compared to other VM's and it seemed faster though that project was simpler. Virtualbox I ran on windows and it has a gui and has often been slow. The vagrant boxes I used did well but had slightly more …
Chose HashiCorp Vagrant
Docker feels lighter, faster, but Vagrant offers better support across platforms, which is a must in my company where there are users on Linux, Mac OS and Windows.
Chose HashiCorp Vagrant
Virtualbox and VMware were easier products to set up but did not stack up against Vagrant with the customization and the ability to specifically test and work with our code base. Virtualbox and VMware were more generic solutions that may be easier but they did not fulfill the …
Chose HashiCorp Vagrant
MAMP is a much simpler solution than Vagrant. Pretty much anyone should be able to get MAMP up and running quickly, and it's much easier to maintain. However, MAMP is fairly limited to specific versions of software and runs within macOS, so it won't always completely be an …
Chose HashiCorp Vagrant
Previously I had used MAMP and DesktopServer. MAMP was constantly giving me MySQL problems and is frustrating in that it limits how many installs you can have. DesktopServers was a little better, but broke when i switched to High Sierra OSX. Their website and support were very …
Chose HashiCorp Vagrant
I like Vagrant much more than Docker. In my opinion it's easier and more flexible to configure a Vagrant machine how i like it compared to Docker. Of course Docker executes faster, but with Vagrant only the machine creation or booting process is slower, normally you don't …
Chose HashiCorp Vagrant
There's not much that I'm aware of that really does exactly what Vagrant does. Many of its tasks could be accomplished manually or via custom scripts. However, with Vagrant, automation is within easy grasp as well as a large community of experts who have pre-built solutions …
Chose HashiCorp Vagrant
Vagrant is a little different than other options out there. It blurs the lines between the server environment and the local environment. Options like MAMP and XAMPP allow a developer to run a local version of Apache, MySQL and PHP locally, but it's all based on the local …
Chose HashiCorp Vagrant
Vagrant is more of a meta-tool compared to traditional VM software. It provides a layer on top of VMware or VirtualBox. Configurations in a Vagrantfile are so much easier to manage than complete VMs.
Chose HashiCorp Vagrant
In comparison to Docker, Vagrant is a lot easier to create its [containers] boxes, than it is with Docker. Our company already dealt with and its devops team knew somewhat well the way of Vagrant, so it was quite natural to go Vagrant when trying to choose which would be our …
Chose HashiCorp Vagrant
By default Vagrant uses VirtualBox but compared to using VirtualBox directly, I've found using Vagrant makes things easier. For one, you can commit your Vagrant configuration to GitHub and manage changes that way. I'm not sure how you'd handle updated virtual machines to all …
Best Alternatives
CloudMapperHashiCorp Vagrant
Small Businesses
HashiCorp Terraform
HashiCorp Terraform
Score 8.5 out of 10
HashiCorp Terraform
HashiCorp Terraform
Score 8.5 out of 10
Medium-sized Companies
Ansible
Ansible
Score 9.2 out of 10
Ansible
Ansible
Score 9.2 out of 10
Enterprises
Ansible
Ansible
Score 9.2 out of 10
Ansible
Ansible
Score 9.2 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
CloudMapperHashiCorp Vagrant
Likelihood to Recommend
-
(0 ratings)
8.0
(0 ratings)
Likelihood to Renew
-
(0 ratings)
9.0
(0 ratings)
Usability
-
(0 ratings)
5.5
(0 ratings)
User Testimonials
CloudMapperHashiCorp Vagrant
Likelihood to Recommend
No answers on this topic
If you're writing software, particularly software that depends on other services (web servers or databases for example) then Vagrant is great. I know some people skip Vagrant and just set up virtual machines on their own, but I've found that Vagrant streamlines the process nicely and makes it easy to update or swap out versions. If you're a web developer (which I am) it's amazing. I can have several boxes configured for my different projects and I just spin them up or down based on what I'm working on. One scenario where this might not be ideal is if you're running Vagrant on a computer that has limited resources. Since you're running a virtual machine with its own operating system and such you'll want a host computer with enough RAM, hard drive space and CPU to run the virtual machine properly without killing the performance of the host. The virtual disks can also take up a lot of space if you're not careful so if you have many virtual machines provisioned and don't clean up the old ones that you're not using, you may find that your hard drive is full. Each of my Linux servers take up about 10GB of disk space.
Read full review
Pros
No answers on this topic
  • Easy to create machines with different OS's, list of them can be found from Vagrant's website with configuration details.
  • Flexible configuration, user can determine what software will be pre-installed to machine. Saves time because it doesn't need to be done manually every time.
  • Easily manage full environments, not just single machines, with single command.
Read full review
Cons
No answers on this topic
  • Learning curve is steep - It can be challenging for someone to set up initially. After some coaching, the basics come pretty quickly though.
  • Relies on external Virtual Machine applications - It would be great if Vagrant itself could run the virtual machine instead of leaning on other virtualization software. This is a small detail, but would make setup simple.
  • Better support for running
Read full review
Likelihood to Renew
No answers on this topic
Vagrant is fast, versatile and does exactly what we need it to do: spin up virtual servers for local development fast and without trouble.
Read full review
Usability
No answers on this topic
A GUI would be nice for entry level users.
Read full review
Alternatives Considered
No answers on this topic
Docker has a few advantages, especially with the disk size bloat brought on by Vagrant's hosting an entire OS and project in a VM. It relies on native tools, however, and may not support every software. Vagrant provides uniformity, efficiency and repeatability within team work and for deployment and testing.
Read full review
Return on Investment
No answers on this topic
  • Saved lots of time by being able to set up a local env quickly
  • Occasionally made troubleshooting bugs harder than it would have been using native Linux
  • Clients had issues setting it up, which may have provided us some security in keeping their business
Read full review
ScreenShots