Crate
A self-hosted, unmetered private Composer registry for Laravel, on Laravel Cloud.
Crate is MIT licensed. Fork it and run it yourself for free, forever — or let Scalpels do the setup on your own Laravel Cloud account.
A private registry you own
Crate is a private Composer registry you host yourself. Register the private repositories you want to serve, and Crate builds Composer metadata and mirrored dist archives for them and serves both behind a credential gate on infrastructure you control.
It is unmetered by construction, because there is no meter: each deployment is single-tenant and sits in your own account, so there is no per-seat registry bill and no third party holding your private packages.
Built for Laravel Cloud ownership
Crate follows the same fork-and-own-it model as the rest of Built for Cloud. You fork the application, connect it to Laravel Cloud, and run your own registry on your own compute, database, queue and object storage.
Consuming it is ordinary Composer. Point a repository entry at your Crate host, hand the application its credential, and `composer require` resolves your private packages through the gate exactly as it resolves public ones.
Credentials you issue and revoke
Access is credential-level. An admin-token guarded API issues a named credential, lists the ones already out, and revokes any of them by name — so a build box, a contractor or a CI runner each gets its own, and taking one back does not disturb the others.
Headless, and honest about it
This release has no web dashboard: Crate is operated from Artisan commands and the credential API. It does not mirror public packages from packagist.org, and it has no per-package or per-vendor access control, no search and no download statistics. It is the self-hosted floor under a hosted registry, not a replacement for every feature of one.
How to run it yourself
You do not need Scalpels for any of this. Crate is MIT licensed — these are the steps, and you are welcome to do them by hand.
-
1
Fork the Crate repository into your own GitHub organization.
-
2
Deploy the fork to Laravel Cloud with its own compute, database, queue and object storage.
-
3
Register the repositories you want to serve, build the registry, and issue a credential to each application that pulls from it.
Or let Scalpels deploy Crate for you
Scalpels forks the repository into your GitHub, provisions exactly what the app needs on your own Laravel Cloud account, and deploys it. The app and the infrastructure are yours either way — the only question is who spends the afternoon.