Skip to content
Ravenstash
Create account
Private developer infrastructure

Dev infrastructure that feels like your favorite tools.

Ravenstash is private developer infrastructure with the speed and polish of the tools you reach for every day. Start with private package registries for PyPI, npm, Maven, container images, and Helm charts.

Create accountRead quickstarts

Browser sign-in · No credentials in project files · Unlimited data transfer

Artifacts

Products

One platform, built one product at a time

Every Ravenstash product shares the same sign-in, organizations, and CLI. Artifacts is the first.

Artifacts

Private registries for packages, container images, and Helm charts

Publish and install with the package managers your team already uses, and bring public dependencies in through protected private mirrors.

Explore Artifacts →
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/*
Artifacts

Protect what you depend on, deliver it everywhere

Private mirrors for public dependencies, a choice of where package files live, and fast authenticated downloads for developers and CI.

Protected dependency mirrors

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

Learn more →

Storage where you need it

Choose North America, the European Union, or storage your organization controls.

Learn more →

Global package delivery

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

Learn more →
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 Linux or macOSbash
curl -fsSL https://staging-hxa159.ravenstash.com/install.sh | bash
Sign in once. Keep your tools.
# Sign in once, in your browser
rvs auth login

# Pick a repository
rvs art select platform/packages

# Keep using the tools you know
rvs twine upload dist/*
rvs pip install internal-sdk
rvs npm install @acme/design-system

Linux, macOS, Windows, NixOS, and WSL on x86-64 and ARM64. Windows uses the PowerShell installer in the CLI guide.

Platform

The same foundation under every product

Accounts, organizations, credentials, and the rvs CLI work the same way across Ravenstash, so each new product starts out familiar.

Device login for rvs

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

Explore the CLI →

Organization ownership

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

See organizations →

Private by default

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

Read about security →

Dashboard visibility

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

Create account →
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, Pro is $7/month or $72/year ($6/month equivalent), and Team starts at $34/month. Create an account and publish your first private package.

Create accountRead the docs