Ravenstash
Private artifact repositories

Every package your team needs.
Private, protected, and fast.

Publish private packages and protect public dependencies across PyPI, npm, Maven, Container, and Helm with familiar developer tools.

Works with

PyPInpmMavenContainerHelm OCIProtected dependency mirrorsOrganizations
Familiar workflows

Use the package managers your team already trusts

Choose a repository with rvs, then keep using familiar install and publish commands across every supported ecosystem.

Python packages

Private Python Package Repository

Host private Python packages in a PyPI-compatible repository with secure rvs workflows for pip, uv, Poetry, and Twine.

View PyPI page
Install from a private indexbash
rvs art select platform/packages
rvs pip install internal-sdk
Publish with Twinebash
rvs art select platform/packages
rvs uv build
rvs twine upload dist/*
Ravenstash CLI

Sign in and manage package workflows from your terminal.

Sign in through your browser, choose a private repository or mirror, and use package tools without managing registry credentials by hand.

Explore the CLI

Install on Debian or Ubuntu

curl -fsSL https://ravenstash.com/install.sh | bash

Ubuntu 20.04+ or Debian 11+, Linux amd64. The installer verifies the APT signing-key fingerprint before installing rvs.

Private package platform

Everything your team needs to publish, protect, and deliver packages

Start with private repositories, rvs package workflows, organization automation tokens, protected dependency mirrors, and clear package activity.

Private by default

Developers need Ravenstash credentials to publish or install from private repositories, so internal packages do not become public by accident.

Organization ownership

Give CI tokens and shared repositories to the organization, not to one developer's personal account.

Protected dependency mirrors

Use public dependencies through private mirrors with authentication, security scanning, minimum package age, and faster repeat installs.

Global package delivery

Serve authenticated package downloads through 300+ locations built for low latency and high-throughput CI.

Dashboard visibility

See what packages exist, which versions are used, and how storage and downloads grow over time.

Device login for rvs

Developers sign in to the rvs CLI through the browser and can revoke active device sessions from the dashboard.

Customer perspectives

Built around the package problems global teams recognize

Composite examples reflecting common package workflows and concerns.

“I thought the monthly price was per user. It wasn't. I checked twice because the other quote on my desk was nearly ten times higher.”

Daniel C.

Startup founder · Boston, MA

“Our CI pulls packages all day. Unlimited egress means I don't have to watch a bandwidth meter every time we add more runners.”

Ethan B.

Build systems engineer · Austin, TX

“When I created the repository, I could choose to keep the package files in the EU. That made the compliance discussion very short.”

Lucas M.

Engineering manager · Paris

“Our packages are part of the product, so we keep them in our own storage. Developers still publish and install normally. That's exactly what I wanted.”

Mei L.

Security architect · Singapore

“I expected a long setup and had a package published before my coffee got cold. Everything feels simple and considered. Honestly, congrats.”

Maya C.

Platform engineer · San Francisco, CA

“The main project is public, but the release tools and sponsor builds aren't. I can keep the same package workflow without running another service myself.”

Jamal P.

Open-source maintainer · Atlanta, GA

Free to start

Start with private repositories.

Individual plans start free, Premium is $7/month or $72/year ($6/month equivalent), and Team starts at $34/month. Create an account and publish your first private package.