Ravenstash
Package cache and proxy

Connect any package source through one private cache.

Use supported public registries or connect an external PyPI, npm, or Maven repository, whether it is public or protected by authentication. Access the cache directly or place it upstream of a private repository.

Build experiencetext
package manager -> private Ravenstash URL
package request -> approved source
first download -> fetched and cached
repeat download -> served faster
Why it helps

One private path to the packages your builds need

Give developers and CI one authenticated Ravenstash URL while keeping external package sources behind a controlled cache.

  1. 1

    Choose a supported public registry or connect your own package source.

  2. 2

    Add source credentials when the external repository requires them.

  3. 3

    Use its private URL directly or connect it to one of your private repositories.

  4. 4

    Ravenstash fetches packages on demand and keeps repeat installs fast.

Public package sources

Use familiar public sources for PyPI, npm, and Maven through a private Ravenstash URL.

Custom package sources

Connect an external package repository with or without source authentication.

Use it directly

Give the cache its own private package-manager URL for a clean, read-only dependency endpoint.

Use it as an upstream

Connect the cache behind a matching PyPI, npm, or Maven repository without changing normal install commands.

Cached on demand

Packages are retrieved when requested and kept ready for faster repeat builds.

Visible and manageable

Review cached packages, connected repositories, downloads, storage, and recent activity.

Questions

A private package cache without the maintenance burden

Connect the sources your team already uses and keep the developer workflow simple.

Can I connect a private external package repository?

Yes. A custom cache can connect to a public or private HTTPS package repository. Add source credentials when the external repository requires authentication.

Can I use a cache without connecting it to another repository?

Yes. Every cache can provide its own private package-manager URL, and it can also be connected as an upstream to one or more private repositories.

Does Ravenstash copy the entire external repository?

No. Ravenstash retrieves package content as it is requested and keeps cached copies for repeat installs.