No more typing reviews! Try our Samantha, our new voice AI agent.

CloverETL vs Elastic Search comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

CloverETL
Average Rating
7.0
Reviews Sentiment
6.8
Number of Reviews
2
Ranking in other categories
Data Integration (57th), Data Visualization (31st)
Elastic Search
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
96
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Search as a Service (1st), Vector Databases (2nd)
 

Featured Reviews

it_user856614 - PeerSpot reviewer
Lead Programmer at a healthcare company with 10,001+ employees
Very easy to schedule jobs and monitor them, however we run out heap space even with a high allocation
Flexibility: We can bring in data from multiple sources, e.g., databases, text files, JSON, email, XML, etc. This has been very helpful Connectivity to various data sources: The ability to extract data from different data sources gives greater flexibility. Server features for scheduler: It is…
reviewer2817942 - PeerSpot reviewer
Senior Software Engineer at a consultancy with 11-50 employees
Logging and vector search have transformed observability and empowered reliable ai agents
Elastic Search is not specifically being used for certain purposes. I deploy Elastic Search database on the cloud and use cloud services so that nobody can attack. However, I do not use Elastic Search to resolve attack issues. The basic main purpose of Elastic Search, as of now, I feel it can do more in the AI area. Sometime I saw that when I am developing RAG and have to generate the embeddings, which I call metadata, sometimes it tries to fail. That durability or issue handling should be improved, but apart from that, I did not find anything as of now. As per my use case, whatever I am using seems pretty good. Apart from that, some definitely improvement will be there. One improvement is that it should be faster. Whenever I am searching any logs, it takes much time. For example, if I open my log in Notepad or a similar tool, I can search the text within a second. With Elastic Search, it takes a little bit of time, ten to fifteen seconds. That can be improved. Sometimes, engineers take time to assign when I create a ticket.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"No dependence on native language and ease of use.​​"
"We switched to CloverETL because of its flexibility to connect to various data sources and no dependence on native language and ease of use."
"Server features for scheduler: It is very easy to schedule jobs and monitor them. The interface is easy to use."
"Key features include wealth of pre-defined components; all components are customizable; descriptive logging, especially for error messages."
"Familiar, intuitive GUI coming from a Java development background, in-depth, descriptive, and well-laid-out documentation, responsive support through forums directly from Clover staff, a wealth of customizable pre-defined components, descriptive logging for error messages, and ease of install with a light footprint make it very effective to use."
"Connectivity to various data sources: The ability to extract data from different data sources gives greater flexibility."
"All the quality features are there. There are about 60 to 70 reports available."
"I have found the sort capability of Elastic very useful for allowing us to find the information we need very quickly."
"The dashboard is a valuable feature - it's awesome and very customizable."
"Elastic Search has impacted my organization positively as we use it for logging and APM."
"If you decide to run with it, the performance and the result can be very satisfactory."
"Elastic is doing a fantastic job by doing the indexing, and with a couple of indexing configurations, we are able to achieve our goal even though we are maintaining a huge amount of data per day, around millions of transactions for each record."
"Search is really powerful."
"From the customer side, Elastic Search is super fast and very efficient, delivering results quickly."
 

Cons

"Its documentation could be improved.​"
"Resource management: We typically run out of heap space, and even the allocation of high heap space does not seem to be enough."
"Needs easier automated failure recovery, more and more intuitive auto-generated or filled-in code for components, and easier or more automated sync between CloverETL Designer and CloverETL Server."
"Needs: easier automated failure recovery; more, and more intuitive auto-generated/filled-in code for components; easier/more automated sync between CloverETL Designer and CloverETL Server."
"​Resource management: We typically run out of heap space, and even the allocation of high heap space does not seem to be enough.​"
"The one area that can use improvement is the automapping of fields."
"I think Elastic Search could be improved by introducing more AI features, particularly for complex queries and aggregator functions to enhance usability and readability."
"They could simplify the Filebeat and Logstash configuration piece. There are a lot of manual steps on the operating system."
"We'd like to see more integration in the future, especially around service desks or other ITSM tools."
"Dashboards could be more flexible, and it would be nice to provide more drill-down capabilities."
"I would like to see more open source tools and testing as well as a signature analysis in the solution."
"It is hard to learn and understand because it is a very big platform."
"I would like to see more integration for the solution with different platforms."
 

Pricing and Cost Advice

Information not available
"we are using a licensed version of the product."
"To access all the features available you require both the open source license and the production license."
"We use the free version for some logs, but not extensive use."
"The version of Elastic Enterprise Search I am using is open source which is free. The pricing model should improve for the enterprise version because it is very expensive."
"The cost varies based on factors like usage volume, network load, data storage size, and service utilization. If your usage isn't too extensive, the cost will be lower."
"The price of Elasticsearch is fair. It is a more expensive solution, like QRadar. The price for Elasticsearch is not much more than other solutions we have."
"This is a free, open source software (FOSS) tool, which means no cost on the front-end. There are no free lunches in this world though. Technical skill to implement and support are costly on the back-end with ELK, whether you train/hire internally or go for premium services from Elastic."
"The pricing model is questionable and needs to be addressed because when you would like to have the security they charge per machine."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
894,738 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
27%
Manufacturing Company
13%
Computer Software Company
10%
Retailer
6%
Financial Services Firm
12%
Computer Software Company
9%
Manufacturing Company
9%
Retailer
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business39
Midsize Enterprise12
Large Enterprise47
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for ELK Elasticsearch?
When it comes to pricing, I think we had to pay AWS approximately 1,000 to 1,200 per month for the overall stack. I am not quite certain about how much Elastic Search costs specifically because I w...
What needs improvement with ELK Elasticsearch?
Elastic Search has many features, including Kibana and Logstash, which we regularly use. However, one downside in our product is cost, as it can be expensive when maintaining multiple shards and in...
What is your primary use case for ELK Elasticsearch?
As a developer, I use Elastic Search in developing one of my applications, basically integrating the back-end with Elastic Search. Our main use case for Elastic Search is for Logstash, which is a s...
 

Comparisons

 

Also Known As

No data available
Elastic Enterprise Search, Swiftype, Elastic Cloud
 

Overview

 

Sample Customers

IBM, Oracle, MuleSoft, GoodData, Thomson Reuters, salesforce.com, Comcast, Active Network, SHOP.CA
T-Mobile, Adobe, Booking.com, BMW, Telegraph Media Group, Cisco, Karbon, Deezer, NORBr, Labelbox, Fingerprint, Relativity, NHS Hospital, Met Office, Proximus, Go1, Mentat, Bluestone Analytics, Humanz, Hutch, Auchan, Sitecore, Linklaters, Socren, Infotrack, Pfizer, Engadget, Airbus, Grab, Vimeo, Ticketmaster, Asana, Twilio, Blizzard, Comcast, RWE and many others.
Find out what your peers are saying about CloverETL vs. Elastic Search and other solutions. Updated: April 2026.
894,738 professionals have used our research since 2012.