Free for small teams, one price for the rest

No per-seat maths and no enterprise tier to unlock SSO. Both plans have every feature; the only difference is how many people are in your GitHub organisation.

Free

$0 for organisations with up to 5 members

Set up a free registry

No card, no time limit. Outside collaborators do not count as members.

Team

$100 per GitHub organisation per month, for more than 5 members. Unlimited users.

Start 3-month free trial

3 months free, and no card to start. Add one any time before the trial ends.

Everything is in both plans

No SSO tax, no feature gates: a team of three gets what a team of three hundred gets.

Every developer
Everyone in the organisation, and outside collaborators on the repositories they can read.
SSO and SCIM through GitHub
SAML SSO, provisioning and offboarding apply as they already do. No SSO tax.
Trusted publishing from GitHub Actions
OIDC in CI: no secrets to store for reading or publishing.
Provenance and immutable releases
Every CI-published version carries GitHub-signed proof of the workflow that built it.
The open-source verifier
Run it hourly in your own CI to check everything we write.
Search
cargo search returns your private crates first, then crates.io results.
Your data stays yours
Index and crates live in a repository your organisation owns.

Billing questions

Who counts as a member?

The active members of your GitHub organisation, as GitHub lists them. Outside collaborators and pending invitations do not count, and neither do CI jobs. One organisation gets one registry at your-name.privatecrates.dev; a second organisation has its own plan.

What happens when we grow past 5 members?

Nothing breaks. The 3-month free trial starts by itself, with no card, and the account page shows how long is left. Organisations that already have more than 5 members start the same trial with one click when they set up.

Each organisation gets one trial. An organisation that subscribes again later pays from the first day.

What if the trial ends and we have not added a card?

Publishing stops when the trial ends. Builds keep reading crates for 14 more days, so nothing breaks overnight, and adding a card or subscribing turns publishing back on. We remind you in the last 14 days: on the account page, and as a warning in cargo publish.

Can we cancel?

Yes, at any time, under Manage billing on the account page. Publishing stops at the end of the paid month; reading keeps working for 14 days after that, then stops too.

If your organisation shrinks to 5 members or fewer, it is free again straight away. The account page then suggests cancelling; we do not cancel for you, because member counts go up and down.

Nothing is deleted: your index and every crate file are in your own repository, and stay there.

What if a payment fails?

Your registry keeps working while Stripe retries the payment, and the account page says so. An admin can update the card under Manage billing.

Who manages billing?

Admins of the GitHub organisation: they start the trial, add a card and cancel, from the account page. Stripe handles cards and invoices. Members see the plan and the registry’s status, but cannot change them.