Gearset DevOps Reviews & Product Details

Our onboarding has been FANTASTIC. As a team of only admins we were unfamiliar with typical devops processes, but we were really set up for success to use all the tools Gearset has to offer and convert almost 100% of our development and building time to be in conjunction with Gearset tools. Review collected by and hosted on G2.com.

I think when I was brand new to the platform, I was a little confused by how many similar tools there were. There are a lot of ways to do the same thing, so we really relied on the training resources to help us understand the differences and when it made sense to use each tool. Review collected by and hosted on G2.com.

I like Gearset’s new Cam AI agent because it could help our Salesforce team move faster while keeping changes under review. Gearset Org Intelligence looks useful for tracing metadata dependencies before we change a Flow or field. gearset.com The new automated UI testing could reduce manual checks during releases. assets.gearset.com Gitflow support in Pipelines gives teams more flexibility in how they manage releases. Gearset The Jira ticket improvements should make it easier to see which work is included in a release. Review collected by and hosted on G2.com.

Make deployment errors easier to understand, with clearer steps to resolve them. Show the likely impact of a change across Flows, fields, Apex, and integrations before deployment. Make it easier to group and track everything tied to one Jira ticket through UAT and production. Give release managers a clearer view of what passed testing and what still needs review. Make rollback steps more visible and easier to prepare before a production release. Review collected by and hosted on G2.com.

The UI is user-friendly, the AI agent is good, and the event monitoring works well. Their support team is Awesome. Integrations are also good. They have different options to optimize the performance for the deployment. Review collected by and hosted on G2.com.

Configuration complexity: For larger projects, the setup can be intricate and often requires careful planning, ongoing maintenance, and attention to detail.

Dependency management: Salesforce metadata dependencies can still be complicated, and I sometimes end up needing to troubleshoot them manually to resolve issues. Review collected by and hosted on G2.com.

Rollbacks, easy to resolve conflicts when working on overlapping components, precise deployments of only necessary metatada (like not having to push an entire page), easy management of a proper dev pipeline that encourages best CI/CD practices Review collected by and hosted on G2.com.

We would all like for it to be able to be faster, but it is getting better, and vastly better than traditional tools. I would like to be able to more easily accommodate refreshing sandboxes in the pipeline (or hot-swapping). No real dislikes, just feature requests, I guess! Review collected by and hosted on G2.com.

Pipeline functionality is amazing. Work has been simplified and changes are being released more easily, but also very controlled from the checks Gearset performs. Observability is also a key feature for us that we are still implementing Salesforce and need to have an update of the most common issues and errors users are having. Review collected by and hosted on G2.com.

It is not a dislike, rather a potential drawback that sometimes the amount of time of the comparison or verification takes more time than expected. But this could also be related to the amount of filters that we are using with metadata types. Review collected by and hosted on G2.com.

What I like best about Gearset DevOps is how powerful it is. It gives me excellent visibility into merge requests, deployments, merge conflicts, code reviews, and rollback options, making the entire release process much easier to manage. The automation and overall workflow have significantly improved our development and deployment process. It’s an incredibly capable platform and has become an essential part of our DevOps toolkit. Review collected by and hosted on G2.com.

My biggest frustration is that some new features are released as trials and later require an additional paid upgrade to continue using them. I would prefer that platform enhancements and new functionality be included with the existing subscription rather than becoming separate add-ons. Review collected by and hosted on G2.com.

What stands out the most to me is how intuitive and easy to use the interface is. Managing, comparing, and updating Salesforce orgs is remarkably smooth and straightforward, which saves a lot of time during everyday deployment workflows. Review collected by and hosted on G2.com.

My main issue is that when creating a Pull Request, it doesn't show the code differences immediately in place, forcing you to navigate elsewhere to review them. Additionally, it lacks direct integrations or plugins for code editors like Visual Studio Code, which would make the developer workflow much more seamless. Review collected by and hosted on G2.com.

In my opinion, the best part of gearset is the ability to precisely deploy your changes. Meaning I can select specific changes that I made within each component and I can exclude any changes that are part of someone else's changes in the same component.

This has made it so that if one person's changes are deploying before another's changes, they can without having to spend a great deal of time or rework getting one version ready for deployment.

We previously used a tool that when you committed a component it committed everything including all changes. So if one set of changes had to deploy first, we had to go in and remove or comment out the other persons changes, Commit it again and then we could deploy it. Then we had to go in and replace or uncomment the changes we removed. Review collected by and hosted on G2.com.

Because of the size of our org, comparisons are slow. In addition, when deploying to Sandboxes it takes the following steps.

1) Does something in the backend not sure what, but it can take anywhere from 2-15 minutes before it starts actually doing step 2 in Salesforce.

2) Validates in Salesforce (depending on the size of the deployment and performance of Salesforce this can take quite some time)

3) Then it commits the changes in our Version Control System (VCS)

4) Deploys in Salesforce (using quick deploy if possible, but again depending on the size of the deployment and performance of Salesforce this can take quite some time)

In theory we could skip step 2 but then if there is a failure in the deployment GIT is already updated. I would much rather it deploy, then update GIT if it succeeds. That way they don't need to do a validate AND a Deploy in Salesforce.

Also for Step 1 to give an example, we have a weekly release to Production that has to be done after hours starting at 7:00 PM. I have had to schedule it to start at 6:45 PM and when I log in at 7:00 it is JUST barely starting the actual deployment in Salesforce. Review collected by and hosted on G2.com.

I like the precision deployments and how it highlights dependencies for you. Review collected by and hosted on G2.com.

There’s been quite a bit of apprehension about dev orgs not being synced until after features are deployed to production. I’m not sure yet whether this will actually cause problems for us, but it’s definitely something we need to keep an eye on and monitor closely. Review collected by and hosted on G2.com.

The core deployment process is straightforward and comes with a variety of admin-focused features that many other Salesforce DevOps companies simply don’t provide. It also offers a broad set of useful tools for managing the metadata lifecycle end to end. On top of that, the customer support team is a real strength: they’re professional, responsive, and genuinely helpful when you’re navigating the platform’s features. Review collected by and hosted on G2.com.

There are several significant drawbacks for our specific workflow. To start, having to work in a separate application outside of Salesforce adds an extra step and breaks up our process. We also found that the CI/CD functionality didn’t fit our needs, even after a long POC; overall, it felt buggy and lacked a native back-promotion option. In addition, the deployment process doesn’t support auto-merging: it stops at every conflict during the comparison, which forces us to manually resolve conflicts and make selections each time. Finally, the lack of an external API is a major limitation because it prevents us from integrating Gearset with our custom pipelines or other external tools. Review collected by and hosted on G2.com.