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

CentOS 9 (centos 9) | Support by SupportedImages 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

CentOS 9 (centos 9) | Suppo...
Ranking in AWS Marketplace
484th
Average Rating
8.4
Number of Reviews
3
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

Chaithanya Kutnikar - PeerSpot reviewer
Senior Solutions Architect at Capgemini
Modern infrastructure has supported cloud migrations and improved secure distributed workloads
Among the downsides of CentOS 9 | Support by SupportedImages, I find that while installation becomes easier, the migration process concerning mainframes has been well-represented, especially with CentOS 9 | Support by SupportedImages 10 now integrating AI capabilities. The inclusion of GPUs and other resources to process large datasets could be a future direction worth pursuing, enhancing its abilities with RAG or generative AI through proper prompt engineering and ethics considerations. I would prefer to see more AI integrations within CentOS 9 | Support by SupportedImages. IBM is already making strides in this area by investing significantly. Following their acquisition and merger with Red Hat, CentOS 9 | Support by SupportedImages distribution aligns closely with Red Hat's, fostering AI capabilities and a futuristic approach to enhance daily operations through flexible application building on virtual machines.
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

"The low cost, low maintenance, support, and latency features of CentOS 9 | Support by SupportedImages are what I appreciate the most about it."
"CentOS 9 (centos 9) | Support by SupportedImages is stable as far as I am concerned. It is 100% stable."
"CentOS 9 (centos 9) | Support by SupportedImages helps with my application deployment process in general, and I get more productivity with it.I measure this productivity by the earlier build time with another OS, which was 32 minutes; with CentOS 9 (centos 9) | Support by SupportedImages, we are able to achieve the build time of around 14 to 16 minutes, down from an earlier 32 to 36 minutes."
"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."
"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."
"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."
"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."
 

Cons

"The support system is not very much up to the mark as we have with Ubuntu, and definitely, with respect to CentOS 9 (centos 9) | Support by SupportedImages, the help or support forum needs to be more comprehensive so that for many issues we need not reinvent the wheel."
"I experienced some lagging or crashing when I migrated to CentOS 9 | Support by SupportedImages 8; this event occurred during the early stage of that version."
"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."
"ReadMe is a software-as-a-service offering only, and there is no way to self-host ReadMe."
"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 CentOS 9 (centos 9) | Support by SupportedImages?
Pricing challenges may be difficult for me to address since I focus primarily on technical details and tend to negotiate trade-offs based on requirements. When good hardware is present, particularl...
What needs improvement with CentOS 9 (centos 9) | Support by SupportedImages?
Among the downsides of CentOS 9 | Support by SupportedImages, I find that while installation becomes easier, the migration process concerning mainframes has been well-represented, especially with C...
What is your primary use case for CentOS 9 (centos 9) | Support by SupportedImages?
CentOS 9 is still in use in my infrastructure operations and support coming from a traditional data center background. I utilized it extensively in projects from 2022 to 2024, including retailers a...
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 ...
 

Overview

Find out what your peers are saying about CentOS 9 (centos 9) | Support by SupportedImages vs. ReadMe and other solutions. Updated: October 2026.
921,523 professionals have used our research since 2012.