What is our primary use case?
We use Helix Core in our software development processes as a configuration management solution. Our typical use cases include system-level configuration management, versioning software, and managing files related to software such as traces and large binary files.
What is most valuable?
I find the configuration management features of Helix Core particularly valuable. The tool provides comprehensive functionality for versioning and managing large files, which makes it highly usable.
We also utilize its strong baselining features and the ability to efficiently cherry-pick data to build new configurations. Although we have deactivated some features like branching and merging, its overall feature set helps streamline our workflow significantly, requiring us to manage large binary assets effectively.
What needs improvement?
I need to work more with Helix Core to identify specific areas for improvement. However, it has an extensive feature set that leads to a steep learning curve, where users need to learn quite a bit of features to work with it effectively. While its customization is not an issue, the GUI might not appeal to everyone.
For how long have I used the solution?
I have been working with Helix Core for about a year now.
What do I think about the stability of the solution?
Helix Core is extremely stable. I would rate its stability as ten out of ten.
What do I think about the scalability of the solution?
I would rate Helix Core's scalability as eight or nine on a scale from one to ten. It is crucial for us to have this level of scalability because we handle a considerable amount of large binary assets, making our repositories quite large.
How are customer service and support?
The customer service and support are excellent. During a difficult case involving IDP integration, I received an email reply within 15 minutes. With a few email interactions and a subsequent Teams call, the issue was resolved the same day. I couldn’t ask for more as a customer.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Before Helix Core, we used IBM Rational Synergy. We switched because Synergy is out of maintenance.
How was the initial setup?
The initial setup was straightforward. The first test deployment took about five minutes, as it simply involved executing a statically linked binary, which immediately provides a server environment.
What about the implementation team?
Currently, I am responsible for maintaining Helix Core as a part-time job. However, this will change when we scale up, potentially requiring more resources.
What was our ROI?
Not yet, as we are still in the introduction phase.
What's my experience with pricing, setup cost, and licensing?
Pricing is relatively moderate at three to four out of ten. I find this cost justified for the capabilities provided by the product.
Which other solutions did I evaluate?
We evaluated other solutions like Mercurial, Plastic, and Subversion before deciding on Helix Core.
What other advice do I have?
I would rate Helix Core seven out of ten. It is not perfect, yet it is pretty solid. The product is best suited for large-scale configuration management, and that's why we chose it.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.