Sold by: AutoRABIT
AutoRABIT ARM (Automated Release Management) is a robust DevOps solution purpose-built for Salesforce. ARM enhances development efficiency by automating deployments, enabling seamless branch merges, and tracking changes with complete visibility across the entire Salesforce release lifecycle.
4.1
Overview
AutoRABIT ARM is the most advanced CI/CD and release management tool for Salesforce, offering a complete solution for development teams looking to scale beyond basic deployment tools. ARM provides end-to-end automation of release processes, reduces manual errors, and enhances the overall security of your Salesforce environments. Key Capabilities
- Automated Release Processes to minimize manual errors
- Version Control Integration with Git and other systems
- Sandbox Management with automated refreshing
- Continuous Integration & Delivery Pipelines
- Customizable Deployment Workflows
- Quality Gates for code reviews and compliance checks
- Real-Time Reporting and Analytics
- Enhanced Security Measures for safe deployments
- Security and Quality Assurance: Incorporates quality gates and security measures for reliable, compliant releases.
For custom pricing, EULA, or a private contract, please contact info@autorabit.com
Highlights
- Deployment Automation: Provides structured, automated release processes to ensure consistency and reliability.
- Version Control: Facilitates effective branch management and integration with multiple systems.
- CI/CD Pipelines: Enables rapid, automated delivery of features with consistent, repeatable deployments.
Details
Sold by
Delivery method
Deployed on AWS
New
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide
Gain valuable insights from real users who purchased this product, powered by PeerSpot.
Financing for AWS Marketplace purchases
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing
Pricing is based on the duration and terms of your contract with the vendor, and additional usage. You pay upfront or in installments according to your contract terms with the vendor. This entitles you to a specified quantity of use for the contract duration. Usage-based pricing is in effect for overages or additional usage not covered in the contract. These charges are applied on top of the contract price. If you choose not to renew or replace your contract before the contract end date, access to your entitlements will expire.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
Dimension | Description | Cost/12 months |
|---|---|---|
ARM Starter Package | 10 developer licenses, implementation & basic support | $39,780.00 |
Dimension | Description | Cost/unit |
|---|---|---|
TAC_ARM_USER | Annual charge for additional user license | $3,978.00 |
Vendor refund policy
No Refunds
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Vendor resources
Support
Vendor support
For AutoRABIT support, please visit: https://support.autorabit.com/
To submit a support ticket, please visit https://support.autorabit.com/ and click "Submit a Ticket" at the bottom of the page.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Updated weekly
Top
50
In Agile Lifecycle Management
Top
10
In Source Control, Application Development, Continuous Integration and Continuous Delivery
Top
25
In Migration
Sentiment is AI generated from actual customer reviews on AWS and G2
Functionality
Ease of use
Customer service
Cost effectiveness
Positive reviews
Mixed reviews
Negative reviews
AI generated from product descriptions
Deployment Automation
Automated release processes that minimize manual errors and ensure consistency across Salesforce deployments
Version Control Integration
Integration with Git and other version control systems for effective branch management and seamless merges
CI/CD Pipeline Capabilities
Continuous Integration and Continuous Delivery pipelines enabling rapid, automated delivery with customizable deployment workflows
Sandbox Management
Automated sandbox refreshing and management capabilities for Salesforce environments
Quality Gates and Security Measures
Quality gates for code reviews and compliance checks with enhanced security measures for safe deployments
Source Code Management
Powerful branching tools for creating and managing code with version control capabilities
Continuous Integration and Continuous Deployment
Advanced CI/CD pipeline functionality with automatic testing and reporting for production code quality standards
Package Management
Built-in universal package management for creating and managing software supply chains
Project Planning and Analytics
Project planning tools with analytics capabilities providing insights into team productivity and performance metrics
High Availability and Disaster Recovery
Enterprise readiness features including HA (High Availability) and DR (Disaster Recovery) infrastructure support
Schema Registry
Centralized storage for schema changes with auto-generated documentation for database schemas.
Continuous Integration Testing
Automated simulation and review of database migrations during CI process to detect destructive changes and constraint violations before deployment.
Deployment Visibility
Single pane of glass interface to monitor and view the status of schema migrations across multiple environments with detailed deployment logs.
Migration Management
Central repository for storing and managing migration directories with simplified deployment process to production environments.
Deployment Tool Integration
Seamless integration with modern deployment platforms including Kubernetes and Terraform for automated schema migration deployment.
Standard contract
No
Customer reviews
Umesh Bharatrao
User-friendly release process has reduced deployment time and supports reliable production changes
Reviewed on Jun 22, 2026
Review provided by PeerSpot
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using AutoRABIT Automated Release Management (ARM) for the last three years.
What do I think about the stability of the solution?
AutoRABIT Automated Release Management (ARM) is very stable.
What do I think about the scalability of the solution?
AutoRABIT Automated Release Management (ARM) has very good scalability, and less effort is needed from us.
How are customer service and support?
I have never had an opportunity to raise incidents with support for AutoRABIT Automated Release Management (ARM) because I have never faced any challenges.
Which solution did I use previously and why did I switch?
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.
Which other solutions did I evaluate?
I did not evaluate other options before choosing AutoRABIT Automated Release Management (ARM).
What other advice do I have?
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.
Robertkingsly R
Automated releases have reduced deployment time and now support faster error‑free migrations
Reviewed on Jun 21, 2026
Review provided by PeerSpot
What is our primary use case?
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).
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been working for the past seventeen years in my current field.
What do I think about the stability of the solution?
AutoRABIT Automated Release Management (ARM) is stable.
What do I think about the scalability of the solution?
AutoRABIT Automated Release Management (ARM)'s scalability is good, making it worth proceeding with AutoRABIT Automated Release Management (ARM).
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
Before choosing AutoRABIT Automated Release Management (ARM), I evaluated other options, including Copado.
What other advice do I have?
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.
RaviRanjan3
Automated CI jobs have streamlined parallel releases and have improved deployment reliability
Reviewed on Jun 19, 2026
Review from a verified AWS customer
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
reviewer2857212
Automated releases have boosted delivery speed but still need better UI and troubleshooting support
Reviewed on Jun 16, 2026
Review from a verified AWS customer
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using AutoRABIT Automated Release Management (ARM) for two and a half years.
What do I think about the stability of the solution?
In my experience, AutoRABIT Automated Release Management (ARM) is not stable. It has a lot of scope for improvement.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Gaurang Karve
Unified release management has simplified org migrations and improved audit readiness
Reviewed on Jun 08, 2026
Review provided by PeerSpot
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using AutoRABIT Automated Release Management (ARM) for the last five years, for deployments and all other purposes.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
AutoRABIT Automated Release Management (ARM) is scalable, and we can scale it however we want to.
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What about the implementation team?
On a scale of 1 to 10, I would rate AutoRABIT tech support as an eight, or even a nine.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.