ReadMe.io vs Stoplight

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

ReadMe.io
ReadMe.io

66
92
+ 1
70
Stoplight
Stoplight

34
53
+ 1
32
Add tool

ReadMe.io vs StopLight: What are the differences?

ReadMe.io: Beautiful documentation made easy. Collaborative Developer Hubs; StopLight: Visual API Tooling. Stop writing thousands of lines of specification code. Our intuitive visual editors significantly cut down on design time, and are spec agnostic. Generate OAI (Swagger) and RAML specification code on demand.

ReadMe.io and StopLight are primarily classified as "Documentation as a Service &" and "API" tools respectively.

Some of the features offered by ReadMe.io are:

  • Collaboration - Crowdsource your docs! Users can keep docs current by suggesting changes.
  • API Explorer - Let users play with your API right inside the documentation.
  • GitHub Sync - Keep auto-generated reference docs synced with your actual code.

On the other hand, StopLight provides the following key features:

  • Powerful API modeling tools
  • Robust HTTP request maker
  • One click hosted documentation

"Great UI" is the primary reason why developers consider ReadMe.io over the competitors, whereas "Intuitive UX" was stated as the key factor in picking StopLight.

- No public GitHub repository available -
- No public GitHub repository available -

What is ReadMe.io?

Collaborative Developer Hubs

What is Stoplight?

Stop writing thousands of lines of specification code. Our intuitive visual editors significantly cut down on design time, and are spec agnostic. Generate OAI (Swagger) and RAML specification code on demand.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose ReadMe.io?
Why do developers choose Stoplight?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con

    Sign up to add, upvote and see more consMake informed product decisions

    What companies use ReadMe.io?
    What companies use Stoplight?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with ReadMe.io?
    What tools integrate with Stoplight?
    What are some alternatives to ReadMe.io and Stoplight?
    Postman
    It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide.
    Swagger UI
    Swagger UI is a dependency-free collection of HTML, Javascript, and CSS assets that dynamically generate beautiful documentation and sandbox from a Swagger-compliant API
    Apiary
    It takes more than a simple HTML page to thrill your API users. The right tools take weeks of development. Weeks that apiary.io saves.
    jsdoc
    JSDoc 3 is an API documentation generator for JavaScript, similar to JavaDoc or PHPDoc. You add documentation comments directly to your source code, right along side the code itself. The JSDoc Tool will scan your source code, and generate a complete HTML documentation website for you.
    Read the Docs
    It hosts documentation, making it fully searchable and easy to find. You can import your docs using any major version control system, including Mercurial, Git, Subversion, and Bazaar.
    See all alternatives
    Decisions about ReadMe.io and Stoplight
    Todd Gardner
    Todd Gardner
    President at TrackJS · | 4 upvotes · 49.6K views
    atTrackJSTrackJS
    Gatsby
    Gatsby
    Read the Docs
    Read the Docs
    ReadMe.io
    ReadMe.io
    GitHub Pages
    GitHub Pages
    Jekyll
    Jekyll

    We recently needed to rebuild our documentation site, currently built using Jekyll hosted on GitHub Pages. We wanted to update the content and refresh the style to make it easier to find answers.

    We considered hosted services that could accept our markdown content, like ReadMe.io and Read the Docs, however both seemed expensive for essentially hosting the same platform we already had for free.

    I also looked at the Gatsby Static Site generator to modernize Jekyll. I don't think this is a fit, as our documentation is relatively simple and relies heavily on Markdown. Jekyll excels at Markdown, while Gatsby seemed to struggle with it.

    We chose to stick with the current platform and just refresh our template and style with some add-on JavaScript.

    See more
    Noah Zoschke
    Noah Zoschke
    Engineering Manager at Segment · | 29 upvotes · 137K views
    atSegmentSegment
    Swagger UI
    Swagger UI
    ReadMe.io
    ReadMe.io
    Markdown
    Markdown
    Postman
    Postman
    #QA
    #Api
    #Documentation

    We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

    Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

    Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

    This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

    Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

    Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

    Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

    See more
    Interest over time
    Reviews of ReadMe.io and Stoplight
    Review ofReadMe.ioReadMe.io

    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.

    Review ofReadMe.ioReadMe.io

    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.

    How developers use ReadMe.io and Stoplight
    Avatar of Site Blindado
    Site Blindado uses StoplightStoplight

    Our API was defined using the tool. It's an excellent design-first tool.

    Avatar of SHOUTca.st
    SHOUTca.st uses ReadMe.ioReadMe.io

    Used for docs.shoutca.st + open source documentation of Cast.

    How much does ReadMe.io cost?
    How much does Stoplight cost?
    Pricing unavailable