Try our new research platform with insights from 80,000+ expert users

Logpoint vs Mezmo comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 9, 2024

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

Logpoint
Ranking in Log Management
38th
Average Rating
7.6
Reviews Sentiment
7.0
Number of Reviews
23
Ranking in other categories
Security Information and Event Management (SIEM) (30th), User Entity Behavior Analytics (UEBA) (11th), Endpoint Detection and Response (EDR) (43rd), Security Orchestration Automation and Response (SOAR) (18th)
Mezmo
Ranking in Log Management
54th
Average Rating
9.0
Number of Reviews
2
Ranking in other categories
Application Performance Monitoring (APM) and Observability (89th), Observability Pipeline Software (7th)
 

Mindshare comparison

As of July 2025, in the Log Management category, the mindshare of Logpoint is 0.5%, up from 0.4% compared to the previous year. The mindshare of Mezmo is 0.2%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Log Management
 

Featured Reviews

Abdullah Secca - PeerSpot reviewer
Valuable monitoring and integration features boost compliance
They are not in the US market, and the quality of support has declined. They migrated operations from Boston to Denmark, and we cannot use a tool hosted outside the country. Additionally, dealing with foreign entities for support was a challenge, leading us to switch providers due to lack of adequate support.
TO
It consolidates all logs into one place and provides required features and functionalities
Every once in a while, our IBM cloud operational implementation gets behind. Sometimes, when we have a customer event, we do not get access to the latest logs for about 30 minutes, particularly for the sites that are heavily utilized. This is clearly not good. It is impossible to do RCA when you can't look at the logs that pertain to the time period in which the event occurred. It could be more of an operational problem than a feature problem. I don't have visibility about whether it is a LogDNA issue or just an operational issue.

Quotes from Members

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

Pros

"The most valuable feature of LogPoint is that they have the SIEM and SOAR combined in one solution. They are not on a separate platform."
"It is an AI technology because it is using machine learning technology. So far, there is nothing better out there for UEBA in terms of monitoring endpoints and user activity. It is using machine learning language, so it is right at the top. It provides that capability and monitors all the activities. It devises a baseline and monitors if there is any deviation from the baseline."
"The flexibility of the search feature and the solution's analytics features are the most valuable parts of the solution."
"Technical support is responsive and very friendly."
"The most beneficial was being able to prove, with proper reports, that from a compliance perspective, the company is in control. The service part of LogPoint did modifications or did some additional work to have the proper reports defined."
"The solution offers excellent reporting features. Our customers have been satisfied that they have been able to meet their compliance needs by giving them a standard report."
"The most valuable features are the ones that we use the most, which are the search and report facilities."
"The UEBA component, as well as the SOAR component, are some of the most valuable features of Logpoint."
"The solution aggregates all event streams, so that if there are any issues, it's all in the same interface."
"LogDNA consolidates all logs into one place, which is super valuable."
 

Cons

"LogPoint can improve its dashboards. We are not able to customize the dashboard when creating them. They only have preset dashboards which do not have exactly what we are looking for."
"One of the downsides is it is not a SaaS solution. It must be on-premises."
"The documentation part is something that needs to be improved, as well as the threat intelligence investigation part."
"Dashboards could be developed further."
"We were missing visuals and graphics. Recently, a new version seems to have come out, and it has a new graphical user interface. When I was integrating it, it was usable, but the GUI needed improvement."
"The general public wasn't looking for that type of product unless you had a company that was medical or financial and needed 24-hour responsiveness."
"What could be improved in LogPoint is its UI because it's less friendly to users than LogRhythm. The UI could be more aesthetically appealing to users. It's completely outdated."
"The thing that makes it a little bit challenging is when you run into a situation where you have logs that are not easily parsable. If a log has a very specific structure, it is very easy to parse and create a parser for it, but if a log has a free form, meaning that it is of any length or it can change at any time, handling such a log is very challenging, not just in LogPoint but also in everything else. Everybody struggles with that scenario, and LogPoint is also in the same boat. One-third of logs are of free form or not of a specific length, and you can run into situations where it is almost impossible to parse the log, even if they try to help you. It is just the nature of the beast."
"Every once in a while, our IBM cloud operational implementation gets behind. Sometimes, when we have a customer event, we do not get access to the latest logs for about 30 minutes, particularly for the sites that are heavily utilized. This is clearly not good. It is impossible to RCA when you can't look at the logs that pertain to the time period in which the event occurred. It could be more of an operational problem than a feature problem. I don't have visibility about whether it is a LogDNA issue or just an operational issue."
"No ability to encapsulate a query or a filter, and communicate or share that among the team."
 

Pricing and Cost Advice

"For a hundred user deployment the cost is about $10,000. The next year it would be the same because it's a subscription-based license. There are separate costs as well, for example, if a customer asks for training for their staff."
"LogPoint seemed like it was a good product, but it was expensive and there wasn't any room to move the pricing when customers needed a lower-costing solution."
"It was on a yearly basis at about $100K. It was not a huge environment. We were running it on our own virtual server environment, which, of course, had a cost. There was hardware and some energy cost, and then there were Microsoft Windows licenses for servers. That's all, but there was nothing in comparison to the licensing costs."
"It has a fixed price, which is what I like about LogPoint. I bought the system and paid for it, and I pay maintenance. It is not a consumption model. Most SIEMs or most of the log management systems are consumption-based, which means that you pay for how many logs you have in the system. That's a real problem because logs can grow very quickly in different circumstances, and when you have a variable price model, you never know what you're going to pay. Splunk is notoriously expensive for that reason. If you use Splunk or QRadar, it becomes expensive because there are not just the logs; you also have to parse the logs and create indexes. Those indexes can be very expensive in terms of space. Therefore, if they charge you by this space, you can end up paying a significant amount of money. It can be more than what you expect to pay. I like the fact that LogPoint has a fixed cost. I know what I'm going to pay on a yearly basis. I pay that, and I pay the maintenance, and I just make it work."
"On a scale of one to ten, where one is cheap, and ten is expensive, I would rate LogPoint's pricing a seven. It is not very expensive compared to some of the more costly products, and it is not very cheap compared to some of the cheaper products in the SIEM market."
"My company used to pay for LogPoint costs annually. It's a cost-effective solution. I'm not part of the Finance team, though, so I'm not sure exactly what the licensing fee is or what license my company had."
"Logpoint's pricing is mid-ranged and depends on the number of devices."
"It's less expensive than the competitors. The Logpoint marketing team is very accommodating and client-friendly. They offer very good reductions in price. They are pretty good in this aspect. They are transparent in their licensing and pricing."
Information not available
report
Use our free recommendation engine to learn which Log Management solutions are best for your needs.
861,803 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
23%
Educational Organization
16%
Comms Service Provider
8%
Manufacturing Company
8%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for LogPoint?
I rate the pricing at eight, suggesting it's relatively good or affordable.
What needs improvement with LogPoint?
Logpoint needs to be cloud-native, as currently, it is not. Additionally, there should be compliance mapping, where the features and actions within Logpoint map to security compliance standards.
Ask a question
Earn 20 points
 

Comparisons

 

Also Known As

No data available
LogDNA
 

Overview

 

Sample Customers

AP Pension, Copenhagen Airports, KMD, Terma, DISA, Danish Crown, Durham City Council, Game, TopDanmark, Lahti Energia, Energi Midt, Synoptik, Eissmann Group Automotive, Aligro, CG50...
Instacart, Asics, Lime, Salesforce
Find out what your peers are saying about Logpoint vs. Mezmo and other solutions. Updated: July 2025.
861,803 professionals have used our research since 2012.