Contact sales: +1 (833) 441 7687
If you don't find an answer to your question, email us at [email protected] and we'll help you asap.
Gearset is licensed per end user of our tool, and can be paid for monthly or yearly. Gearset Pro costs $150 per user, per month. Gearset Enterprise costs $300 per user, per month. Check out our pricing page for more information about the differences between the two editions.
You can choose to pay monthly or annually - simply choose the payment option that's most convenient for you.
If paying monthly, you will be required to pay by credit card. If you wish to pay for a year up front, you can pay by cheque, bank transfer and credit card. Just email [email protected] and we'll help with processing your order.
Gearset is priced at a flat fee per month. We don't believe in difficult to understand or variable usage pricing. You can add any of your developer, sandbox or production Salesforce orgs without worrying about hidden costs or usage based credits.
No. If you only need one license of Gearset, then simply choose the edition you need and whether to pay monthly or annually. The choice is yours.
Gearset is licensed per end user of Gearset. If you have three people in your team using Gearset you will need three licenses. Team members can collaborate on creating and validating deployment packages, view deployment history, share Salesforce org connections, create and view change monitoring results and automate unit testing!
Yes. To add additional users to an existing subscription, contact us at [email protected].
Yes. We provide support by email and via the in-app chat window. We're based in the UK so our core hours are between 9AM and 6PM GMT, but if you have any questions outside of those hours don't be afraid to get in touch - you can often get a reply from us outside of our official support hours.
Only team owners can invite new members to their team. This can be done via the invitation option in the account summary section of the app when logged in. Once they accept the invitation they will be automatically added to your team.
Not at the moment. If you are going to switch to a new team, you will no longer be able to access or share any of the information from your old team. This helps ensure SOX compliance and data integrity.
Absolutely! You can choose who in the team has access to any of your Salesforce orgs via the team permissions section of the app in the account section. When delegating access to your Salesforce orgs, you can choose what level of access you want each team member to have, from read only to full compare and deploy.
Yes! You can add the team members you wish to notify about successful deployments via the account summary section in the app. They can also be notified of failing unit tests and when changes to your Salesforce orgs have been detected when creating an automated job.
Yes. Any team member can create and view the results of change monitoring and unit testing job results.
Yes. For any activity performed using Gearset, such as a deployment, any member of your current team can view and share the reports that are automatically generated after a deployment has finished.
When choosing the objects to deploy, your current selection can be saved as a draft deployment which you can go back to at any point in the future. Draft deployments can be accessed and edited by your team members to collaborate and help prepare for an upcoming deployment.
Yes. We use AWS ISO 27001 compliant data centers to meet security, legal and business compliance requests.
We use the standard Salesforce metadata API to access only the metadata. We don't access your business data.
No. Gearset uses OAuth for authenticating access to your orgs. We don't access or store your login credentials.
Data transfer between you, Gearset and Salesforce is all done using the latest SSL standards (SSL Report).
Gearset uses the same Amazon data centers that Salesforce and Heroku trust for their compute needs.
Yes. All Gearset requests originate from
188.8.131.52, so you will need to allow logins from these IPs.
Yes! We currently support GitHub, GitHub Enterprise, Bitbucket, GitLab and Visual Studio Team Services (VSTS) Git. This includes branch level support for all repos.
Not yet. We're expanding our support for more source control sytems this year. Please contact us to let us know what system you would like us to support.
Yes. Comparing from source control, folder on disk or using a live Salesforce org comes as standard with Gearset.
Yes! Just choose your source control system as the target in the same way you would if deploying to a Salesforce org.
Yes. Any text you enter into the deployment notes section in the pre-deployment summary will be included as your commit message.
package.xmlfile in my source control repository to filter comparison results?
Yes. If Gearset detects a valid
package.xml file in your source repository, we will use that to filter your comparison results. This can be a great way to reduce noise when comparing orgs and source control.
Metadata in source control should be in the same format as you use for Ant or Eclipse deployments. Within a branch, each metadata object type should sit within its own folder. You can place all of these folders within a single
unpackaged folder if you wish, but you should not create a nested folder structure. If you include a
package.xml file, we'll use that to filter the comparison results. For more information on structuring your metadata, see the Salesforce documentation on package creation.
Gearset can't deploy your metadata to a totally blank repository. You'll need to initialise your repository first and create a branch to deploy to.