Your storage account
Package files remain in S3-compatible storage owned and managed by your organization.
Keep critical package files in storage controlled by your organization while Ravenstash manages publishing, authenticated access, package metadata, and global delivery.
Ravenstash provides the private package registry while your organization retains control of the storage holding its binary package data.
Package files remain in S3-compatible storage owned and managed by your organization.
Developers continue publishing and installing through Ravenstash with the package tools they already use.
Keep binary package data outside Ravenstash-owned storage without operating a complete package registry yourself.
The same storage choice can hold the PyPI, npm, and Maven files in a multi-ecosystem repository.
Ravenstash stays responsible for the developer-facing package experience. Your storage service holds the binary package data that represents your critical intellectual property.
Connect S3-compatible storage controlled by your organization.
Select it for a private repository or custom package cache.
Publish and install through the same Ravenstash package URLs.
Move storage later without renaming the repository or packages.
Keep the registry familiar for developers while choosing where package files live.
Ravenstash can connect to any S3-compatible object storage service that your organization chooses.
No. Developers and build systems continue using authenticated Ravenstash package URLs and normal package-manager commands.
Yes. A repository can move between Ravenstash-managed storage and customer-owned storage without changing its package identity.