Kellnr review
A focused, open-source Cargo registry for teams managing private Rust packages.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
Kellnr is an open-source, self-hosted private registry for proprietary Rust crates. It is designed for organizations and individuals that want to publish and manage packages through Cargo, while also providing a web interface for crate, version, and metadata management. Access can be organized through users, groups, roles, tokens, and crate ownership, with optional authentication for crate downloads. Rust teams that need control over private package distribution are the clearest fit.
The published product details show a free, open-source model rather than a tiered commercial plan structure. Kellnr can run with a local filesystem, S3, or Google Cloud Storage backend, giving teams options for how packages are stored. Its ecosystem fit centers on Cargo and crates.io, with additional compatibility across Docker, Kubernetes, Helm, PostgreSQL, SQLite, and OpenID Connect. A REST API and webhooks support integration with surrounding development and delivery workflows.
Its standout strength is the combination of private crate hosting and Rust-specific documentation support. Kellnr can automatically generate Rustdoc and accept custom documentation uploads, while its crates.io proxy and cache can support access to upstream crates. That focused scope is also the main boundary: teams seeking a general-purpose repository for many package ecosystems may prefer a broader artifact platform. Choose Kellnr when self-hosted Rust package management, fine-grained access control, and Cargo compatibility matter most; look elsewhere when the primary requirement is broad artifact coverage or a managed service.
Kellnr pros and cons
- Where it wins
- Cargo-compatible publishing with web-based crate and metadata management
- Fine-grained control for users, groups, roles, tokens, and ownership
- Crates.io proxying, Rustdoc generation, APIs, webhooks, and flexible storage
- Where it doesn't
- Focused on Rust crates rather than a broad range of artifact formats
- Self-hosted deployment puts infrastructure operation on the organization
- Documentation and access features may exceed simpler registry needs
Kellnr fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. We may earn a commission when you click some links. How we rank.
Last updated · How we research and update