Automatically generate easy to read documentation based on your Protocol Buffers schema.
Never write standalone API docs again.
Start treating your API definition like the critical asset it is.
Never write standalone API docs again.
Improve service discovery by generating documentation for all of your API versions. All available in a browseable UI.
Make your service easier to grok with a consistent visual representation, updated in real time for every new version of your API.
*Currently available in Go, with more languages coming soon.
Generate consistent, versioned libraries across all of your services without heavyweight custom build scripts.
Eliminate the need to manually manage generated assets.
Consume APIs as if they’re 3rd party libraries in your native language.
Buf is pioneering a Protocol Buffers module ecosystem, enabling you to make the most of your APIs.
Call your APIs confidently, without having to coordinate with other teams or worry about breaks. Rely on a single source-of-truth.
Treat Protocol Buffers dependencies as first class citizens. No more manually copy-and-pasting external proto files into your source.
Stop vendoring commonly used proto files that litter your codebases.
Generate a CLI for your API definition, with configurable mapping from endpoint to the command and its arguments, flags, and help text.
Test your schema design without having to implement a server. The Buf generated mock-servers will spin up valid responses with mock data based solely on your proto definitions.
Configure build requirements that enforce adherence to semantic versioning and lint checks on your published API.
Teams define Protocol Buffers schemas for services they own, leveraging the Buf CLI.
The schema is pushed to the Buf Schema Registry.
Teams consume assets from Buf to interact with the service, including generated docs and libraries.