eXo Platform is an open-source, social-collaboration software designed for enterprises. Some key features include: Enterprise Social Network, Enterprise Content Management and Social Collaboration.
$0
engaged user/month
HCL Connections
Score 9.0 out of 10
N/A
Connections from HCL Technologies (formerly from IBM, acquired by HCL in 2018) is a collaboration tool and employee digital workspace with key features like social analytics, blogs, document management, and a social network.
N/A
Pricing
eXo Platform
HCL Connections
Editions & Modules
Community
$0
engaged user/month
Social Intranet
$3
per month per user
Digital Workplace Cloud
$5
per month per user
Digital Workplace On-Premise
$5
per month per user
Enterprise Unlimited
9$
engaged user/month
No answers on this topic
Offerings
Pricing Offerings
eXo Platform
HCL Connections
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
eXo Platform
HCL Connections
Features
eXo Platform
HCL Connections
Project Management
Comparison of Project Management features of Product A and Product B
eXo Platform
9.2
Ratings
18% above category average
HCL Connections
-
Ratings
Task Management
10.00 Ratings
00 Ratings
Gantt Charts
8.00 Ratings
00 Ratings
Scheduling
10.00 Ratings
00 Ratings
Workflow Automation
8.30 Ratings
00 Ratings
Mobile Access
10.00 Ratings
00 Ratings
Search
10.00 Ratings
00 Ratings
Visual planning tools
8.00 Ratings
00 Ratings
Communication
Comparison of Communication features of Product A and Product B
eXo Platform
9.5
Ratings
18% above category average
HCL Connections
-
Ratings
Chat
10.00 Ratings
00 Ratings
Notifications
10.00 Ratings
00 Ratings
Discussions
10.00 Ratings
00 Ratings
Surveys
7.10 Ratings
00 Ratings
Internal knowledgebase
10.00 Ratings
00 Ratings
Integrates with GoToMeeting
9.00 Ratings
00 Ratings
Integrates with Gmail and Google Hangouts
10.00 Ratings
00 Ratings
Integrates with Outlook
10.00 Ratings
00 Ratings
File Sharing & Management
Comparison of File Sharing & Management features of Product A and Product B
In our scenario, we're using it for DMS, too. The DMS functionalities are suited only for small enterprises because when the number of resources increases it becomes harder to manage overall configuration. Anyway software is quite easy to use from an end-user point of view and it increases collaboration, especially when the team is already suited to use collaborative tools.
IBM Connections is possibly most suited for larger organizations where bigger teams are able to have more people to share with. Also, it may be less appropriate when there is so much security that it would hinder the anytime, anywhere access capabilities and prevent users from being able to enjoy sharing content with each other.
I personally love the user-friendly interface. Often you find software which is difficult to learn, and not utilized as often as it should be because of this. With eXo Platform, the interface is easy to understand, and is not particularly challenging to new users and non-tech savvy individuals.
It allows you to get work done, without feeling like using the platform is part of the actual work. It feels more like a natural system you would use in your leisure time to connect with friends and family, rather than a social intranet designed to facilitate employee communication and help you meet project deadlines.
The cloud platform allows users to easily share information and files, and collaborate on project work. Another benefit to this is it makes mobile collaboration possible.
Ajax call timing is more when creating space from eXo portal. Sometimes some UI portion was getting messed up in older version of eXo portal.
Should have a good validations for e.g "There are no documents available in this folder" instead of blank when there are no documents available in document folder.
Search in connections is incredibly poor. It's commonly joked that once data goes into Connections, you never find it again, unless you have a direct link. This alone kills usability for Connections.
Embedded content in wiki pages in connections is poorly implemented. While the content displays, you can't interact with it, or edit it reasonably, and it's really slow to load.
The "social" features in Connections are pretty lame, and no self-respecting user spends any time trying to build their profile. It's just disappointing.
Connections has continued to more than meet our needs from a collaboration point of view and we are currently working on integration with our IBM Websphere portal platform to provide an integrated collaboration solution. This scenario will provide our users the best both products have to offer in a single interface.
This platform has a pleasant user interface, is very easy to use, and offers a lot of useful accessories and add-ons. At first it can be a little intimidating, but it doesn't take long to get used to it. It is considerably reliable and safe. Facilitates connection and collaboration with coworkers. It provides tools that allow you to capture, organize and act according to the internal knowledge of your team.
Connections combines all the most useful abilities from various social networks. This makes it useful of course, but it also reduces user adoption time initially by allowing users to get comfortable with basic features. Once they are comfortable, it's easy for users to start exploring. They find new people in the organization to contact, new sources of information, etc. Before you know it, about half of the users are contributing back in some form -- and all with little or no training needed by IT.
Once Connections was installed, patched, etc. it was ALWAYS up. We only had to bring it down for OS updates to the servers. That seems to be typical of anything that runs on WebSphere; it's bulletproof and could probably run for months and years if the underlying OS didn't require constant patching.
IBM Connections web UI, mobile app (data sync to / from the device), and file transfer speeds were almost always very fast. It was rare for a slow-down of any kind, even when doing searches.
The eXo platform offers a high quality support, which satisfies the requirements of our company, especially when the platform begins to be used, due to the amount of tools that can be overwhelming. Support responses are made in a short period of time.
IBM Support has ALWAYS been quick to respond, regardless of the product. Even first level techs seldom provide "canned" responses and they really try to help. If they can't help, they don't wallow around but engage the right person immediately. It's very rare that the first level tech needs to escalate, and even more rare when they do escalate and the next person engaged cannot solve it. We have been more than satisfied with IBM support's quick and professional responses to our issues.
Try to understand you will never find a product which suites all your end user for 100%. IBM Connections is the best of all breeds but if you go look on each functionality on its own there are better example out there. But as IBM COnnections delivers it all in just one platform makes it the best example about integration of different functionality into one platform.
EXo platform offers a large number of ready-to-use functions, which determined your selection. Also, that it has a user interface is well designed. It is easy to know what tasks are available in each section. Learn the system and have the best customer service
IBM Connections offers a complete package of tools that can be useful but it doesn't integrate well with other services. Competitors like Yammer offer slightly fewer features but are cheaper and much easier to maintain. If we were making a decision today we probably would choose a combination of Yammer, Slack, Microsoft Teams, and other Microsoft or Google Tools.
Scaling UP is never an issue with IBM's core technologies like WebSphere, DB2, etc. as long as you have or can find the technical resources to implement it. Where IBM seems to fail is scaling DOWN for smaller organizations. Connections 5.0 on-premises would have required us to create 7 servers -- yes, they would be virtualized, but still that's 7 OS licenses, 40 virtual CPU cores, 80GB RAM, and a few TB of hard disk space. All to replace Quick which runs on 1 server with 1 OS license, 4 cores, 8GB RAM and 600GB of disk. Granted, there are major differences in capabilities between the two, but how do you get a CFO understand why features like a mobile app, file sync, and social sharing require 10x the back-end resources?