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 →Private registries without the friction.
Host everything your team builds in one private place, and keep using the package managers you already know. Ravenstash handles access, security, and delivery.
Browser sign-in · No credentials in project files · Unlimited data transfer
One platform, built one product at a time
Every Ravenstash product shares the same sign-in, organizations, and CLI. Artifacts is the first.
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 pagervs art select platform/packages
rvs pip install internal-sdkrvs art select platform/packages
rvs uv build
rvs twine upload dist/*Node.js and JavaScript packages
Private npm Repository for Node.js and JavaScript
Publish and install private Node.js, JavaScript, TypeScript, and WebAssembly packages with familiar rvs workflows for npm, Yarn, pnpm, and Bun.
View npm pagervs art select platform/packages
rvs npm install @acme/design-systemrvs art select platform/packages
rvs npm publishJava and JVM artifacts
Private Maven Repository for Java, Kotlin, and Scala
Host private Java, Kotlin, Scala, and JVM artifacts with Maven-compatible publishing, dependency resolution, checksums, and authenticated downloads.
View Maven pagervs art select platform/packages
rvs mvn verifyrvs art select platform/packages
rvs mvn deployOCI and Docker-compatible images
Private Container Image Repository
Push, pull, and manage private OCI and Docker-compatible container images with familiar rvs Docker and ORAS workflows.
View Container pagervs art select platform/runtime-images
rvs docker build -t acme/api:1.0.0 .
rvs docker push acme/api:1.0.0rvs art select platform/runtime-images
rvs docker pull acme/api:1.0.0Helm charts over OCI
Private Helm Chart Repository
Publish, manage, and install private Helm OCI charts with familiar rvs Helm workflows, organization ownership, and global delivery.
View Helm OCI pagervs art select platform/deployment-charts
rvs helm package ./charts/api
rvs helm push api-1.2.3.tgz chartsrvs art select platform/deployment-charts
rvs helm pull charts/api --version 1.2.3Artifacts
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 CLIcurl -fsSL https://ravenstash.com/install.sh | bash# 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-systemLinux, macOS, Windows, NixOS, and WSL on x86-64 and ARM64. Windows uses the PowerShell installer in the CLI guide.
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
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.