AutoRABIT Automated Release Management (ARM) Reviews

My main use case for AutoRABIT Automated Release Management (ARM) is that initially, we started by using it for taking backups, archiving, and storing them for various testing activities and performance testing activities for high loads. After that, we started using it for DevOps activities by connecting it to a configuration and deploying for that purpose.

We use AutoRABIT Automated Release Management (ARM) to automate Salesforce releases, typically for development, QA, UAT, and production. Instead of creating change sets manually and tracking deployment dependencies, we use ARM to track metadata changes, validate deployments across environments, and promote approved releases to production. This includes rollback support and audit tracking.

We even use AutoRABIT Automated Release Management (ARM) for hot fixes during production environments instead of using manual change sets, which improves release governance, traceability, and deployment reliability.

The best features that AutoRABIT Automated Release Management (ARM) offers are definitely the automated deployments. Pre-deployment validation is used for early detection of deployment issues, and the audit trails are decently good. Overall, the Salesforce metadata handling and source control integration are quite seamless. The visibility of a particular release becomes much clearer when we use AutoRABIT Automated Release Management (ARM).

I rely on pre-deployment validation most day-to-day because it gives me much better confidence before we deploy to production. This allows me to take necessary action to fix things before it becomes a production issue and to allocate resources to work on it.

The rollback capability is one of the features that I always appreciate and want it to work most of the time, but apparently it is not that easy. I look forward to this feature being more robust in AutoRABIT Automated Release Management (ARM).

AutoRABIT Automated Release Management (ARM) impacts my organization positively by helping to standardize deployments. Every developer is not doing it in a different way; instead, deployments are standardized across environments, thereby improving governance through approval workflows and audit trails. In summary, it improves our teams' ability to deliver changes to production more efficiently, faster, and with greater confidence.

Regarding how AutoRABIT Automated Release Management (ARM) can be improved, the user interface is not great. It should be more intuitive and more oriented toward what comes next. Deployment error messages need clear root cause analysis and remediation guidance. Both of these aspects need to be improved. Additionally, metrics are sometimes taken manually; having dashboards with release metrics and team performance would be beneficial. Out-of-the-box integrations with DevOps or ITSM tools like ServiceNow and project management tools would also be really helpful. The rollback capabilities should be made more granular. Real-time notifications and alerts would be valuable, and with AI available, self-service troubleshooting and diagnostic capabilities could reduce support dependency.

Troubleshooting deployment failures slows down daily work, which is where AutoRABIT Automated Release Management (ARM) can really help. Support documentation could be improved; instead of verbose documentation, contextual guidance would be more helpful. Root cause identification remains a problem, and often a veteran is needed to identify issues. Additionally, improved handling and visibility of Salesforce profile permission sets and sharing-related changes are always problematic. These daily challenges can definitely be improved.

I have been using AutoRABIT Automated Release Management (ARM) for two and a half years.

In my experience, AutoRABIT Automated Release Management (ARM) is not stable. It has a lot of scope for improvement.

Regarding the scalability of AutoRABIT Automated Release Management (ARM), the UI sometimes hangs, and we have filed a couple of tickets for it. Once the vendor assigns a technical person for support, they provide assistance, but we are still facing issues. Scalability is quite concerning.

I would rate customer support for AutoRABIT Automated Release Management (ARM) as below average. Many items are still open, some are implicitly closed, and overall it is a bit of an adjustment process.

We previously used an open-source solution, Jenkins. We used to create stages in the pipeline and integrate it with source control to perform all other metadata tasks and deployments. It had a lot of limitations, which led us to move to AutoRABIT Automated Release Management (ARM). In some projects, we have even removed and decommissioned AutoRABIT Automated Release Management (ARM) and moved to more effective solutions.

The time we take for releases has been reduced by roughly 40 to 60% since adopting AutoRABIT Automated Release Management (ARM), and automated validation helps reduce deployment-related issues, making it a higher quality tool. Overall, we have seen a 50% reduction in release efforts compared to the previous open-source Jenkins that we used. This translates to faster deployment cycles with around 30 to 35 releases per week, compared to what used to be 5 to 10 in a week.

Using AutoRABIT Automated Release Management (ARM) allows us to increase the number of releases from 7 to 10 a week to around 30 releases a week. Perhaps some more could be achieved, but for AutoRABIT Automated Release Management (ARM), it is more structured, and those are the metrics I have observed.

My experience with pricing, setup cost, and licensing for AutoRABIT Automated Release Management (ARM) is that it is expensive for the features it offers. However, if the features I mentioned have good depth and are truly usable, the pricing and return on investment would be worthwhile. If troubleshooting were much more helpful, then the price paid would justify its value.

We did not evaluate other options before choosing AutoRABIT Automated Release Management (ARM); the decision was based on experiences we already had in previous projects.

For others looking into using AutoRABIT Automated Release Management (ARM), I would advise considering something more highly organized for a more dynamic environment. I believe I have covered everything I wanted to say about AutoRABIT Automated Release Management (ARM). I have given this review a rating of 6 out of 10.

On-premises

Amazon Web Services (AWS)

Our main use case for AutoRABIT Automated Release Management (ARM) involves a software development team of almost 20 members who are parallelly working on different business requirements, completing their user stories, adding components, and pushing those components to higher environments. During this process, we validate whether the changes pushed by developers are valid and will not break anything in the target org. As soon as a developer works on the feature branch, that feature branch automatically gets merged, and whenever they create a PR through Git, it gets merged into the target org. We have a webhook job that triggers an AutoRABIT Automated Release Management (ARM) job to push those changes into the target org, and if there is any failure, an email is triggered to the developer who made the change as well as to all leads for verification. If no issues arise, we proceed to push all the changes to the target org, run a script to check that the newly added components or updates on existing components are reliable, and ensure nothing else is broken.

We also work with AutoRABIT Automated Release Management (ARM) in conjunction with Git, where we have a webhook job set up. This setup gives us the ability to create new jobs to segregate releases, for example, functionalities that will only be included once a user signs off are placed in a separate branch. Components for those functionalities remain in that branch, and once sign-off is received, we push all changes to the target org like UAT and pre-prod. This setup makes it easier to debug components, allowing for straightforward checks on which components were pushed as part of a functionality. Moreover, with AutoRABIT Automated Release Management (ARM)'s auto deployment schedule, we can select the specific commit versions to push changes. AutoRABIT Automated Release Management (ARM) also allows for scheduled incremental jobs that only pick up incremental changes instead of pulling the entire lot. This expeditious process includes options for rollbacks if any failures occur, ensuring that we can revert an entire functionality or exclude certain components when creating CI jobs.

AutoRABIT Automated Release Management (ARM) offers many valuable features, including the ability to pull components via CI automated jobs that deploy all incremental changes. In cases of Git authentication issues, we can still pull components through the normal deployment window without being blocked. It also provides the ability to push profiles and permission sets, which are tricky components in Salesforce environments. Through AutoRABIT Automated Release Management (ARM)'s change management, we can push full profiles and permission sets as well. There are various ways to pull source code from version control to orgs, and we can also do the reverse, allowing developers to push changes from their staging orgs to staging branches, automating the process for changes made within specific time frames simply by configuring and running a job.

The automated CI job feature of AutoRABIT Automated Release Management (ARM) saves our team the most time and headaches since it pulls components from version control to our org while running difference reports and checksums or code scans during the execution process. This feature is valuable when releasing to production, ensuring compliance with security standards for Apex and LWC. Additionally, it allows us to identify the differences we are looking for and which code scans to execute. Another helpful feature enables the exclusion of specific components, like named credentials and connected apps, that we do not want to deploy every time.

Currently, we have only one person managing the entire release process till production with AutoRABIT Automated Release Management (ARM). Since developers are already reviewing their components and addressing any issues during the automated CI job process, the release personnel only need to create specific branches and segregate components for deployment. The manual task of creating different branches and registering new branches in AutoRABIT Automated Release Management (ARM) whenever adding functionalities can be cumbersome. It is essential for us to segregate specific functional deployments, and the automated process allows us to validate changes efficiently. If the validation is successful, we can execute quick deployments. Importantly, the logging of CI jobs is detailed, providing exact error messages that help us troubleshoot. It also records the commit IDs from which components were pulled, enhancing traceability.

I choose a nine out of ten because while it is highly effective, there are aspects such as registering branches that can be time-consuming. When in a hurry, I might create a CI job and forget to register the branch. It would be helpful to have an action button to sync all available branches under Git since our Git is already authenticated, allowing us to avoid repeatedly registering branches.

We have been using AutoRABIT Automated Release Management (ARM) for the last two years, and we have end-to-end setup to automate all the deployments activity from dev to production.

I rate AutoRABIT Automated Release Management (ARM) a nine out of ten, as we use it daily for creating various release cycles and managing releases. Our team of 20 developers simultaneously works on common components and new components, all effectively managed by AutoRABIT Automated Release Management (ARM).

I have not encountered any AI features in AutoRABIT Automated Release Management (ARM) within my current organization, so I cannot provide details about that aspect as I have not used it.

AutoRABIT Automated Release Management (ARM) demonstrates high accuracy and reliability in output, particularly for automated deployments and reports. The CI jobs, triggered upon merging a PR in Git, pull components featuring incremental changes. Logging provides insights into deployment outcomes, whether successful or failed, and offers backup options for changes. If developers modify existing components, backup capabilities allow rollbacks in case of errors in the target org. The logging framework effectively captures ongoing deployment statuses, showing which components have been pulled and their completion status.

We use AutoRABIT Automated Release Management (ARM) in a public cloud setup, integrated through a proxy tunnel mechanism that ensures there is no direct contact between AutoRABIT Automated Release Management (ARM) and Git for security reasons.

We directly purchased AutoRABIT Automated Release Management (ARM) from AutoRABIT, not through AWS Marketplace.

I advise others considering AutoRABIT Automated Release Management (ARM) to proceed, as I have found the UI and overall usability much more straightforward compared to other tools such as Change Set, Copado, and Flosum. There is minimal training required; a one-time navigation session is typically sufficient. Once trained, users can easily follow each step as all required options are clearly presented. Previously, before we set up Git, we utilized the standard deployment feature in AutoRABIT Automated Release Management (ARM), which was also effective. You can also use AutoRABIT Automated Release Management (ARM) to download, extract, or update data from any org, with options for downloading as CSV or GIF files, enhancing its overall utility.

Public Cloud

Amazon Web Services (AWS)

AutoRABIT Automated Release Management (ARM) serves as my organization's primary DevOps and release management platform for Salesforce deployment and development. Our organization runs customized Salesforce organizations that support sales, services, and operation teams. Before AutoRABIT Automated Release Management (ARM), Salesforce deployments were largely manual. Developers used the Salesforce CLI or change sets and releases were infrequent and risky, and version control was inconsistently maintained.

On a day-to-day basis, I use AutoRABIT Automated Release Management (ARM) primarily to manage and monitor our Salesforce metadata deployments across multiple environments. Every morning, I check the deployment dashboards or review overnight scheduled deployments and confirm that they are completed and successfully deployed. Throughout the day, whenever a developer raises a deployment request, I use AutoRABIT Automated Release Management (ARM) to validate the metadata components before pushing them to the target ORG. This catches dependency conflicts early before they become production issues. I also keep an eye on the static code analysis results that run automatically on every Apex commit, flagging any violations to the development team. On days when we have a production deployment window, I use AutoRABIT Automated Release Management (ARM)'s environment comparison tool to do a final diff between staging and production to ensure that nothing unexpected has been interrupted. At the end of the week, I pull the deployment audit logs for our change management records. Overall, it has become the central tool I open every single day for everything related to Salesforce release management.

The best features AutoRABIT Automated Release Management (ARM) offers are the CI/CD pipelines built specifically for Salesforce management, which form the core value proposition that it delivers well. AutoRABIT Automated Release Management (ARM) understands the unique Salesforce deployment problems, handling metadata types, dependencies, destructive changes, and the quirks of the Salesforce deployment APIs in ways that generic CI/CD tools simply cannot accomplish without enormous custom scripting. The version control integration is solid, supporting both Git branching strategies and org-to-org comparisons. The static code analysis integration, CodeScan for Apex, and other Salesforce code add a security and quality gate that most Salesforce deployment teams lack. The environment management dashboard gives visibility into what version of each managed component is in each sandbox versus production, acting as a daily tool for my release manager responsibilities.

After using AutoRABIT Automated Release Management (ARM), it has transformed how our Salesforce team delivers changes. Previously, a production deployment was a half-day event involving manual coordination, spreadsheets that tracked the change logs, and a significant risk of configuration conflicts. With AutoRABIT Automated Release Management (ARM), we can now deploy to production multiple times per week with confidence. The automated delta deployment capabilities, which identify and deploy only what has changed, have dramatically reduced deployment times from two to three hours or even four hours to now almost twenty to thirty minutes on average. From a compliance perspective, the complete audit trail that AutoRABIT Automated Release Management (ARM) maintains for every deployment has been invaluable during the SOC 2 audits.

The positive impact AutoRABIT Automated Release Management (ARM) has shown with us is primarily time-saving. I would also highlight the pre-deployment validation engine, which validates everything before deployment, ensuring it is good to go, along with the environment comparison tool and rollback compatibility capability. All of this has positively impacted our workflow.

Certain improvements that I feel should be made would start with the UI perspective. The UI is not user-friendly, and newcomers or new users might get confused at times about how to proceed and what to do. This is an area AutoRABIT Automated Release Management (ARM) should work on. Additionally, the build and deployment job configuration is very powerful but complex. There are many settings, and the consequences of misconfiguration are not always clearly communicated until a deployment fails. We have also experienced occasional performance issues with the web application during periods of high concurrent activities, particularly when multiple teams are running deployments simultaneously. During those times, we feel lag.

Regarding needed improvements, deployment progress visibility when we kick off a large metadata deployment involving hundreds of components is quite limited. There are times when it is genuinely difficult to tell whether the deployment is progressing normally or has silently stalled somewhere in the middle. A more granular real-time progress view would reduce a lot of anxiety during critical deployment windows. I would also mention the observability integration. We heavily use DataDog for monitoring our systems, and there is no clean native integration between AutoRABIT Automated Release Management (ARM) and DataDog. This means deployment events are completely disconnected from our application performance metrics, so correlating a deployment with a spike in errors requires manual cross-referencing between two separate tools. A proper webhook or native integration would be a significant improvement.

We have been using AutoRABIT Automated Release Management (ARM) for a year now.

AutoRABIT Automated Release Management (ARM) is stable.

The platform handles our environment for fifty connected Salesforce organizations without any issues. Scalability is more of an organizational question than a technical one. AutoRABIT Automated Release Management (ARM) scales well technically, but scaling its adoption across a large team requires investment in training and governance processes.

The customer support is one of the differentiating strengths. The support team has deep Salesforce-specific expertise, which is critical given how domain-specific deployment issues can be. On several occasions when we observed metadata type conflicts and deployment API errors that we could not diagnose ourselves, the support engineer resolved the issues quickly and took time to explain the root cause. The response time could occasionally improve for non-critical issues, but for anything marked urgent, the response has been prompt.

Previously, we did not have any such solution; we used to do deployments manually. Then we got into AutoRABIT Automated Release Management (ARM).

My experience with pricing, setup cost, and licensing was good. It adds value.

The return on investment for AutoRABIT Automated Release Management (ARM) has been clear for us. One significant improvement has been the reduced deployment failures. Before using AutoRABIT Automated Release Management (ARM), we dealt with frequent deployment failures caused by missing dependencies and metadata conflicts. After using AutoRABIT Automated Release Management (ARM)'s pre-deployment validation, it eliminated the majority of those failures and saved time across our team. That one improvement alone is significant. Additionally, the speed of rollback has improved; we can now roll back production within half an hour, mostly.

My experience with pricing, setup cost, and licensing was good. It adds value.

We looked for other options but chose AutoRABIT Automated Release Management (ARM) only.

AutoRABIT Automated Release Management (ARM) is a definitive DevOps platform for Salesforce organizations. For people serious about release quality and compliance for any team managing a complex Salesforce organization with multiple developers and frequent deployments, it eliminates the pain of risk and manual deployments while delivering audit-ready traceability. I give this solution a rating of eight out of ten.

Public Cloud

Amazon Web Services (AWS)

The main use case for AutoRABIT Automated Release Management (ARM) when I was using it was for release management, as we were having different sandboxes, so the code is released from one org to another, all the way to production.

AutoRABIT Automated Release Management (ARM) was especially helpful because production used to have the code for two different releases, so using AutoRABIT Automated Release Management (ARM), we could have multiple monthly branches, and any codes, hotfixes, or bug fixes could be handled smoothly.

AutoRABIT Automated Release Management (ARM) made my day-to-day work easier with around 30 developers, as it helped in release management very effectively because there would be some automated processes as well as different code bases, helping in managing conflicts and release time.

AutoRABIT Automated Release Management (ARM) has positively impacted my organization by helping in handling release timelines as well as ensuring that hotfixes are handled properly. While not dramatic, it represents the bare minimum in improvements, and the results are excellent.

The best features that AutoRABIT Automated Release Management (ARM) offers include conflict resolution, multiple branches resolution, determining which code should go in which branch, as well as the capability to have org data deployed using AutoRABIT Automated Release Management (ARM), which makes it an additional tool that helps in the deployment of data as well as metadata.

The org data deployment feature was helpful for my team in Salesforce, for example, as we used to deploy products as well as rules, such as matrix rules. AutoRABIT Automated Release Management (ARM) was a very good help in this regard, which allowed developers to deploy directly without manual steps and handle it without going into a call with DevOps, as long as they have the access.

To improve AutoRABIT Automated Release Management (ARM), I suggest adding components such as managed packages and velocity components, which could also be deployed, and it could connect with multiple orgs using SFDX metadata instead of the old metadata, which would be helpful for Salesforce development.

I have been using AutoRABIT Automated Release Management (ARM) for around three years.

I have used AutoRABIT Automated Release Management (ARM) for three years, and we are currently using a different tool.

AutoRABIT Automated Release Management (ARM) helped with release timelines and hotfixes by providing smart conflict management and information about expected issues, such as if the code base is not available in the higher org, which informs the developer before submitting instead of finding the issue afterwards. The automation part also helped in running automated test cases, so it was quite helpful.

Regarding AutoRABIT Automated Release Management (ARM)'s AI capabilities, I find that its governance and security are decent, and while AI governance security is improving, the company states that it is secure and client data is secure, so I have not thought about it in depth.

Concerning AutoRABIT Automated Release Management (ARM)'s AI capabilities, I find its accuracy and reliability of output to be decent as it could improve more. It currently provides all the help tools, and if it does not have the information, it refers to the help documents, which is quite good.

For others looking into using AutoRABIT Automated Release Management (ARM), I say it is a great tool for automation. It could improve on some parts, but if you do not mind having robotic automation, AutoRABIT Automated Release Management (ARM) is the place to go, as it performs quite well in what it does. I have rated this review as a seven out of ten.

Private Cloud

Other

I use AutoRABIT Automated Release Management (ARM) mainly for RBC; as an nCino developer, I use it for RBC migration, deploying RBC from one sandbox to another sandbox, and we also handle prod deployments through AutoRABIT Automated Release Management (ARM). We also use the deployment part of it for metadata deployments and for committing our changes to Git branch; I use mainly these three parts.

We don't use a complete CI/CD pipeline with AutoRABIT Automated Release Management (ARM), but we have integrated it with Bitbucket and GitHub; we use the branching strategy without using complete YAML files and Jenkins.

On a scale of 1 to 10, I would rate AutoRABIT Automated Release Management (ARM) as an eight or nine.

I appreciate the part of AutoRABIT Automated Release Management (ARM) where I don't have to do different commits on Git; if I'm deploying anything from one org to another org, I can just deploy it to a branch as well, so I value that feature, as we don't have to do any extra deployments for that.

Because of AutoRABIT Automated Release Management (ARM), we don't have to do anything extra for audit purposes; we have a few audit requirements where they want to see everything deployed in one sprint, and since we set it as yes, which deploys to branch, it takes care of that whole part, and we don't have to do anything extra for that, which was beneficial for us.

AutoRABIT Automated Release Management (ARM) helps with real-time analytics; there are a few things such as profile comparison and org comparison that help us a lot, particularly if we have any permission issues, so those things are very useful to us.

Everything is in one place with AutoRABIT Automated Release Management (ARM), which we love; we don't have to use Inspector for data migration, and it's not that we have to use multiple tools; it's everything in one tool, which is our most used, go-to solution. For Git and Bitbucket, we don't even have to go to those orgs specifically; we can set it up through AutoRABIT Automated Release Management (ARM) and don't have to open it at all, and one license covers everything, which I appreciate. AutoRABIT Automated Release Management (ARM) also has data management features, so I value those as well; if we have any major data manipulations, we can do data uploads and other things through AutoRABIT Automated Release Management (ARM), and we don't have to do anything extra.

I am using the automated backup feature of AutoRABIT Automated Release Management (ARM) as well, and we are using it within one sandbox where we are taking backups.

Merging scenarios in AutoRABIT Automated Release Management (ARM) could be better; also, a few things which could improve include nCino RBC configuration, as sometimes if we have any extra lookup fields which are not configured by nCino, AutoRABIT Automated Release Management (ARM) sometimes misses those lookups to create the records or fetch those objects from our previous org to the next org, so I would feel more comfortable for RBC if AutoRABIT Automated Release Management (ARM) takes care of that too.

I haven't seen anything enhanced in AutoRABIT Automated Release Management (ARM) such as the ability to take a backup of RBC migrations as well, so how it works for metadata, deploying it from one org to another and deploying the same thing to the branch, I would like to see if we can do the same with RBCs also.

I have been using AutoRABIT Automated Release Management (ARM) for the last five years, for deployments and all other purposes.

We had a few issues with AutoRABIT Automated Release Management (ARM) where it started taking too much time to deploy things, but we found out they had some server issues at that particular time; AutoRABIT informed us to wait a while, and after restarting the whole system, it started working again, and other than that, we don't face many major downtime issues.

AutoRABIT Automated Release Management (ARM) is scalable, and we can scale it however we want to.

The initial setup of AutoRABIT Automated Release Management (ARM) was easy and much easier than expected; even when we faced some issues, we had an AutoRABIT support person who was there in the call and showed us if we were missing anything, so he was there to help us out.

I've used different products such as the normal Jenkins pipeline and data workbench; for data updates, we used Salesforce Inspector, so we used many tools, but once we got introduced to AutoRABIT Automated Release Management (ARM), we stuck to that.

The initial setup of AutoRABIT Automated Release Management (ARM) was easy and much easier than expected; even when we faced some issues, we had an AutoRABIT support person who was there in the call and showed us if we were missing anything, so he was there to help us out.

On a scale of 1 to 10, I would rate AutoRABIT tech support as an eight, or even a nine.

We did evaluate another solution, Copado, but it was not giving us anything specific to nCino; when we adopted AutoRABIT Automated Release Management (ARM), it provided us with a special, specific package for nCino, and it was a good demo as well, with the assurance that the whole RBC's part would be covered, so we didn't have to worry about that.

I'm quite confident with AutoRABIT Automated Release Management (ARM) regarding data integrity; I don't feel there's any mishap with it, and I feel comfortable working with AutoRABIT Automated Release Management (ARM).

I would say that if organizations are using nCino and developing anything on nCino, then they should go for AutoRABIT Automated Release Management (ARM) without any second thoughts; that's my recommendation, as it takes care of everything, and I feel more comfortable using AutoRABIT Automated Release Management (ARM) compared to any other tool when developing anything related to nCino.

I haven't used data masking yet. I would rate this review an overall 8 out of 10.

Public Cloud

Other

My main use case for AutoRABIT Automated Release Management (ARM) is for deployment.

For deployment with AutoRABIT Automated Release Management (ARM), my developers typically make code changes or modifications in the flows, and I am responsible for migrating these changes to production.

I usually perform the deployment to the lower environment first, and then process it into the production instance.

The best features AutoRABIT Automated Release Management (ARM) offers are its user-friendly interface and design.

What makes AutoRABIT Automated Release Management (ARM) user-friendly is that the user interface is intuitive, and a person who is new to deployment can easily access it.

All the features are quite user-friendly, and the UI is very good and explanatory.

AutoRABIT Automated Release Management (ARM) has positively impacted my organization because the deployment time has reduced significantly. Since the interface is user-friendly, there are fewer mistakes and less rework that needs to be done.

Regarding specific time savings with AutoRABIT Automated Release Management (ARM), I estimated that previously it took approximately one hour to deploy, but now it has reduced to around forty-five to fifty minutes.

AutoRABIT Automated Release Management (ARM) is working seamlessly well.

If I had to think of one area for improvement in AutoRABIT Automated Release Management (ARM), I would suggest improvements to the flows because when migrating the flows, it is somewhat challenging.

Finding out the dependencies when migrating flows in AutoRABIT Automated Release Management (ARM) is a bit difficult.

I have been using AutoRABIT Automated Release Management (ARM) for the last three years.

AutoRABIT Automated Release Management (ARM) is very stable.

AutoRABIT Automated Release Management (ARM) has very good scalability, and less effort is needed from us.

I have never had an opportunity to raise incidents with support for AutoRABIT Automated Release Management (ARM) because I have never faced any challenges.

Before using AutoRABIT Automated Release Management (ARM), I used Change Sets, but in this organization, I was taught AutoRABIT, and I have been using it since then.

I did not evaluate other options before choosing AutoRABIT Automated Release Management (ARM).

I would rate AutoRABIT Automated Release Management (ARM) a nine out of ten.

I chose nine out of ten for AutoRABIT Automated Release Management (ARM) because it is user-friendly, and I am very comfortable using it. I have never faced any challenges when accessing it, except for flows.

Regarding AutoRABIT Automated Release Management (ARM)'s governance and security, they are exactly as expected.

As far as the accuracy and reliability of output from AutoRABIT Automated Release Management (ARM), I rely on it, and it is a reliable application because we have not experienced any issues in the last three years.

I would definitely recommend others to use AutoRABIT Automated Release Management (ARM) because it is user-friendly and an effective, efficient, and good application. My overall rating for this review is nine.

On-premises

My main use case for AutoRABIT Automated Release Management (ARM) is release management and deployment from one sandbox to another sandbox, as well as backups, particularly metadata backups.

For a specific example of how I use AutoRABIT Automated Release Management (ARM) for release management or metadata backup, I proceed to the CI job and take the backup. As a release manager, we proceed with the deployment from UAT to production, so whatever changes we have in UAT, we deploy to production with the help of AutoRABIT Automated Release Management (ARM).

The best features that AutoRABIT Automated Release Management (ARM) offers include data backup, deployment from one org to another org, and deploying data from one branch to another branch. Additionally, we can also figure out the differences between one org to the other org.

AutoRABIT Automated Release Management (ARM) positively impacts my organization by helping deploy changes very quickly and allowing us to validate changes beforehand. That truly helps at the time of actual deployment in production so that it will not throw an error, and we can exactly estimate the time of deployment, as we have validated the changes and ensured everything is error-free.

In terms of how AutoRABIT Automated Release Management (ARM) can be improved, I think it is perfect as it has all the features similar to other tools such as Flosum and Copado. The main thing is that I do not think the user story bundle available in Copado is present in AutoRABIT Automated Release Management (ARM), which is the only thing I see as a limitation.

I have been working for the past seventeen years in my current field.

AutoRABIT Automated Release Management (ARM) is stable.

AutoRABIT Automated Release Management (ARM)'s scalability is good, making it worth proceeding with AutoRABIT Automated Release Management (ARM).

The customer support for AutoRABIT Automated Release Management (ARM) is good. They promptly address everything, resolving issues quickly and providing assistance with each solution we seek.

We were previously using Azure DevOps, which is a scripting tool needing multiple release managers to proceed and provide support. Now, with AutoRABIT Automated Release Management (ARM), we find it especially helpful.

I have seen a return on investment as time is saved significantly. With AutoRABIT Automated Release Management (ARM), we can manage with very few release managers compared to when we relied on scripting tools, which required many release managers for support. If any error arises, we need to fix it, but with AutoRABIT Automated Release Management (ARM), being a no-code and low-code deployment tool, it is straightforward to manage.

My experience with pricing, setup cost, and licensing for AutoRABIT Automated Release Management (ARM) is that it costs around four hundred dollars per month on an admin license.

Before choosing AutoRABIT Automated Release Management (ARM), I evaluated other options, including Copado.

Regarding how I measure the impact of AutoRABIT Automated Release Management (ARM), I have seen improvements in speed. Compared to other tools such as Azure DevOps or Bitbucket or GitLab, it takes much less time for validation and deployment. It is mainly supportive of unlocked packages and also works well with managed packages.

I would rate AutoRABIT Automated Release Management (ARM) overall as a nine out of ten. I choose nine out of ten because it has all the features, it is easy to use as a no-code or low-code deployment tool, and it allows for efficient deployment and validation of changes with all the available features including the updated marketing.

Regarding AutoRABIT Automated Release Management (ARM)'s AI capabilities, I think its governance is good. In terms of AutoRABIT Automated Release Management (ARM)'s AI capabilities regarding accuracy and reliability of output, I could rate it nine out of ten.

My advice to others looking into using AutoRABIT Automated Release Management (ARM) is to understand all the features available and recognize how helpful it will be for their needs. I will share the advantages of AutoRABIT Automated Release Management (ARM) with them.

AutoRABIT Automated Release Management (ARM) is good, and I have no additional thoughts. My overall review rating for AutoRABIT Automated Release Management (ARM) is nine out of ten.

On-premises

Other

My main use case for AutoRABIT Automated Release Management (ARM) is that it makes the work easier and helps to handle a large amount of data. During our refresh time for data merging, we used AutoRABIT Automated Release Management (ARM) data tool for the data migration, which also helped me significantly.

A quick specific example of how I use AutoRABIT Automated Release Management (ARM) for data migration involves setting the branches and the pipelines and ensuring that the test class coverage is covered as per the required standards from the Salesforce side for each class and trigger. Apart from this, I can say the data migration part with the org connection being seamless from one end to another. The initial step of AutoRABIT Automated Release Management (ARM) connecting with Salesforce through Git makes it much easier. Connecting Git, creating a pipeline, and authorizing them, and on the other end, authorizing an org helps it to be seamless.

The best features AutoRABIT Automated Release Management (ARM) offers are the automation validation, automation testing, approval, and the deployment process. If there is anything, we can roll back. The easy pipelines, sandbox management, the integrations, the version controls, and the feature updates are the ones I appreciate most.

Out of all those features, I can say the deployment automation and the rollback have made the biggest difference for my team because they reduce the failures and production risk. Second, the version control integration tracks every metadata change and supports team collaboration, where the versions have been updated recently. These are the things that I highly use. Additionally, Data Loader Pro supports data migrations across all the environments, which is also very helpful on our side when doing data migration activities.

For the release management, I could say that AutoRABIT Automated Release Management (ARM) has positively impacted my organization.

I would say syncing up with Jira for AutoRABIT Automated Release Management (ARM) could be improved. We have the stories and are picking the PR links directly from Jira. We tried this in our project, but it was not seamless connectivity, so we were not able to implement it fully. It would be helpful to have some customization after the PR is taken from Jira and deployed through AutoRABIT Automated Release Management (ARM). For example, automatically updating the status back to Jira would be beneficial. We need some customized statuses, which would be helpful for us.

I can say there are some other opportunities where AutoRABIT Automated Release Management (ARM) could improve. I need to explore where we can make further use of it. Due to that, I have given that score.

I have been working in the current field for three years.

AutoRABIT Automated Release Management (ARM) is stable.

AutoRABIT Automated Release Management (ARM) is very scalable. There are many options available, though I need to explore them further.

The customer support for AutoRABIT Automated Release Management (ARM) is good. They are patient and able to see what the requirement is from our side based on the tickets, and they help us solve it.

I have seen a return on investment with AutoRABIT Automated Release Management (ARM), and it is time-saving.

I have been using AutoRABIT Automated Release Management (ARM) for three years.

I am not much familiar with the AI capabilities of AutoRABIT Automated Release Management (ARM) regarding its governance and security.

I am not much familiar with the AI capabilities of AutoRABIT Automated Release Management (ARM) regarding its accuracy and reliability of output.

I can say some features, such as pipelines, are seamless compared to other pipelines such as Jenkins, where those are manual things that need to be done. We need to set the validation criteria.

I give this review a rating of nine.

Private Cloud

Other

My main use case for AutoRABIT Automated Release Management (ARM) is deploying or merging changes on a day-to-day basis with the help of this tool.

A specific example of a deployment or merge I have done recently using AutoRABIT Automated Release Management (ARM) involves all developers working on different environments. Whenever we work on a functionality, we compare the changes we have made to a component, and with the help of AutoRABIT Automated Release Management (ARM), we deploy the changes to the higher orgs. For example, we created a portal recently where the UI was worked on by me and there were other changes done by other developers.

I have been automating from one of the orgs that directly deploy the changes to the higher org once the deployment is successfully completed in one of the lower orgs.

The best features AutoRABIT Automated Release Management (ARM) offers include my work on two different kinds of packages, one being Salesforce components and the other being OmniStudio components. We separated both deployments so that the deployment should not be blocked if there are issues and both can be taken care of separately.

AutoRABIT Automated Release Management (ARM) has positively impacted my organization because earlier, we used to compare changes via Notepad and then merge our changes manually. With the help of AutoRABIT Automated Release Management (ARM), these tasks are now automated.

AutoRABIT Automated Release Management (ARM) could be improved by offering the feature where I can deploy both OmniStudio and Salesforce components together.

I would also mention that the UI should be more user-friendly. Rather than displaying all code, it should have a better user interface.

I have been using AutoRABIT Automated Release Management (ARM) as a deployment tool for three-plus years.

We have previously used Copado before switching to AutoRABIT Automated Release Management (ARM).

I would rate AutoRABIT Automated Release Management (ARM) an eight out of ten.

I chose an eight because, as I mentioned, the UI needs to be improved, and it should allow me to deploy multiple different types of components at a time.

Regarding AutoRABIT Automated Release Management (ARM)'s AI capabilities, I have not encountered any issues with respect to security, so I believe it is good. I think the AI capabilities are still in the learning phase, and I still see challenges that can be improved.

My overall rating for AutoRABIT Automated Release Management (ARM) is eight out of ten.

Private Cloud

Other

The main use case for AutoRABIT Automated Release Management (ARM) is to deploy components across various sandboxes from developer sandbox to QA sandbox, then UAT, and then to production. This allows us to automate a lot of the deployment process in Salesforce. We can also specify all of the other artifacts and, for test classes, we can increase the test case scenario beyond 75% for our own purposes.

Many customizations can be done using AutoRABIT Automated Release Management (ARM) for specific use cases of the company.

The best features that AutoRABIT Automated Release Management (ARM) offers are resolving merge conflicts and the configuration capabilities. The UI makes it very easy to see the changes and get those resolved. There is a lot of detailing about the configuration we can do in Salesforce, which is very valuable. Integrating with Git or Bitbucket is something really useful for version control as well.

Regarding the merge conflict resolution feature of AutoRABIT Automated Release Management (ARM), it has positively impacted my team's workflow and productivity by making it easier for even junior developers to see what incoming changes are there. Previously, some of the junior developers were hesitant about how to handle merge conflicts, but once they started using AutoRABIT Automated Release Management (ARM)'s merge conflict resolution, it became easier to see what incoming changes are present. Even if they are not sure how to proceed, they can perform the manual merge as well, which is very handy.

AutoRABIT Automated Release Management (ARM) has impacted my organization positively by fostering trust and reliability. It is able to perform a lot of commits and changes at scale. Even if we have many commits happening and many changes going through, it is able to perform those at scale, which is a good thing.

AutoRABIT Automated Release Management (ARM) can be improved in terms of the UI. There are some competitors, such as Copado, which offer a Salesforce native UI. Something similar to a Salesforce native interface so that people do not have to learn how to navigate the UI again would be beneficial.

I started using AutoRABIT Automated Release Management (ARM) in 2021.

Regarding AutoRABIT Automated Release Management (ARM)'s accuracy, I would rate it very high, about nine out of ten. The reliability is also good. Sometimes we have issues with AutoRABIT Automated Release Management (ARM)'s new releases where some things do not work, but those issues get fixed once someone addresses them. Overall, everything is good.

The specific outcomes in terms of numbers since using AutoRABIT Automated Release Management (ARM) include increasing people's productivity because they are not concerned about overwriting someone's changes. Everything is transparent. In terms of productivity, it initially takes some time to understand the process for a couple of weeks, but once the process is understood, it saves approximately 30 minutes per story compared to traditional deployment methods. If there are many developers that are added to AutoRABIT Automated Release Management (ARM), scalability becomes easier.

Governance and security with AutoRABIT Automated Release Management (ARM) is pretty robust. It is able to handle all of the Salesforce security components that are part of code or metadata. We can configure all of those things using AutoRABIT Automated Release Management (ARM), which we can specify based on the company's needs. It is pretty robust. I would rate this review an 8 out of 10.