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

ReadMe vs Windows Server 2022 (Windows Server 2022) | Support by SupportedImages 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

ReadMe
Ranking in AWS Marketplace
44th
Average Rating
8.6
Number of Reviews
3
Ranking in other categories
No ranking in other categories
Windows Server 2022 (Window...
Ranking in AWS Marketplace
484th
Average Rating
9.0
Number of Reviews
3
Ranking in other categories
No ranking in other categories
 

Featured Reviews

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.
NP
Infrastructure Administrator at a marketing services firm with 10,001+ employees
Centralized infrastructure has streamlined SQL and collaboration workloads while saving administration time
I believe Windows Server 2022 (Windows Server 2022) | Support by SupportedImages can still be improved; it is not perfect yet. I think there should be a lesser number of patches, as every time the system is patched, the vulnerabilities that I scan always show some vulnerabilities. The product should be hardened from the beginning itself. Nothing else comes to mind now regarding disadvantages, but perhaps it requires more brainstorming. So far, I think it is all good with no additional features or integrations needed in Windows Server 2022 (Windows Server 2022) | Support by SupportedImages. Security must be enhanced, for sure.

Quotes from Members

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

Pros

"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."
"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."
"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."
"The biggest advantage of Windows Server for me is that it is more secure and adds security complexity to the environment."
"The installation of Windows Server 2022 (Windows Server 2022) | Support by SupportedImages is very easy."
"I see savings in time and money with Windows Server 2022 (Windows Server 2022) | Support by SupportedImages."
 

Cons

"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."
"ReadMe is a software-as-a-service offering only, and there is no way to self-host ReadMe."
"I think there should be a lesser number of patches, as every time the system is patched, the vulnerabilities that I scan always show some vulnerabilities."
"Microsoft needs to act faster. They have to merge the level of support to solve problems at once."
"I do not see any return on investment from Windows Server, and I do not see that it is saving me time or money."
report
Use our free recommendation engine to learn which AWS Marketplace solutions are best for your needs.
915,341 professionals have used our research since 2012.
 

Top Industries

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

Company Size

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

Questions from the Community

What needs improvement with ReadMe?
For our internal APIs that move quickly with frequent minor schema changes, the versioning felt more rigid than we wanted. We ended up simplifying our branching strategy to fit ReadMe's model. Read...
What is your primary use case for ReadMe?
My company has been using ReadMe for about two years. We use ReadMe to document the APIs exposed by our large finance-related application. We document internal-facing endpoints consumed by our team...
What advice do you have for others considering ReadMe?
You need to have a good Open API specification that is clean because if that is bad, then it is not ReadMe's fault that the documentation is bad, as the underlying data has to be there. My overall ...
Ask a question
Earn 20 points
 

Comparisons

No data available
 

Overview

Find out what your peers are saying about ReadMe vs. Windows Server 2022 (Windows Server 2022) | Support by SupportedImages and other solutions. Updated: September 2026.
915,341 professionals have used our research since 2012.