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

Elastic Search vs FME 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

Elastic Search
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
100
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Search as a Service (1st), Vector Databases (6th)
FME
Average Rating
8.6
Reviews Sentiment
6.5
Number of Reviews
7
Ranking in other categories
Data Integration (32nd)
 

Featured Reviews

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.
Gert Booysen - PeerSpot reviewer
Software Solutions Leader at GE Vernova
Extensive format support and reliable integration enhance data management while new pricing model requires reassessment
I haven't had any input or requirements from any customers that are not currently covered, so I don't have any additional needs that were identified or raised to me. Regarding pricing, with the model changes that they've implemented a while back, it actually made it more expensive to use, especially on the server side. They changed the licensing model, and that made customers think it is overpriced. Some customers were actually looking at alternatives. Pricing with the model changes was perceived negatively. I work primarily with enterprise customers, Vodacom, Eskom, so it's tier-one customers. For small customers, this solution is a bit too expensive. They don't really use it and just do direct integration on smaller implementations. This is basically used by tier-one customers. FME is still able to save time and money for clients. It's still a good investment. Regarding similar products to FME, GE developed a product called Data Fabric. That is a real-time operational integration platform, Data Fabric Network Connect, which is a GE Grid OS product. It is actually more expensive than FME, but the purpose is different as it's operational. The vendor in this case is GE, and it's a company that we bought that used to be called Greenbird. In current use scenarios, FME is still leading compared to Data Fabric. The GE product has a different application.

Quotes from Members

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

Pros

"What I appreciate about Elastic Search is that the best features include the ability to search through very big documents and index and search through them really fast."
"It is easy to scale with the cluster node model.​"
"The most valuable feature of the solution is its utility and usefulness."
"It is stable."
"The initial setup is very easy for small environments."
"Logsign provides us with the capability to execute multiple queries according to our requirements. The indexing is very high, making it effective for storing and retrieving logs. The real-time analytics with Elastic benefits us due to the huge traffic volume in our organization, which reaches up to 60,000 requests per second. With logs of approximately 25 GB per day, manually analyzing traffic behavior, payloads, headers, user agents, and other details is impractical."
"The AI-based attribute tagging is a valuable feature."
"The special text processing features in this solution are very important for me."
"FME's features that I have found most valuable are that it has a very friendly user interface, you don't need to use a lot of code, it has a lot of connectors and few forms, and it has a strong facial aspect that can do a lot of facial analysis."
"All spatial features are unrivaled, and the possibility to execute them based on a scheduled trigger, manual, e-mail, Websocket, tweet, file/directory change or virtually any trigger is most valuable."
"FME is spatially aware and understands how to deal with the conversion of spatial objects and their attributes."
"It has standard plug-ins available for different data sources."
"The most valuable feature of FME is the graphical user interface. There is nothing better. It is very easy to debug because you can see all steps where there are failures. Overall the software is easy to optimize a process."
"From my reseller perspective, the best features in FME are the ease of operation and the fact that it works."
"We make minor subtle changes to the workbenches to improve it. We can share the workbenches. We don't have to use GitHub or anything else."
"The most valuable feature of FME is the graphical user interface."
 

Cons

"We had initially planned to expand use of ELK because of its cheap price and the services that are included, but given the difficulty with implementation we've decided to go with Nagios instead."
"Elastic Search needs to improve its technical support. It should be customer-friendly and have good support."
"I see that there are areas in Elastic Search that have room for improvement, such as user documentation and onboarding processes."
"I found an issue with Elasticsearch in terms of aggregation. There is a maximum of 10,000 entries, so the limitation means that if I wanted to analyze certain IP addresses more than 10,000 times, I wouldn't be able to dump or print that information."
"This solution is stable, but at times the stack will freeze and you have to remove and recreate the cluster."
"There is a lack of technical people to develop, implement and optimize equipment operation and web queries."
"We have an issue with the volume of data that we can handle."
"We'd like to see more integration in the future, especially around service desks or other ITSM tools."
"FME is a great tool, but I don't know if we can scale it up since the prices are high and we would need to convince the decision makers to provide more budget."
"To get a higher rating, it would have to improve the price and the associated scalability. These are the main issues."
"Regarding pricing, with the model changes that they've implemented a while back, it actually made it more expensive to use, especially on the server side."
"We are looking at the possibility of using Glue instead of FME, using the native AWS product."
"The one thing that always appears in the community is the ability to make really easy loops to loop through data efficiently. That needs to be added at some point."
"FME's price needs improvement for the African market."
"FME can improve the geographical transformation. I've had some problems with the geographical transformations, but it's probably mostly because I'm not the most skilled geographer in-house. The solution requires some in-depth knowledge to perform some functions."
"Improvements could be made to mapping presentations."
 

Pricing and Cost Advice

"​The pricing and license model are clear: node-based model."
"We are paying $1,500 a month to use the solution. If you want to have endpoint protection you need to pay more."
"To access all the features available you require both the open source license and the production license."
"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."
"We use the free version for some logs, but not extensive use."
"There is a free version, and there is also a hosted version for which you have to pay. We're currently using the free version. If things go well, we might go for the paid version."
"Elastic Search is open-source, but you need to pay for support, which is expensive."
"We are using the Community Edition because Elasticsearch's licensing model is not flexible or suitable for us. They ask for an annual subscription. We also got the development consultancy from Elasticsearch for 60 days or something like that, but they were just trying to do the same trick. That's why we didn't purchase it. We are just using the Community Edition."
"FME Server used to cost £10,000; now it can cost over £100,000."
"The product's price is reasonable."
"We used the standard licensing for our use of FME. The cost was approximately €15,000 annually. We always welcome less expensive solutions, if the solution could be less expensive it would be helpful."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
909,948 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Manufacturing Company
9%
Computer Software Company
7%
Outsourcing Company
7%
Government
25%
Energy/Utilities Company
12%
Construction Company
7%
Comms Service Provider
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business40
Midsize Enterprise12
Large Enterprise50
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise1
Large Enterprise4
 

Questions from the Community

What is your experience regarding pricing and costs for ELK Elasticsearch?
The pricing for Elastic Search is mainly budgeted according to the organization budget, so we take it as a yearly subscription, and that is acceptable since we do get a fair discount when we are ta...
What needs improvement with ELK Elasticsearch?
When we get the logs, it is mostly about how we edit the configurations and how we make changes according to the requirements of our organization. In these cases, the logs sometimes can be a bit in...
What is your primary use case for ELK Elasticsearch?
I am the Elastic Search admin for my organization, and we are using Elastic Search to handle the traffic to GCP. The monitoring of all the clusters and all the deployments are quite good, and compa...
What needs improvement with FME?
I haven't had any input or requirements from any customers that are not currently covered, so I don't have any additional needs that were identified or raised to me. Regarding pricing, with the mod...
What is your primary use case for FME?
The use cases for FME are mainly integration to the GE Smallworld product. GE Smallworld is a GE product, and we are using it to integrate with other third-party products into GE Smallworld and ADM...
What advice do you have for others considering FME?
The overall rating for FME is eight out of ten, and I prefer the feedback to be anonymous. My job title is Senior Solutions Architect.
 

Comparisons

 

Also Known As

Elastic Enterprise Search, Swiftype, Elastic Cloud
No data available
 

Overview

 

Sample Customers

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.
Shell, US Department of Commerce, PG&E, BC Hydro, City of Vancouver, Enel, Iowa DoT, San Antonio Water System
Find out what your peers are saying about Amazon Web Services (AWS), Informatica, Palantir and others in Cloud Data Integration. Updated: August 2026.
909,948 professionals have used our research since 2012.