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

ReadMe vs Turbot 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
Turbot
Ranking in AWS Marketplace
89th
Average Rating
7.6
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2026, in the AWS Marketplace category, the mindshare of ReadMe is 0.2%, up from 0.2% compared to the previous year. The mindshare of Turbot is 0.2%, up from 0.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
AWS Marketplace Mindshare Distribution
ProductMindshare (%)
ReadMe0.2%
Turbot0.2%
Other99.6%
AWS Marketplace
 

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.
reviewer2849844 - PeerSpot reviewer
Vice President - Intelligent Automation at a financial services firm with 1,001-5,000 employees
Automation has transformed reconciliation accuracy and now cuts manual effort across operations
Turbot's best feature is its ease of use and simple installation process, as it is a no-code, low-code platform. It is well integrated with all libraries that can be used directly with drag and drop feature availability, including Excel automation, Outlook automation, reading and writing emails, and automating web portals with the Universal Recorder feature, which records all applications using one single recorder whether it is a desktop application, web application, or mainframe application. The Universal Recorder has positively impacted my daily work and my team's productivity because we do not have to rely on any other recorder and have consistency of the XPath and web element capturing. It automatically captures depending on the target application. Users do not have to do anything else; they just have to start the recorder, click on the actions, and things will get recorded easily. Another feature of Turbot is the low-code Cockpit web application, which provides a real pictorial view of all the bots on the dashboards, showing what is running, what is in progress, what is paused or failed. It has a continuous notification system in case of failures and successful bot executions, and includes a user management feature with role-based access control. Since integrating with Turbot, our organization has benefited by reducing the FTE percentage from 5% of the manual team using it. We have cut down almost 20 FTE resources, which has saved our costs, and the integration of automation with Turbot has served significantly in the cost optimization part. These cost savings and resource reductions were seen within a year of implementing Turbot. The specific process that benefited the most was related to retail operations of reconciliation of the manual books. Turbot integrates well with all other applications such as Excel, Outlook, the S3 bucket of AWS, and other API applications, which can be easily integrated with the help of REST API and SOAP components directly available. It also has a rich feature for developing custom libraries and components which are easily accessible through the toolbox of the application. Turbot has rich documentation with user guides that can be directly followed, and there are YouTube videos now published on Turbot application on how to get started and how to begin with one single RPA bot to convert manual tasks into automation.

Quotes from Members

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

Pros

"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."
"The predefined policy library is probably the biggest time-saver for us."
"Since integrating with Turbot, our organization has benefited by reducing the FTE percentage from 5% of the manual team using it, we have cut down almost 20 FTE resources, which has saved our costs, and the integration of automation with Turbot has served significantly in the cost optimization part."
 

Cons

"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."
"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."
"I think ease of use is the main area that needs improvement."
"The support system of Turbot needs more improvement in terms of raising SLA tickets and maintaining the TAT should get a little more refined, but not in respect to features, as rest of all things are good."
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%
Construction Company
49%
Comms Service Provider
10%
Outsourcing Company
8%
Insurance Company
6%
 

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 needs improvement with Turbot?
The support system of Turbot needs more improvement in terms of raising SLA tickets and maintaining the TAT should get a little more refined, but not in respect to features, as rest of all things a...
What is your primary use case for Turbot?
Turbot is used for automation in RPA across different domains including retail, retail banking operations, real estate, and various business use cases on airline portals. In the retail banking doma...
What advice do you have for others considering Turbot?
Currently, I do not see any improvements needed for Turbot; everything regarding performance is providing great services for us. The review rating given for this product is 8.
 

Comparisons

No data available
 

Overview

Find out what your peers are saying about Dice, Upbound, Tulip Interfaces and others in AWS Marketplace. Updated: October 2026.
921,523 professionals have used our research since 2012.