ControlMonkey Platform

What do you like best about the product?

ControlMonkey gives us significantly better visibility and control over our cloud environments.

Our DevOps team supports multiple internal teams, each with different infrastructure needs. We operate mainly on AWS, and most of our infrastructure is managed through Terraform, Terragrunt, OpenTofu, and Crossplane.

Before ControlMonkey, managing everything was more challenging. We had several Terraform codebases, different Terraform versions, and a mix of pipeline-based and manual deployments. It wasn’t always clear what had changed, where drift existed, or whether our environments were fully aligned with our IaC.

After onboarding our environments to ControlMonkey, we gained much better control. The drift alerts helped us catch changes we didn’t know were happening, including cloud provider changes, automatic upgrades, and limited manual changes in sensitive environments.

We also use ControlMonkey to manage GitHub repositories and configuration as IaC, which made repository creation and configuration more structured, consistent, and easier to govern.

Overall, the product simply works. Our cooperation with the ControlMonkey team has also been excellent—they’re responsive, practical, and genuinely care about our feedback and use cases.

What do you dislike about the product?

Nothing major at this point. The product has been working well for our needs.

One area that could be useful for us is more flexible grouping of namespaces, especially as more teams and environments are onboarded. Overall, the core functionality is strong and the team has been very responsive to feedback.

What problems is the product solving and how is that benefiting you?

ControlMonkey helps us solve visibility, drift detection, and control across cloud infrastructure and IaC.

Before using it, our environment was harder to manage because we had several Terraform codebases, different versions, and a mix of manual and automated deployments. That created gaps in visibility and made it harder to know if the real cloud state matched the intended IaC state.

With ControlMonkey, we have much better control over onboarded environments. We get alerts on drift, including changes caused by automatic cloud provider updates or limited manual work. This helps us reduce surprises and react faster when something changes outside the expected process.

It gives us a more reliable way to manage infrastructure, keep our cloud configuration closer to the expected state, and improve confidence in our IaC process.

What do you like best about the product?

What used to take days now takes minutes, I feel confident working with them and suggest to customers their solution

What do you dislike about the product?

One of the biggest benefits for our customers is how much manual work it removed from recovery situations. Before, it depended a lot on who was available and what they remembered. Now they have snapshots and a clearer path to recovery, which takes a lot of pressure off the team when something goes wrong.

What problems is the product solving and how is that benefiting you?

Before ControlMonkey, customers didn’t have a reliable way to reconstruct our infrastructure after an issue. Now they have consistent snapshots and a repeatable recovery process, which made our overall disaster recovery approach much stronger.

What do you like best about the product?

Extremely fast at delivering new backup features. If you’re using a third party that has a Terraform provider and you realize you don’t have IaC, no problem—get CM on their case and they’ll get you a daily backup of the entire vendor stack within a week or two. That’s amazing.

What do you dislike about the product?

The stored IaC is raw and not directly usable in its current form. It would be great to have a generic way to store module inputs instead, so that the backed-up IaC can be reapplied directly.

What problems is the product solving and how is that benefiting you?

Control Monkey backs up our entire cloud infrastructure, along with many of our vendors, in GitHub. I hope I don’t need to explain how beneficial that is for any company.

ControlMonkey  has been used for managing resources across multi-region accounts and large-scale infrastructure in AWS , with the goal of achieving easy control of the resources and the easiest way to manage them.

ControlMonkey  has impacted our organization positively so far, as it was really difficult to manage multi-region accounts and now it is easier to have AWS  accounts in different regions that can communicate.

We have seen a decrease in errors by 5% so far, which shows how things have improved with ControlMonkey.

The multi-region support is what we have been looking for, so that is the most important feature. ControlMonkey is easy to use when it comes to the features.

There is not much to improve at this time regarding how ControlMonkey can be improved.

I have tried ControlMonkey since a couple of weeks ago.

ControlMonkey appears to be stable.

ControlMonkey's scalability is performing quite well.

Customer support has not been used yet.

I did not previously use a different solution, as everything was customized and directly made by the engineers.

I did not evaluate other options before choosing ControlMonkey.

We are a partner with this vendor other than just being a customer.

There has been a return on investment, as there was a decrease of time spent on managing the infrastructure by 20%.

The experience with pricing, setup cost, and licensing was that it was easy to understand and aligned with the expectations.

ControlMonkey was purchased through the AWS Marketplace .

ControlMonkey is good to try to see if it can make an improvement. The overall review rating for this product is 8.

Public Cloud

Amazon Web Services (AWS)

What do you like best about the product?

Many of our AWS networking resources were not managed with Terraform Code, leaving us with no easy way to roll back configuration when needed.
ControlMonkey's Terraform Import Engine connected to our AWS accounts in minutes, and with a few clicks, we automatically generated the Terraform Code that represented our existing configuration.
We now have a DRP for our networking architecture, and we also utilize ControlMonkey to identify drifts from our desired networking configuration.

What do you dislike about the product?

Currently supporting only Terraform/OpenTofu/Terragrunt. I’d like to see them supporting more IaC Frameworks.

What problems is the product solving and how is that benefiting you?

ControlMonkey helped us shift all of our networking resources to Terraform, and we now have a DRP in place in case we need to roll back our networking configuration.