# Bump.sh alternative: self-hosted API docs and changelog

Bump.sh is the closest tool in spirit to SelfDocHub: you keep your OpenAPI or AsyncAPI definition in the repository, a CLI
command in CI deploys it (`bump deploy openapi.yaml`), the documentation is rebuilt and a changelog of what changed is
produced. The big difference is **where it runs**: Bump.sh is a hosted service, SelfDocHub is software you run yourself.

## At a glance

| | SelfDocHub | Bump.sh |
|---|---|---|
| Publish from CI | One `curl` call with the service token | The Bump CLI deploys the definition |
| Automatic changelog | Yes, per version, with field-level details and breaking changes flagged | Yes, compared with the previously deployed version |
| Where it runs | Your own infrastructure only | Bump.sh's hosted service |
| Formats | OpenAPI/Swagger, GraphQL, OpenRPC, AsyncAPI | OpenAPI and AsyncAPI; check their site for more |
| Multiple APIs in one place | Groups, merged navigation, teams | Hubs that mix OpenAPI and AsyncAPI docs |
| Try-It, MCP | Built in | Check their site |

## Where SelfDocHub fits better

- Your documentation must be served from **your own servers**, behind your own authentication and network rules.
- You document **GraphQL or JSON-RPC** services too.
- You want **users, teams, roles and SSO** around internal documentation, or an **MCP server** for AI assistants.
- You prefer a plain `curl` to installing a CLI in every pipeline.

## Where Bump.sh is the better choice

- You want a **fully managed** service with nothing to install, maintain or back up.
- Your documentation is **public** and you want a hosted, branded site with the changelog emailed to subscribers.

*Comparison checked: November 2026. Vendors change plans and features, so confirm the points that matter to you on their own sites, linked in the sources below.*

## Sources

- [Bump.sh](https://bump.sh/)
- [Bump.sh API documentation](https://bump.sh/api-documentation)

---
Source: https://selfdochub.com/compare/bump-sh-alternative
