Blobr vs ReadMe

ReadMe and Blobr share part of the same goal: provide API consumers with clear documentation. But the path to that goal is a bit different between ReadMe and Blobr.
Here’s a guide to help you choose.
Free plan available, no credit card required.

Overview

What does Blobr do?

Blobr is a no-code SaaS to create your API developer portal. API providers can manage, document and distribute API products from one place on their terms. Each portal is unique and each API provider has its own. They can add their branding and link it to their website. Blobr has been made so that both technical and non-technical profiles can succeed.

What does ReadMe do?

ReadMe is a tool to build out API Documentation. It provides a complete hub for developers where end developers can find: documentation, interactive reference guides, changelogs etc. An upgraded version allows the API provider to customize colour, logo and layout of its developer hub as well as the domain name. Readme also enables API Providers to better understand, compared to other documentation tools, the consumption of their APIs by their users.

Blobr’s API Documentation tool

Blobr’s API documentation is built-in to be synced with API products, providing a personalized experience. API providers can provide use-case based instructions, making it easier for the user to consume the API by explaining how to use different endpoints together.
A “Try it out” button gives a quick response and a concrete illustration of the documentation. When an API is versioned and impacts an end-user, a customized changelog is sent to users to keep them updated with the latest changes. The documentation is always synced and changed accordingly.

ReadMe API Documentation tool

ReadMe displays documentation as a whole. It’s possible to create Guides to accompany an API reference section. API Providers can also add Recipes - short bundles highlighting key features or use-cases - but they require coding skills. API References are a complete way to document every endpoints, and the Guides are providing a sandbox to further help the API consumer understand how to implement functionalities. User metrics provide insight into how the API is used.

Comparaison table

Pricing
Free to use for API management and documentation purposes. Customization and branding available with the free plan.
Free plan with very little options. More options, including custom landing page and domain start at 99$ per month.
Branding
Logo, colours, custom domain name (API and API Portal), SSO (start at 0$/month).
Custom domain name and page (start at 99$/month). SSO options (start at 2000$/month).
API Documentation & difference between Workflow and Recipes
Based on the product creation and selected endpoints. Customized.

Workflows are step-by-step instructions adapted to each API products.
Displayed as a whole. Same for all API consumers.

Recipes are code samples providing developers use-cases and highlights of the API.
API Versioning
API versioning is handled on a product level directly. If an API is versioned, API Consumers get personalized changelogs. Docs are changed automatically and appropriate communications can be sent.
By sending API request data to ReadMe, API versioning can be partially covered. Some tracking options are available to see how people are using the API. Communication can be sent accordingly.
Target User
Made for all profiles of users.
Developer's hub.
Pricing
Free to use for API management and documentation purposes. Customization and branding also available with the free plan.
Branding
Logo, colours, custom domain name (API and API Portal), SSO.(start at 0$/month).
API Documentation & difference between Workflow and Recipes
Based on the product creation and selected endpoints. Customized.

Workflows are step-by-step instructions adapted to each API products.
API versioning
API versioning is handled on a product level directly. If an API is versioned, API Consumers get personalized changelogs. Docs are changed automatically and appropriate communications can be sent.
Target User
Made for all profiles of users.

Blobr’s advantage:
We push the personalized version of ReadMe a step further

ReadMe targets companies looking for a clear and comprehensive hub for developers. While the documentation is clear and simple, the company has also focused on providing metrics so that companies can understand how their users are consuming their APIs.

Blobr’s approach is different through the API Products focus.

What’s key with Blobr is that API Providers adapt to their clients’ use-cases with the products’ approach. The documentation - on products’ levels - only displays what’s necessary to implement for end-users. It reduces the time to the first call for final users. Versioning - one of the main challenges for developers - is also supported. Since consumers’ use of APIs is known on Blobr, we ensure that versioning creates the least amount of burden. Blobr anticipates all the impacts of the newly added API. Products are updated accordingly. API consumers get changelogs and communicated is smooth. Developer experience is finally improved.

On ReadMe though, only in case API Providers work on the right setup, they are given insights about how the API is used. On Blobr, whatever the set up of API Providers, personalization is much more advanced. This ensures the best developer experience.