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

Akamai Segmentation [Private Offer Only] vs ReadMe comparison

Why PeerSpot?
 

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

Akamai Segmentation [Privat...
Ranking in AWS Marketplace
515th
Average Rating
8.0
Number of Reviews
2
Ranking in other categories
No ranking in other categories
ReadMe
Ranking in AWS Marketplace
35th
Average Rating
8.6
Number of Reviews
4
Ranking in other categories
No ranking in other categories
 

Featured Reviews

Brice-Abrioux - PeerSpot reviewer
Lead Cyber Architect at a energy/utilities company with 10,001+ employees
Micro-segmentation has delivered deep flow visibility and simplified firewall rule management
Although mapping is currently fine, Akamai Segmentation [Private Offer Only] can improve by providing a more useful and visually appealing graphical user interface for mapping. While we can automate rules through API calls, this is not entirely possible with the same API. Navigation between different sources and generations of APIs can make it time-consuming to achieve cartography. While labeling is beneficial, there is still room for user experience improvements. The improvements are not solely due to the Akamai project; they also stem from issues related to CMDB and the information systems of our company, where sometimes the information is inconsistent, causing Akamai to be unable to automate labeling if that information is not consistently provided.
TejaswiniAleti - PeerSpot reviewer
Member Technical at ADP
Centralized API documentation has improved collaboration and reduces onboarding time
Overall, I have had a positive experience with ReadMe, but there are a few areas where I think it could improve. One is customization. While it is easy to create clean documentation, making deeper UI or layout customizations can be somewhat limiting without additional effort. Having more built-in customization options would help teams tailor the developer portal to their branding and documentation needs. I would also like to see more advanced analytics. It would be useful to have richer insights into which APIs are viewed most frequently, where developers spend the most time, and which document pages generate the most support requests. Those metrics could help us continuously improve our documentation. Another improvement would be the tighter integration with Git-based development workflows. While synchronizing documentation works well, making documentation updates, previews, and reviews even more seamless as part of the pull request process would improve the developer experience. All of these are not major issues. They are enhancements that would make an already solid platform even better. Overall, ReadMe has worked well for our API documentation needs. An additional improvement I would like to see is better support for documentation versioning and change tracking. In enterprise applications, APIs evolve over time, and having more intuitive tools to compare versions and clearly highlight changes would make it easier for both internal teams and external consumers to adopt new API versions. I would also appreciate more built-in collaboration features, such as richer review workflows or commenting capabilities for documentation changes before they are published. That would make it easier for developers, QA teams, and technical writers to review documentation together and keep it accurate. Other than those enhancements, I think ReadMe is an easy-to-use platform that has met our API documentation needs. I do not have any major concerns beyond the improvements I already mentioned.

Quotes from Members

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

Pros

"Akamai is globally available with globally distributed edge locations and presence across the globe, which ultimately benefits our customers."
"Akamai Segmentation [Private Offer Only] has positively impacted our organization by giving us a better understanding of our flows, saving time implementing segregation and fixing production issues because we have a complete overview that allows us to determine whether the flow is functioning or if issues are due to flow problems."
"With ReadMe serving as a clear, self-service developer portal, our partners can now complete their integration in a fraction of the time, which has accelerated project delivery timelines, improved our partner satisfaction, and optimized engineering promises."
"Instead of investing time in documentation, ReadMe can document entire APIs quickly and we can just go and do a review, saving a lot of time instead of spending a couple of days or three days on documentation."
"Overall, if your organization wants to improve the developer experience, reduce repetitive support questions, and provide a centralized and professional API portal, I think ReadMe is a strong choice."
"Previously, our documentation was split up, but now it is unified through ReadMe, which gives a clear overview and is very easy to navigate, acting as a single source of truth for our business and providing more stability."
 

Cons

"I would rate their customer service as four out of ten."
"It is quite expensive, to be honest, but it is really useful, as we see positive results."
"ReadMe is a software-as-a-service offering only, and there is no way to self-host ReadMe."
"On a scale of one to ten, I rate ReadMe overall as eight out of ten. I choose eight out of ten because it is a very strict platform with limited customization."
"We could probably have more advanced analytics, multi-domain support, or something similar, and advanced access controls."
"One is customization. While it is easy to create clean documentation, making deeper UI or layout customizations can be somewhat limiting without additional effort."
report
Use our free recommendation engine to learn which AWS Marketplace solutions are best for your needs.
921,523 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Construction Company
42%
Healthcare Company
11%
Comms Service Provider
11%
Outsourcing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Akamai Segmentation [Private Offer Only]?
I have a separate account team who manages the cost and handles product procurement, licensing, and license renewal.
What needs improvement with Akamai Segmentation [Private Offer Only]?
Akamai could pass more headers directly to the application layer, such as user details or other user attributes, which would enable more granular personalization. These configurations require colla...
What is your primary use case for Akamai Segmentation [Private Offer Only]?
I have used Akamai Segmentation [Private Offer Only] for CDN purposes, specifically for Content Delivery Network and static content caching, delivering static assets and content globally near the e...
What needs improvement with ReadMe?
ReadMe is a very new tool and I have not used it much, but what we are doing right now is great, so I do not think there is any improvement needed. One thing is that I think there is some limitatio...
What is your primary use case for ReadMe?
Our main use case for ReadMe is that we will be having a lot of APIs and we wanted to document them very well. We were using Swagger, but ReadMe provides more interactive API documentation with goo...
What advice do you have for others considering ReadMe?
ReadMe is deployed in our organization in a dev environment where we do testing and documentation. We use it in a dev environment which is only accessible for our organization. We use Azure as our ...
 

Comparisons

No data available
 

Overview

Find out what your peers are saying about Akamai Segmentation [Private Offer Only] vs. ReadMe and other solutions. Updated: October 2026.
921,523 professionals have used our research since 2012.