# Protorip (protos.rip) > Drop-in Protobuf schema registry implementing the open Buf Schema Registry (BSR) protocol for the `buf` CLI, with flat pricing and no per-type or per-seat charges. Use this guide when configuring a repository to consume modules, run remote code generation, migrate from `buf.build`, or publish schemas to `protos.rip`. For general `buf` CLI commands, configuration reference, and linting/breaking checks, consult the official Buf CLI docs (`https://buf.build/docs/cli/`). ## Prerequisites and hard constraints - **CLI version:** `buf` `>= v1.32.0` is required; `>= v1.46.0` is recommended for `buf registry whoami` and stable module, label, and commit commands (`v1.47.0+` also supports `buf registry module label` and `buf registry module commit`). Check `buf --version` before running commands. - **Configuration format:** Only `version: v2` `buf.yaml` and `b5:` digests in `buf.lock` are supported. `v1` configurations and `b4:` digests are rejected. - **No cross-registry federation:** The `buf` CLI hardcodes a federation allowlist that excludes `protos.rip`. Every transitive dependency in your graph must be hosted on `protos.rip`. Core public dependencies are mirrored at matching `/` paths. - **Unsupported features:** - Hosted language package feeds / Generated SDKs (`npm`, Go proxy, PyPI, Maven, Cargo, Swift) are not hosted; generate code with `buf generate` in local or CI builds. - Push-time server-side quarantine gates are not supported; run `buf lint` and `buf breaking` in your own CI before `buf push`. - `buf alpha registry token`, `buf beta registry webhook`, and `buf registry sdk info` are not supported. Create API tokens in the dashboard. ## Discover supported modules and plugins Before guessing a dependency path or plugin version, check the live registries on `protos.rip`: - **Public modules:** Browse `https://protos.rip/registry` (or check `https://protos.rip//` directly, or `https://protos.rip/sitemap-modules.xml`) to verify whether a public module or transitive dependency is hosted on `protos.rip`. - **Remote plugins:** Browse `https://protos.rip/plugins` (supports `?scope=`) and check `https://protos.rip/plugins//` to verify whether a plugin and specific version tag are listed as `Available` (versus `Unsupported` or `Unavailable`). Protorip maintains current and recent releases for active community plugins rather than every historical version. ## Consume public modules and remote plugins (no account required) Anonymous requests can resolve public modules and run remote code generation without logging in. Curated core modules use identical paths to `buf.build`: - `protos.rip/googleapis/googleapis` - `protos.rip/bufbuild/protovalidate` - `protos.rip/envoyproxy/protoc-gen-validate` - `protos.rip/grpc-ecosystem/grpc-gateway` Example `buf.yaml`: ```yaml version: v2 deps: - protos.rip/googleapis/googleapis - protos.rip/bufbuild/protovalidate ``` Example `buf.gen.yaml` using hosted community remote plugins: ```yaml version: v2 plugins: - remote: protos.rip/protocolbuffers/go out: gen/go opt: paths=source_relative - remote: protos.rip/connectrpc/go out: gen/go opt: paths=source_relative ``` Run dependency resolution, build, and code generation: ```bash buf dep update buf build buf generate ``` Anonymous `buf generate` limits: cached generations are unlimited; uncached plugin executions are limited to 5 per hour shared per IP (20s default timeout, up to 60s for JVM/Node plugins, 400 MiB output limit). Signing in applies account-level limits. ## Migrate an existing repository from buf.build Follow this exact order so `v1` configs are upgraded before switching registries: 1. Check `buf --version` (`>= v1.32.0`, recommend `>= v1.46.0`). 2. If `buf.yaml` uses `version: v1`, run `buf config migrate` against your existing registry configuration before changing module names or dependencies to `protos.rip`. 3. Replace `buf.build/` with `protos.rip/` in: - `buf.yaml` (`modules[].name` and `deps[]`) - `buf.gen.yaml` (`plugins[].remote`) - CI scripts and workflows (`buf registry login`, `buf push`, `buf registry module ...`) 4. Run `buf dep update` to rewrite `buf.lock` with `protos.rip` `b5:` digests. 5. Verify locally with `buf build` and `buf generate`. 6. Once a human authenticates the CLI (next section), create the module on `protos.rip` and push: ```bash buf registry module create protos.rip// buf push ``` ## Account setup and authentication (requires a human) Agents cannot create accounts headlessly. Sign-up uses GitHub or Google OAuth in a browser. Complete any `buf.yaml`, `buf.gen.yaml`, `buf dep update`, and `buf build` steps first, then ask the user to authenticate: 1. Direct the user to `https://protos.rip/dashboard` to sign in with GitHub or Google and claim their `` handle. 2. Choose one CLI login method: - **Interactive terminal (device approval flow):** Run `buf registry login protos.rip`. The CLI prints a verification URL and an 8-character code (`XXXX-XXXX`, valid for 10 minutes). Give both to the user to approve in their browser. - **Headless / CI / sandboxed environment:** Ask the user to create an API token at `https://protos.rip/dashboard/account/tokens` and supply it as `PROTORIP_TOKEN`, then run: ```bash echo "$PROTORIP_TOKEN" | buf registry login protos.rip --token-stdin ``` (On `buf` CLI `< v1.35.0`, also pass `--username `.) Verify login (`buf` `>= v1.46.0`): ```bash buf registry whoami protos.rip ``` ## Create and publish modules Configure `buf.yaml` with your module name: ```yaml version: v2 modules: - path: proto name: protos.rip// ``` Common publishing and management commands: ```bash buf registry module create protos.rip// buf push buf push --label v1.0.0 buf registry module info protos.rip// buf registry module deprecate protos.rip// buf registry module undeprecate protos.rip// buf registry label list protos.rip// buf registry commit list protos.rip// ``` (On `buf` CLI `< v1.36.0`, use `buf push --create` instead of `buf registry module create`.) ## Plans and limits - **Free ($0):** unlimited public modules, 1 private module, 1 user, 5 uncached `buf generate` runs/hour (1 concurrent; cached results unlimited). - **Solo ($9/mo or $84/yr):** unlimited private modules, 1 user, 4 concurrent / 2,000 full-concurrency uncached `buf generate` runs/month. - **Team ($49/mo or $490/yr):** unlimited private modules and members, 20 concurrent / 50,000 full-concurrency uncached `buf generate` runs/month. - **Open source ($0):** Team-equivalent limits for eligible public OSS projects (`https://protos.rip/oss`). Paid Solo and Team plans use fair-use concurrency limits with no overage fees or hard monthly cutoffs. ## Links - Home: https://protos.rip/ - Dashboard & tokens: https://protos.rip/dashboard - CLI compatibility: https://protos.rip/compatibility - Remote generation: https://protos.rip/remote-generation - Public module registry: https://protos.rip/registry - Public module sitemap: https://protos.rip/sitemap-modules.xml - Remote plugin registry: https://protos.rip/plugins - Pricing: https://protos.rip/pricing - Protorip vs buf.build: https://protos.rip/compare/buf - Official Buf CLI docs (commands, `buf.yaml`, `buf lint`, `buf breaking`): https://buf.build/docs/cli/ - Official Buf remote plugins docs (`buf.gen.yaml`, managed mode): https://buf.build/docs/generate/remote-plugins/