Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
45 reviews
from
External reviews are not included in the AWS star rating for the product.
ReadMe makes knowledge management simple
What do you like best about the product?
ReadMe makes centralizing and presenting knowledge easy. Out of the box, it has features to host all of your user and developer documentation in a single place. Users will find the knowledge easy to navigate with transparent navigation, and developers will appreciate the OpenAPI Specification of API presentation. We just need to focus on the content now.
ReadMe has also saved us a lot of time with natively supported AI features like the conversational AI search, MCP and the bi-directional Github sync. With massive leaps in LLMs and coding becoming more accessible, this is a critical and future-proof strategy ReadMe is taking. It also means we don't need to piece together tools and build this functionality ourselves - we just get it. Similarly, we also tried a more flexible CMS solution for documentation before - it was a nightmare because of developer dependency. While ReadMe's options may not be infinitely customizable (e.g. predefined docs categories that cannot be altered), what we have suffices, and we are not dependent on anyone else for small changes.
Last but not least, the ReadMe team has been a pleasure to work with. We got a lot of love from Kirby and Dan and their great Support team. We do have a lot of questions and get help very quickly if we need it.
ReadMe has also saved us a lot of time with natively supported AI features like the conversational AI search, MCP and the bi-directional Github sync. With massive leaps in LLMs and coding becoming more accessible, this is a critical and future-proof strategy ReadMe is taking. It also means we don't need to piece together tools and build this functionality ourselves - we just get it. Similarly, we also tried a more flexible CMS solution for documentation before - it was a nightmare because of developer dependency. While ReadMe's options may not be infinitely customizable (e.g. predefined docs categories that cannot be altered), what we have suffices, and we are not dependent on anyone else for small changes.
Last but not least, the ReadMe team has been a pleasure to work with. We got a lot of love from Kirby and Dan and their great Support team. We do have a lot of questions and get help very quickly if we need it.
What do you dislike about the product?
ReadMe could have slightly more customization options mainly for organizing knowledge. Within a single project, I can only organize knowledge into Guides, API Reference, Changelog, Recipes and Discussions. For us, it would be useful to have multiple "Guides" types within a specific project - this way we could organize and present the docs a bit more cleanly since we have a lot of content.
For the AI conversational search, a limitation is that external knowledge can virtually not be indexed. We have a separate, Support-managed Help Center that we cannot index - we can only copy paste content into a static textbox with a limited character count. At this point, the AI search is useful, but only limited to the site's knowledge.
Similarly, I would appreciate a bit more visual customization options. Now, a lot customization needs to happen in the code using CSS, JS and HTML. We got incredibly far with Claude Code and with Readme's recommendations on using the right selectors in their docs, but unless you are okay tinkering with AI, you will need a developer to help you customize this yourself.
For the AI conversational search, a limitation is that external knowledge can virtually not be indexed. We have a separate, Support-managed Help Center that we cannot index - we can only copy paste content into a static textbox with a limited character count. At this point, the AI search is useful, but only limited to the site's knowledge.
Similarly, I would appreciate a bit more visual customization options. Now, a lot customization needs to happen in the code using CSS, JS and HTML. We got incredibly far with Claude Code and with Readme's recommendations on using the right selectors in their docs, but unless you are okay tinkering with AI, you will need a developer to help you customize this yourself.
What problems is the product solving and how is that benefiting you?
Easy centralization and presentation of product knowledge. We can focus all our time on the actual content and organization without worrying about the technicalities of the CMS, because they just work. AI helps make our knowledge even more accessible.
Easy to Navigate and Quick to Learn, with Handy Metadata Controls
What do you like best about the product?
I find it really easy to navigate, even as someone who hadn’t used Markdown syntax before. I was able to figure it out quickly with the help of the drop-down menu, and now I don’t even really need it. Being able to manually add metadata to the background as well has been great.
What do you dislike about the product?
I wish there were a way to add videos, or at least include a link on an image.
What problems is the product solving and how is that benefiting you?
Having our changelog on the README has been great for AI visibility. When people search for information, they can find the correct feature set based on our changelog.
Great docs experience for devs (and non devs) as well as it's easy to keep updated
What do you like best about the product?
We’re building our own investment app, and one of the clearing firms we work with already used ReadMe for their docs, so we checked it out from that referral. It’s been an excellent fit. It’s quick to publish clean, modern docs, the OpenAPI sync and interactive API reference work really well, and it’s easy for both technical and nontechnical folks to contribute. The analytics are also genuinely helpful for seeing what people are reading and where we can make things even clearer.
What do you dislike about the product?
Nothing is perfect, some of the deeper customization and admin settings took us a minute to learn and could be a bit more intuitive, but the defaults are strong and support has been responsive, so it never slowed us down. Once you’re set up, day to day publishing and updates are effortless..
What problems is the product solving and how is that benefiting you?
It gives us one place for API docs, guides, and updates so partners & vendors can onboard faster and we spend less time answering the same questions. Overall it’s made our docs more consistent, more current, and more professional.
Effortless Documentation with Room for Improvement
What do you like best about the product?
I like that it's fairly easy to get set up, and it's visually very clean. The branding is straightforward and sections like guides versus API reference are easy to understand. These aspects make ReadMe quite appealing to me.
What do you dislike about the product?
I would like to have a better way to manage API documentation for different products. Right now, I have to work around things by creating a different version and basically making two products have two versions, but that's not semantically correct. I'd prefer to have a cleaner way to allow switchability between multiple products. Also, there's an annoying thing where the finance team can't have a role just to manage things like payment methods for our monthly payments, so they keep contacting me. That's the only gripe I have.
What problems is the product solving and how is that benefiting you?
I use ReadMe for managing all our API documentation in a brandable and straightforward portal.
They've made strides
What do you like best about the product?
Super easy to use!
Suggested Edits are cool.
Building a professional landing page is a breeze.
Powerful API insights.
Suggested Edits are cool.
Building a professional landing page is a breeze.
Powerful API insights.
What do you dislike about the product?
I think probably b/c it's built to be SO easy to use, it's a bit less flexible and grows feature-rich more slowly. Having said that, it's made strides recently!
What problems is the product solving and how is that benefiting you?
All-in-one documentation for products is what every tool in this market must offer today. ReadMe fits that description, enabling user guides, prod docs, help center layout, API docs and some customizability
Buggy Editor and Terrible Search
What do you like best about the product?
- Easy to get started
- Theme Customizations
- Theme Customizations
What do you dislike about the product?
- For a docs product it has a outrageously buggy editor. Yes I understand buidling WYSIWYG editor is hard but come on, all the menu UI elements keep erractically jumping around. Cannot indent or dendent things correctly
- Terrible Keyword based search in 2024. 9/10 times search results are incorrectly ranked.
- Does not support hosting arbitrary static HTML pages - E.g. generated from Python Sphinx or Mkdocs
- Terrible Keyword based search in 2024. 9/10 times search results are incorrectly ranked.
- Does not support hosting arbitrary static HTML pages - E.g. generated from Python Sphinx or Mkdocs
What problems is the product solving and how is that benefiting you?
Maintaing and Hosting Technical Docs of Product
Great support, great company, great for API docs, not the best for general user docs
What do you like best about the product?
The support is wonderful and I really enjoy how easy it is to add team members. The mascot is really enjoyable and in general it gets the job done. Easy to implement.
What do you dislike about the product?
Lack of collaboration tools, no content resuse tools, hard to work with images and no options to put inline etc. They're constantly improving their API doc tools but really little focus on general user doc needs despite many recommendations over the years. Some features that are entreprise only -- seems really unfair they don't offer the ad hoc. Global search and pdf download options should not be exclusive to enterprise because the cost is so different.
What problems is the product solving and how is that benefiting you?
Public user documentation without the need for Github
ReadMe Product Experience
What do you like best about the product?
It's user interface and display is aesthetically nice and intuitive as it's easy to navigate through features.
What do you dislike about the product?
I think ReadMe has a lot of great features that are just gated for higher subscriptions -- too pricey.
What problems is the product solving and how is that benefiting you?
Streamlining the company's internal API documents for devs and client's use.
Great product, easy to use...but can get expensive quick.
What do you like best about the product?
Start using day 1, very easy to implement.Also easy to customize to fit your needs and your goals.
What do you dislike about the product?
Built for small and medium sized companies. If you need additional segments, multiple sets of API documentaton it can get VERY EXPENSIVE.
Also, product support is non existent for lower tiers. Not a bad thing, but something to think about when selecting your package.
Also, product support is non existent for lower tiers. Not a bad thing, but something to think about when selecting your package.
What problems is the product solving and how is that benefiting you?
We had API documentation that was dissagregated and provided only informaiton about end points, little to know business value. Read.me helped us build an community around our API documetnaton for our technical users.
Easy and fast way to document our public API
What do you like best about the product?
I, as Product Manager, can manage the documentation without using developers' time
What do you dislike about the product?
Not so intuitive to create the home page
What problems is the product solving and how is that benefiting you?
We needed a fast and easy way to publish our public API documentation
showing 1 - 10