Ravenstash hosts and registry URLs

Ravenstash separates the web app, developer API, package downloads, and package uploads by host.

Product hosts

Surface	Host
Marketing website	https://ravenstash.com
Documentation	https://docs.ravenstash.com
App and dashboard	https://app.ravenstash.com
Developer API	https://api.ravenstash.com

Package-manager hosts

Ecosystem	Install	Publish	Private mirror
PyPI	https://pypi.rvsta.sh	https://push.pypi.rvsta.sh	https://mirror.pypi.rvsta.sh
npm	https://npm.rvsta.sh	https://push.npm.rvsta.sh	https://mirror.npm.rvsta.sh
Maven	https://maven.rvsta.sh	https://push.maven.rvsta.sh	https://mirror.maven.rvsta.sh

OCI registry host

Container images and Helm OCI charts use one authenticated endpoint for native reads and writes:

oci.rvsta.sh/{namespace_name}/{repository_name}/{oci_repository_path}

oci.rvsta.sh serves the private OCI format for both container images and Helm charts.

Docker-style references omit a URL scheme:

oci.rvsta.sh/platform/runtime-images/acme/api:1.0.0

Helm uses the oci:// scheme expected by the client:

oci://oci.rvsta.sh/platform/deployment-charts/charts/api

The same host serves both kinds. Do not add /container/ or /helm/ to the address; copy the exact repository target shown by Ravenstash.

Every enabled package registry appends a namespace and repository route. PyPI install URLs also append /simple/ for the package index.

https://pypi.rvsta.sh/in/{repository_permanent_id}/simple/
https://push.pypi.rvsta.sh/in/{repository_permanent_id}/

https://npm.rvsta.sh/in/{repository_permanent_id}/
https://push.npm.rvsta.sh/in/{repository_permanent_id}/

https://maven.rvsta.sh/in/{repository_permanent_id}/
https://push.maven.rvsta.sh/in/{repository_permanent_id}/

Name-based package and OCI routes use the current namespace and repository names. ID-based targets use the literal internal-realm coordinate in and the repository permanent ID. The repository’s current namespace remains the authorization and member-access boundary even though it is absent from the URL. The rvs CLI refreshes those names before launching a package tool, so normal interactive commands follow renames automatically.

ID-based package URLs use in/ar_.... OCI accepts the same target. The former in_.../ar_... form is rejected rather than redirected. The ID-based target remains available for jobs that must continue working across renames.

Direct private-mirror URLs use the mirror host. Copy the exact URL shown by the selected mirror rather than constructing one manually.

Storage hosts for Turbo mode

With Turbo mode, a large package file, container image layer, or Helm chart is downloaded straight from storage instead of from the registry host. Turbo mode is on by default. If your network, proxy, or firewall only allows listed hosts, also allow these over HTTPS (port 443):

• Ravenstash Turbo compatibility host: art-turbo-compat.rvsta.sh. Some tools pass through it on the way to storage. If you already allow every host ending in .rvsta.sh, it is covered.
• Ravenstash-managed storage: hosts ending in .r2.cloudflarestorage.com. Storage in the European Union uses hosts ending in .eu.r2.cloudflarestorage.com, which the same rule covers.
• Your organization’s own storage: the hosts of the storage service you connected, listed under Bring your own storage.

Match these names by their ending. A storage host has several name levels before it, so a pattern that covers only one level, such as a single *, may not match.

Smaller files and resumed or partial downloads stay on the registry host. If the storage hosts cannot be allowed, turn Turbo mode off; every download then comes from the registry host.

Generic browser transfer hosts

Browser downloads and uploads may use art.rvsta.sh and push.rvsta.sh. Package tools should be launched through rvs, which selects the registry-specific host.

Use generated values

Copy the generated rvs command from the selected PyPI, npm, Maven, or OCI tab. It includes the correct repository target and format.