Deploy

No. Gearset uses secure OAuth to enable connections to your Salesforce orgs. There’s nothing to install in your orgs, and Gearset doesn’t have access to or store your credentials.

You can link to as many of your Salesforce orgs as you need. You can also delegate specific access levels to your teammates, so they can compare and/or deploy to and from your orgs, helping you collaborate whatever your team size.

Gearset’s comparison UI highlights all changed, new and deleted metadata items, so you can easily see the differences between your environments. This means you don’t need to rely on manual, time-consuming and error-prone tracking. Plus, you can easily spot when an org is getting out of sync and use the comparison to align your environments.

Most Salesforce deployment tools (Change Sets, Ant migration tool, Workbench, or even DevOps Center) compare the metadata in your source and target orgs.

You can compare and deploy any Salesforce metadata that’s supported by the Salesforce Metadata API. Even metadata types that are notoriously difficult to migrate (profiles, permissions and even layouts) can all be deployed through Gearset’s UI.

You can also deploy unmanaged packages and managed packages with Gearset. Managed packages aren’t included as part of the standard comparison filter but you can add them to your filter in just a few clicks.

Even low-code environments benefit from source control. We support all Git-based providers (such as GitHub, Bitbucket, AWS CodeCommit, VSTS, and GitLab) for declarative source code management.

We support on-premises Git setups, e.g. BitBucket Server (Stash), GitHub Enterprise, Azure DevOps Server and GitLab Self Managed.

Yes. Every deployment you perform via Gearset is saved so you have a complete audit history of every change made to your Salesforce orgs.