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

ReadMe vs Windows Server 2016 (Windows Server 2016) | 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
35th
Average Rating
8.6
Number of Reviews
4
Ranking in other categories
No ranking in other categories
Windows Server 2016 (Window...
Ranking in AWS Marketplace
508th
Average Rating
8.6
Number of Reviews
2
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.
RP
CEO at Ruby Mills Ltd
Familiar platform has supported reliable on-premise file sharing and directory services
I am not currently using virtual machines, but I intend to switch over from VMware, and if I do, I may use the Shielded Virtual Machines feature. I am not using the Nano Server product, so I cannot comment on its impact on reducing server footprint in my organization. I am not working with Windows Containers for managing application deployment. I do not know about the integration capability of Windows Server 2016 (Windows Server 2016) | Support by SupportedImages with Microsoft Azure, as I do not use the cloud. I would give Windows Server 2016 (Windows Server 2016) | Support by SupportedImages a rating of eight on a scale from zero to ten.

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."
"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."
"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."
"I can state that I almost never see crashes or glitches in my experience."
"The product is familiar to use, which is a positive aspect."
 

Cons

"We could probably have more advanced analytics, multi-domain support, or something similar, and advanced access controls."
"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."
"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."
"I would not agree that Windows Server 2016 (Windows Server 2016) | Support by SupportedImages is 99% stable and reliable."
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
Construction Company
42%
Healthcare Company
11%
Comms Service Provider
11%
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?
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 ...
What is your experience regarding pricing and costs for Windows Server 2016 (Windows Server 2016) | Support by SupportedImages?
Windows Server 2016 (Windows Server 2016) | Support by SupportedImages is reasonable in price, and I think the license is acceptable.
What needs improvement with Windows Server 2016 (Windows Server 2016) | Support by SupportedImages?
I am not certain what improvements could be made to Windows Server 2016 (Windows Server 2016) | Support by SupportedImages, but perhaps some built-in security features could help. Additional securi...
What is your primary use case for Windows Server 2016 (Windows Server 2016) | Support by SupportedImages?
I work for a company that supports a ServiceNow platform integrated with other platforms, so I cannot specify whether I am a user, partner, integrator, or consultant for Microsoft. Our client use c...
 

Comparisons

No data available
 

Overview

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