Personal and organization ownership
Keep experimental personal packages separate from shared organization packages that multiple developers and CI jobs rely on.
Organizations
Package ownership that matches how your company ships.
Put shared repositories and CI credentials under the organization, while developers keep their own accounts for sign-in and day-to-day work.
Access model
Shared packages without shared personal credentials
Ravenstash lets each user keep personal repositories while organization memberships provide access to shared repositories and API tokens.
Organization repositories
Create shared repositories that accept PyPI, npm, Maven, or any combination under one organization-owned name.
Invitations and members
Invite members, manage membership, and avoid losing the last admin who can manage the organization.
Organization API tokens
Give CI and release pipelines their own credentials without sharing a personal password or tying builds to one developer.