Storage and package delivery
Storage placement controls where package files remain at rest. Package delivery controls how authenticated developers and CI retrieve them. Choosing a storage location does not change repository names, package-manager commands, or the delivery footprint.
Choose what you need to do
Section titled “Choose what you need to do”Choose where packages are stored
Section titled “Choose where packages are stored”Ravenstash supports managed storage and, for eligible organizations, reusable customer-owned storage choices for private packages:
| Storage choice | Use it when |
|---|---|
| North America | You want the default managed at-rest location and do not require an EU physical-storage boundary. It does not provide a country-specific physical-residency guarantee. |
| European Union | Your compliance framework requires package files to remain physically stored inside the European Union. Availability depends on the selected plan. |
| Customer-owned storage | An eligible organization needs package files in its own Cloudflare R2 or OVH Object Storage account. |
The European Union location provides a strict physical-storage boundary for package files. GDPR can also permit data transfers outside the EU when the required safeguards are in place, but an organization’s own policies, contracts, or controls may require EU physical storage.
Storage location is separate from delivery
Section titled “Storage location is separate from delivery”Every storage choice includes authenticated package delivery through more than
300 locations. Developers and CI keep the same repository and rvs commands
whether packages are stored in North America, the European Union, or
customer-owned storage.
Content delivery does not make repositories public and does not move the at-rest copy of a package into another storage region.
Defaults, exceptions, and moves
Section titled “Defaults, exceptions, and moves”Choose a default storage assignment for a personal account or organization. A namespace can use that default or select another available option.
New repositories use the applicable default unless an eligible repository exception is selected. New custom package caches inherit the customer default. Changing a default does not move existing package files.
Organization administrators can move existing repository files by selecting one or more namespaces in the storage inventory. Custom package caches cannot be moved independently.