Package storage locations

Package storage locations define where Ravenstash keeps the origin copy of your package files at rest. They do not restrict where developers, CI runners, or deployment systems can download those packages.

Ravenstash-managed package storage is available in two customer-facing locations:

Location	Choose it when
North America	You want the default managed at-rest location and do not require an EU physical-storage boundary. This option does not make a country-specific physical-residency commitment.
European Union - GDPR Compliance	Your organization requires package files to be stored physically within the European Union. This location provides an EU storage boundary rather than a best-effort location preference.

The selected location applies to uploaded package files and eligible custom-cache files. It does not change repository URLs, authentication, or package-manager configuration.

Storage at rest, delivery worldwide

Ravenstash delivers authenticated packages through a content delivery network spanning 300+ geographic locations, regardless of the selected at-rest storage location.

Cache placement follows real download usage. An uncached request may read from the package’s at-rest origin; repeated and geographically distributed downloads can then be served closer to the developers and CI runners requesting them. This usage-driven model is built for low latency and high-speed delivery without pre-copying every package to every network location.

Changing a storage location changes the at-rest origin. It does not limit the global delivery footprint available to package consumers.

GDPR and physical storage

GDPR does not require every European organization to store all data physically inside the EU. Personal data can be transferred outside the European Economic Area when the applicable transfer mechanism and safeguards are in place. See the European Commission’s guidance on international data transfers.

Your organization’s requirements can be stricter than GDPR alone. Internal data residency policies, customer contracts, sector-specific controls, or risk frameworks may require physical storage within the EU. Choose European Union - GDPR Compliance when that boundary applies to package files, and confirm the scope of your requirements with your legal or compliance team.

Choose a location

For teams without an EU residency requirement, North America is the default managed at-rest choice. Origin location can affect uploads and an uncached origin read, but routine download performance is handled by the usage-driven delivery network.

Choose the European Union location whenever EU physical storage is a requirement, even if another location may be closer to some package consumers.

Set the default

1. Open storage settings for the personal account or organization.
2. Choose Ravenstash-managed storage.
3. Select North America or European Union - GDPR Compliance.
4. Save the default.

A workspace can inherit the account or organization default or use an explicit assignment.

Defaults apply to new repositories and custom caches. Changing a default does not relocate existing package files. Move an existing repository or custom cache from its own storage settings when its files need a different location.