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

Elastic Observability vs Portkey comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 29, 2026

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 Observability
Ranking in Application Performance Monitoring (APM) and Observability
11th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
29
Ranking in other categories
IT Infrastructure Monitoring (13th), Log Management (14th), Container Monitoring (5th), Cloud Monitoring Software (12th)
Portkey
Ranking in Application Performance Monitoring (APM) and Observability
26th
Average Rating
8.6
Reviews Sentiment
6.4
Number of Reviews
5
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2026, in the Application Performance Monitoring (APM) and Observability category, the mindshare of Elastic Observability is 1.6%, down from 3.9% compared to the previous year. The mindshare of Portkey is 0.3%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability Mindshare Distribution
ProductMindshare (%)
Elastic Observability1.6%
Portkey0.3%
Other98.1%
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

Stefan Decuypere - PeerSpot reviewer
Technology Consultant at Hybrid software
Real-time dashboards and visual insights have streamlined issue analysis and monitoring
After careful consideration about areas for improvement in Elastic Observability, aspects such as pricing, customization, implementation, and scalability could be improved. As a user of the system, I know what it costs but am not directly involved in cost-benefit evaluations or maintenance, which is handled by another team. I develop the visual representation of the data and frankly, I don't see major gaps in my application or anything I would really miss; I appreciate the fast pace of the developments that have occurred in the last couple of years. Regarding room for improvement in Elastic Observability, I would have preferred built-in tools to manage the indexes on deployment for better visual representation, as the initial feedback regarding system performance and data storage was fairly primitive and lacking.
Shravan Revanna - PeerSpot reviewer
Software Engineer at klydo.in
Centralized AI control has standardized our workflows and delivers faster, more reliable features
There are definitely some places where Portkey can be improved. Overall, the experience has been positive, but the first area is analytics and reporting. While the observability feature is excellent, we would like to have richer historical analytics and customizable dashboards. For example, it would be useful to see trends by applications and teams or features over long periods without exporting data to an external BI tool. Another area is governance for large organizations. As AI adoption grows, enterprises need more granular, role-based access control. We would like to see more advanced AI evaluation capability built into the platform itself, including features such as prompt versioning and automated quality scoring and regression testing. Finally, while the platform is supported with multiple providers, we would welcome even more intelligent routing capabilities, such as automatically selecting the best model based on latency, cost, and task complexity using configurable policies. These are not major pain points, but they are enhancements that would make an already strong platform even more valuable for an organization that scales their AI workloads. Documentation and onboarding could be enhanced. Portkey is developer-friendly, but we need more end-to-end references, architecture, and implementation guides for common AI patterns. This would help teams adopt it even faster. I did not give Portkey a perfect score because while it has become a foundational component in our AI stack and solves several operational challenges, I would still like to see deeper analytics, stronger enterprise governance features, and more built-in AI evaluation capabilities, especially for prompt testing, regression analysis, and model benchmarking. I would be comfortable recommending Portkey to any organization that is building multiple AI applications or wants to manage a scalable way to handle LLM providers and produce AI traffic.

Quotes from Members

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

Pros

"Its diverse set of features available on the cloud is of significant importance."
"It is very stable, and I would rate it ten out of ten based on my interaction with it."
"In addition to the fact that we are more proactive in the detection of incident before they occur, we can on one click see the request path from the customer to the backend."
"The tool's most valuable feature is centralized logging. Elastic Common Search helps us to search for the logs across the organization."
"For full stack observability, Elastic is the best tool compared with any other tool like New Relic or AppDynamics or Dynatrace."
"The ability to ensure that the data is searchable and maintainable is highly valuable for our purposes."
"I recommend Elastic Observability for its completeness of vision and wide ecosystem."
"I have built a mini business intelligence system based on Elastic Observability."
"Portkey is totally stable; it is one of the best software solutions in the market for this purpose."
"Portkey definitely provides a solid alternative solution for the agent and large model hosting platforms, and it is very helpful for us to explore the possibilities across the industry rather than staying with a few mainstream options."
"Portkey has significantly improved the organization by streamlining the AI processes being followed."
"Overall, Portkey has had a huge business impact in terms of cost savings and operational efficiency."
"Portkey's visualization is excellent, I particularly appreciate the multiple capabilities they have introduced, especially the MCP gateway, which is outstanding, the caching mechanism is very good, and the logs and traceability features are also excellent."
 

Cons

"There could be more low-code features included in the product."
"Elastic APM's visualization is not that great compared to other tools. It's number of metrics is very low."
"Elastic Observability needs to have better standardization, logging, and schema."
"The tool's scalability involves a more complex implementation process. It requires careful calculations to determine the number of nodes needed, the specifications of each node, and the configuration of hot, warm, and cold zones for data storage. Additionally, managing log retention policies adds further complexity. The solution's pricing also needs to be cheaper."
"Elastic support really struggles in complex situations to resolve issues."
"The solution needs to use more AI. Once the product onboards AI, users would more effectively be able to track endpoints for specific messages."
"The solution would be better if it was capable of more automation, especially in a monitoring capacity or for the response to abnormalities."
"If we had some pre-defined templates for observability that we could start using right away after deploying it – instead of having to build or to change some of the dashboards – that would be helpful."
"However, one thing I would like to say is that it could have better documentation."
"One major problem I see with Portkey is that when I had not yet started any trial, it started to denote that I had exceeded the prompt limit."
"End-to-end traceability is not fully fulfilled. They are only fulfilling about 50 to 60 percent of our end-to-end agent traceability requirements, and the remaining functionality needs to be implemented."
"There are definitely some places where Portkey can be improved."
"The main area for improvement is onboarding and trial experience."
 

Pricing and Cost Advice

"Elastic Observability is cheaper than other similar solutions, such as Dynatrace. Its license calculation is based on various factors like data volume and physical infrastructure, particularly related to RAM capacity."
"So far, there are just the standard licensing fees. Several of the components are embedded in the license or are even open source. They're even free depending on what you use, which makes it even more appealing to someone that is discussing pricing of the solution."
"The product’s pricing needs improvement."
"Pricing is one of those situations where the more you use it, the more you pay."
"Users have to pay for some features, like the alerts on different channels, because they are unavailable in different source versions."
"There are two types: cloud and SaaS. They charge based on data ingestion, ingest rate, hard retention, and warm retention. I believe it costs around $25,000 annually to ingest 30GB of data daily. That is the SaaS version. There is also a self-managed license where the customer manages their own infrastructure on-prem. In such cases, there are three license tiers that respectively cost $5,000 annually per node, $7,000 per node, and $12,500 per node."
"Since we are a huge company, Elastic Observability is an affordable solution for us."
"Elastic Observability's pricing could be better for small-scale users."
Information not available
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
915,341 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Computer Software Company
9%
Comms Service Provider
8%
Manufacturing Company
7%
Non Profit
33%
Computer Software Company
13%
Construction Company
10%
Retailer
10%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise4
Large Enterprise16
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Elastic Observability?
The problem is their licensing model, which is a bit confusing. Many customers struggle to understand their total cost of ownership because Elastic licensing is not dependent on easy, quantifiable ...
What needs improvement with Elastic Observability?
After careful consideration about areas for improvement in Elastic Observability, aspects such as pricing, customization, implementation, and scalability could be improved. As a user of the system,...
What is your primary use case for Elastic Observability?
My use case for Elastic Observability is observability, as we upload our customers' data, including logs, and when there is an issue, we can analyze what went wrong.
What is your experience regarding pricing and costs for Portkey?
Regarding pricing and licensing, the cost was relatively low because Portkey sits in front of our existing AI infrastructure. From a licensing perspective, I appreciate that the pricing model is pr...
What needs improvement with Portkey?
Portkey does not have an agent registry, which is a feature they should implement in a future release. We need to capture metadata of agents, and this capability is currently missing. End-to-end tr...
What is your primary use case for Portkey?
Our client is completely using AWS products. For AI gateways, we are using Portkey, which is the product we have implemented, and we are leveraging all AWS services for internal application develop...
 

Overview

 

Sample Customers

PSCU, Entel, VITAS, Mimecast, Barrett Steel, Butterfield Bank
Information Not Available
Find out what your peers are saying about Elastic Observability vs. Portkey and other solutions. Updated: September 2026.
915,341 professionals have used our research since 2012.