Review repository usage and activity

View	Shows
Dashboard	Repositories available through your personal account and organization memberships.
Repository	Total packages, versions, storage, bandwidth, and recent activity across enabled ecosystems.
PyPI, npm, or Maven tab	Packages, uploads, upstream configuration, and usage for that ecosystem.
Package and file	Ecosystem-specific details and recorded downloads.
Private mirrors	Mirrored packages, connected repositories, recency, downloads, and bandwidth.

Local package-manager caches and downloads served outside Ravenstash are not visible here.

Note

Usage views compare storage and artifact reads with the allowances in your plan. Delivered bytes remain visible as informational bandwidth even though egress is unlimited. You can choose and manage a paid plan from the Ravenstash dashboard.

Artifact reads

Plan	Monthly artifact reads
Free individual	5,000
Premium	30,000
Free organization	0
Team	100,000
Business	250,000
Enterprise	500,000 by default, informational; contract overrides apply

Free organizations can upload up to 10 GB. Package downloads and registry metadata requests are blocked until a paid plan is active. Paid self-service plans can continue downloading above their allowance at $0.15 per 1,000 excess reads. Enterprise allowances are informational and do not stop downloads.

An artifact read is one successful request to download a package payload or an OCI blob, such as a container image layer. It counts requests, not bytes or installs: one install can download several files, while a local package-manager cache can avoid downloads entirely.

Request	Counts as an artifact read?
Successful package payload download, such as a Python wheel, npm archive, or Maven JAR	Yes
Successful OCI blob download for Container or Helm	Yes
Successful partial download (HTTP 206)	Yes, once per range request
Successful retry of a download	Yes, each successful response counts separately
Download redirected to a storage provider	Yes, once when Ravenstash hands off the download
Package metadata, indexes, or version listings	No
OCI manifests or image indexes	No
Maven POM, checksum, or signature files	No
HEAD requests or 304 Not Modified responses	No
Failed or denied requests	No
Uploads or Ravenstash’s internal traffic	No

Serving a download from Ravenstash’s cache still counts. Reusing a file already cached on your machine without requesting it from Ravenstash does not. For example, downloading a wheel and then successfully retrying it counts as two reads; checking its metadata first adds no reads.

Artifact reads and bandwidth measure different things. A small file and a large file each count as one read when downloaded in one successful request. View delivered bytes in a repository’s Metrics tab.