I cannot stress enough how important it is for companies to avoid Readme.io.

There is no accountability from their team when their service encounters serious errors. For weeks now, the service has been throwing internal server errors which were caught by monitoring tools.

In reaching out to readme.io support, the only information they ever gave was "Thank you" and a link to their status page. The status page does not reflect the fact the services is severely depredated and any further attempts over the past 14 days to reach support have been met with total silence.

Then there was an exchange with their CEO on Twitter who seemed like they may try to get us some sort of response or RFO, but that has also been met with silence after submitting exactly what was requested.

If you value the ability for your customers to reach your API Documents, then do not use readme.io.

README.IO DOES NOT CARE ABOUT YOU AS A CUSTOMER.

A pretty UI and the right combination of tools (tutorial section, API documentation, announcements) does not make up for consistently slow and buggy experience. As the amount of stored documentation grows, the app becomes more and more unreliable about saving changes, and for complex, in-depth documentation, the anchor tagging system is terrible, leading to false redirects. Multiple times, I have lost everything I've worked on, and the support service is terrible, even at the enterprise level. Other times, my changes are being saved, even though the app tells me they are not. I do not recommend this service for any company with lots of documentation.