What Bump.sh does, how its OpenAPI and AsyncAPI documentation platform compares, current pricing tiers, key features, pros, cons and frequently asked questions.
Because the name 'Bump' has been used for more than one product over the years, it is worth being explicit about which one this profile covers. This is Bump.sh, an API documentation and change-management SaaS platform founded in 2017 in Angers, France, that is actively developed and commercially operated today. It has no connection to the unrelated consumer mobile app also called Bump, which let users share contact information by physically tapping two phones together; Google acquired that app's maker in 2013 and discontinued the product entirely in 2014. Any reference to 'Bump' in a software or API tooling context in 2026 is referring to Bump.sh.
Bump.sh's core workflow starts with a machine-readable API specification -- an OpenAPI file for REST APIs, an AsyncAPI file for event-driven or message-based APIs, or a workflow specification like Arazzo or Bump.sh's own Flower format -- that a team already maintains or commits to maintaining as part of their development process. Bump.sh turns that specification into an interactive, always-current documentation site, and critically, diffs every new version of the spec against the previous one so that API consumers can see precisely what changed, rather than needing to manually compare two versions of a lengthy spec file themselves.
This diff-driven approach extends into Bump.sh's automatic changelog feature on the Pro tier, which surfaces a running history of API changes without requiring anyone to write release notes by hand, and into release rollback, which lets a team revert a documentation deployment if a bad spec change goes out. Multiple APIs can be organized together into a single developer hub, useful for organizations exposing many microservices or product APIs under one discoverable entry point, and deployment integrates directly into CI pipelines via a CLI and native GitHub integration so documentation updates happen automatically alongside code and API changes rather than as a separate manual step.
Bump.sh's three-tier pricing -- Basic at $50/month, Pro at $250/month, and a custom-quoted Enterprise tier -- scales primarily along the number of API docs, MCP tooling access, and internal versus external (guest) user counts a team needs, rather than usage volume like API call counts. The jump from Basic to Pro adds the API Explorer for interactive request testing directly in the docs, branch-based staging of documentation changes, and deeper CI and Slack integration, while Enterprise adds SSO, white-labeling, and a formal SLA for organizations with compliance or brand requirements.
This pricing and feature structure signals who Bump.sh is really built for: API-first companies, developer platforms, and SaaS vendors that already treat their OpenAPI or AsyncAPI specification as a first-class artifact in their development process, and want documentation, changelogs, and now MCP server generation to be derived automatically from that spec rather than maintained as separate hand-written content. Teams without an existing machine-readable API specification, or with very simple, rarely changing APIs, may find a lighter-weight or free static documentation generator sufficient instead.
No. That consumer contact-sharing app, also called Bump, was acquired by Google and shut down in 2014. Bump.sh is a separate, unrelated company and product focused on API documentation, founded in 2017 in France and actively developed today.
Bump.sh supports OpenAPI 2.x, 3.0.x and 3.1.x for REST APIs, AsyncAPI 2.x and 3.x for event-driven APIs, plain JSON Schema, and workflow specifications including the Arazzo standard and Bump.sh's own Flower format.
Bump.sh's Basic plan starts at $50/month, the Pro plan is $250/month, and an Enterprise tier is available at custom pricing for larger organizations needing SSO, white-labeling, and an SLA.
Documentation is generated automatically from your OpenAPI or AsyncAPI specification file, and updates every time the spec changes, rather than requiring hand-written documentation content.
Yes, Bump.sh lets teams organize multiple OpenAPI and AsyncAPI-based documentation sets into a single developer hub for a unified, searchable entry point.
Yes, Bump.sh provides a CLI and native GitHub integration so documentation can be deployed automatically as part of a normal CI/CD pipeline, following a docs-as-code approach.
Open-source projects can apply for free access to Bump.sh's Pro plan, and all paid plans include a 14-day free trial.
Bump.sh can compile Arazzo or Flower workflow specifications into managed Model Context Protocol servers, letting teams expose their APIs to AI agents in a structured, observable way alongside their human-facing documentation.