Package storage
Ravenstash supports managed storage and reusable customer-owned storage targets for private package files and custom package caches:
| 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 - GDPR Compliance | Your compliance framework requires package files to remain physically stored inside the European Union. |
| Customer-owned storage | Package files should remain in a storage account and configuration controlled by your organization. |
Storage choice controls the origin location of package data at rest. It does not change repository names, package URLs, package-manager commands, or the global delivery footprint available to downloads.
At-rest location is separate from delivery
Section titled “At-rest location is separate from delivery”Ravenstash’s authenticated content delivery network spans 300+ geographic locations. Package files can be cached close to real download demand for low-latency, high-speed access, regardless of whether their at-rest origin is in North America, the European Union, or customer-owned storage.
The first uncached request may read from the selected origin. Later requests can be served from locations populated by actual package usage; Ravenstash does not pre-replicate every package to every location.
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. See Package storage locations for selection guidance.
Defaults and repository choices
Section titled “Defaults and repository choices”Choose a default for your account or organization. A workspace can use that default or select another storage option.
New repositories and custom caches use the applicable default unless you choose another option during creation. Changing a default does not move existing package files.
To change storage for an existing repository or custom cache, start a storage move from its settings.

