At Redpanda, delivering exceptional developer experience is crucial for the adoption of their next-generation data streaming platform. When their existing API documentation stack became a bottleneck, they needed a partner who could deliver both performance and flexibility. With Bump.sh, Redpanda reduced their API documentation work resolution time by 60% and freed up engineering resources to focus on what matters most: building great products.
Before Bump.sh: functional but limited
Redpanda’s API documentation journey began with Redoc, then evolved to Rapidoc when they launched their Cloud API public beta. The team chose Rapidoc for several key features:
- “Try it out” feature that allowed readers to quickly test API calls from the docs.
- Ability to inject some custom content alongside endpoint documentation.
- Free custom domain support to maintain their branded experience.
However, as time went by, limitations appeared:
- Manual customization burden: Improving the look and feel required intensive manual work and engineering resources.
- Fragmented documentation: No support for dedicated custom pages meant maintaining conceptual docs entirely separately from API reference docs.
- No change management: Without an automated changelog, breaking change detection or notification systems, tracking API updates relied on difficult-to-parse git diffs.
As Kat, Senior Technical Writer, explains:
As Redpanda as a company grew and many of our products matured (for example, our Cloud API was about to move out of beta to general availability), we were feeling the need to tighten our internal doc processes and reduce the time and resources required to maintain our API docs.
What led them to Bump.sh
The Redpanda team had clear requirements for their next documentation platform. Unlike other platforms, Bump.sh offered not just the required features, but also advanced capabilities they anticipated needing:
- Essential features: An API Explorer, custom domain and branding, API docs allowing for dedicated content pages.
- Process improvements: Overlays for fine-grained spec editing, and automated changelog capabilities.
- Future-proofing: API docs branching, and emerging standards support.
Why Bump.sh won out
Several factors made Bump.sh the clear choice:
- Complete feature set: All must-haves were offered.
- Partnership approach: The Bump.sh team was committed to collaborative problem-solving, not just selling a product.
The Bump.sh’s team was very attentive to our questions and requests and always took them as opportunities to guide, educate, and problem-solve together.
Smooth onboarding with structured support
Redpanda’s migration experience highlighted Bump.sh’s partnership approach:
- Biweekly onboarding meetings provided regular touchpoints without overwhelming the team.
- Project dashboard kept everyone organized and visualized progress.
- Frequent async communication enabled continuous collaboration between formal meetings.
The team was happy to provide targeted/curated resources, 1:1 support, and jump on quick calls, especially for the trickier aspects of the technical integration with the platform.
One month in: immediate transformation
Within the first month, Redpanda saw concrete improvements across multiple areas:
- Streamlined reader experience: No more context-switching between quickstart, browser testing, and API reference.
- OAuth 2 enabled API Explorer launched for Cloud APIs.
- Documentation branches supported their new Admin API v2 launch.
Behind the scenes:
- Shared overlays streamlined changes across multiple specs using GitHub Actions.
- Intuitive CLI integration: Even non-CLI users found the Bump.sh CLI easy to adopt.
As Kat describes the empowerment:
There is so much you can control and customize through the Bump.sh admin dashboard. In the past, I’ve had to check with our lead docs engineer regarding what feels like should be a simple fix; it feels so much more empowering to know that I can make quick improvements and fixes to our API docs even with just a few clicks in the browser.
Looking ahead: focusing on content quality instead of maintenance
The Bump.sh partnership positioned Redpanda for their next growth phase:
- API expansion confidence: Ready to deliver docs for new APIs without compromising reader experience.
- Strategic alignment: Bump.sh’s roadmap complements Redpanda’s evolution toward Agentic Data Plane.
- Resource optimization: Engineering time freed up for internal tools and process enhancement.
Using Bump.sh has meant that we can focus more of our time on content writing and addressing our readers’ needs, instead of architecting solutions from scratch or finding workarounds.
Advice for other technical leaders
When asked how she’d recommend Bump.sh to other teams, Kat emphasized the partnership approach:
Be clear on your must-haves versus nice-to-haves, but don’t hesitate to bring any ideas, feedback, questions, or suggestions to the Bump.sh’s team, since they really take these as opportunities to build a partnership with you.
Key results
- Productivity: 60% reduction in API documentation work resolution time.
- Experience: Unified reader journey from quickstart to API reference to testing.
- Empowerment: Dashboard controls eliminated engineering bottlenecks for simple doc updates, while workflow integration made global updates seamless.
- Collaboration: A genuine partnership that made the new API doc portal meet every requirement.
🔑 Takeaway: For Redpanda, Bump.sh delivered immediate productivity gains while building a reliable foundation for future iterations of their documentation portal, proving that the right documentation platform is both a tactical solution and a strategic advantage.
About Redpanda
Redpanda is building the next-generation data streaming platform, designed to be the most developer-friendly, operationally simple, and cost-effective solution for real-time data processing. With their innovative Agentic Data Plane, Redpanda is evolving beyond traditional data streaming to enable seamless, AI-powered data experiences for modern applications.
