Personal and team workspaces
Keep experimental personal packages separate from shared team packages that multiple developers and CI jobs rely on.
Teams
Package ownership that matches how teams ship.
Put shared repositories and CI credentials under the team, while developers keep their own accounts for sign-in and day-to-day work.
Access model
Shared packages without shared personal credentials
Ravenstash gives teams the basics they need to run private package workflows together: team spaces, members, shared repositories, and automation tokens.
Team repositories
Create shared private repositories for PyPI, npm, and Maven packages so the team has one trusted place to publish and install.
Invitations and members
Invite teammates, manage membership, and avoid losing the last admin who can manage the team.
Team automation tokens
Give CI and release pipelines their own credentials without sharing a personal password or tying builds to one developer.