Ravenstash
Create account
Private Package Repositories

Private package repositories
for developer teams.

Create one private package repository for PyPI, npm, Maven, or any combination. Publish with standard tools, install through native authenticated endpoints, and manage personal or organization ownership in one place.

Create accountRead quickstarts

Works with

PyPInpmMavenCustom package cachesOrganizations
Native workflows

Use the package managers your team already trusts

One repository can support several ecosystems, each with its own package-manager URL. Developers keep using familiar install and publish commands.

Python packages

Private PyPI Registry for Python

Host private Python packages in a PyPI-compatible registry with pip, uv, Poetry, and Twine publish and install paths.

View PyPI page
Install from a private indexbash
python -m pip install \
  --index-url https://__token__:${RAVENSTASH_TOKEN}@pypi.pkg.rvsta.sh/x/_wsabc123/_repo1234/simple/ \
  internal-sdk
Publish with Twinebash
python -m build
python -m twine upload \
  --repository-url https://pypi.push.rvsta.sh/x/_wsabc123/_repo1234/ \
  dist/*
Ravenstash CLI

Sign in and manage package workflows from your terminal.

Use browser-based device login, work with private repositories, and run pip, uv, Twine, npm, or Maven with temporary Ravenstash authentication.

Explore the CLI

Install on Debian or Ubuntu

curl --proto '=https' --proto-redir '=https' --tlsv1.2 -fsSL https://staging-hxa159.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 the essentials teams need now: private repositories, familiar package-manager commands, shared API tokens, custom package caches, and clear package activity.

Private by default

Developers need Ravenstash credentials to publish or install from current 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.

Custom package caches

Connect public or authenticated package sources, then use the private cache directly or behind a private repository.

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.

Storage and delivery

Control where packages live and serve them worldwide

Choose managed or customer-owned package storage, keep package data at rest inside the EU, and deliver authenticated downloads through 300+ locations.

Package storage choices

Choose a North America or EU at-rest origin, or use storage your organization controls, without limiting worldwide delivery.

Learn more →

Bring your own storage

Keep critical package IP in any S3-compatible storage service while Ravenstash runs the private registry workflow.

Learn more →

300+ delivery locations

Real download usage populates nearby caches for low-latency, high-speed access across regions and cloud environments.

Learn more →
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. The included delivery is generous enough that I don't have to watch a 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

Ecosystems

One dashboard for private packages and package caches

Each registry page shows the commands and setup path developers need to start using Ravenstash quickly.

PyPI

Host private Python packages in a PyPI-compatible registry with pip, uv, Poetry, and Twine publish and install paths.

npm

Publish and install private Node.js, JavaScript, TypeScript, and WebAssembly packages through npm-compatible registry routes for npm, Yarn, pnpm, and Bun workflows.

Maven

Host private Java, Kotlin, Scala, and JVM artifacts with Maven-compatible publishing, dependency resolution, checksums, and authenticated downloads.

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.

Create accountRead the docs