What is Repsy?

Repsy is a cloud-native artifact repository service for developers and teams.
It supports publishing and hosting packages in the following formats:

Key Features

Multi-format support
Host packages for different ecosystems from one account.
Token-based authentication
Secure and flexible access management.
Unlimited repositories
Create as many public or private repositories as you need.
Public or private access
Public repositories can be downloaded by anyone. Private repositories require a signed-in account or a deploy token. A deploy token is scoped to a single repository, so use one to give a CI job or an external party access to just that repository. Repsy has no per-repository collaborator lists; see Understanding Public vs Private for who can do what.
Free and paid plans
Storage limits, service levels and the other differences between the hosted plans are listed on the Repsy pricing page.
CI/CD ready
Easily integrate with your existing build pipelines.

Supported Use Cases

Private internal package hosting
Open-source libraries
CI/CD workflows
Docker image publishing

Plans, Storage and Availability

The storage and service levels of the hosted service at repsy.io depend on your plan. The pricing page is the single source of truth for them, so this documentation does not repeat any figures. If you run your own Repsy instance instead, storage and availability depend on your own infrastructure.

Was this page helpful?