My main use case for Cloudberry is to synchronize my files to S3 on AWS.
A quick specific example of how I use Cloudberry to synchronize my files to AWS S3 is putting my files on my desktop, synchronized with S3 on AWS, and the same thing with synchronizing two S3 buckets across different accounts.
The best feature Cloudberry offers is the Cloudberry MCP, synchronizing files with storage, the main storage.
Synchronization with storage stands out to me because I only use Cloudberry for synchronizing files between different S3 buckets on AWS.
Cloudberry has impacted my organization positively, as today it is easier to manage files with the different S3s and different accounts.
It made file management easier because the tasks are faster and my management of files is better.
I do not think Cloudberry needs improvement; the feature of synchronizing files is wonderful.
I did not previously use a different solution before Cloudberry. Before choosing Cloudberry, I evaluated other options, but I am not using Cloudberry today because the features to synchronize with AWS IAM roles do not exist; it only uses an access key and secret key, which is a failure of security.
Cloudberry should be made to work with IAM roles; that is my only feedback.
I have been using Cloudberry for one month.
In my experience, Cloudberry is not stable; it has not been reliable for me.
I have not interacted with customer support for Cloudberry.
Before choosing Cloudberry, I evaluated other options, but I am not using Cloudberry today because the features to synchronize with AWS IAM roles do not exist; it only uses an access key and secret key, which is a failure of security.
My advice to others looking into using Cloudberry is that I am looking for a tool to more easily manage files in my company. I would rate this review an 8.