HN Showcase
Back to browse
GitHub Repository

Private Composer Registry for PHP Teams

138 starsPHP

Pricore: an open-source private Composer registry (now in public beta)

by mbode·Mar 3, 2026·2 points·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidSolve My ProblemShip It

Laravel-native private Composer registry, but Satis and Nexus already solve self-hosted PHP packaging.

Strengths
  • •Fills a genuine frustration point: Satis requires manual rebuilds, Nexus is overkill; Pricore automates webhook-driven updates
  • •Built on Laravel with full Composer v2 API compliance including metadata-url for fast resolution
  • •Docker Quick Start makes deployment trivial: 60 seconds to production with zero infrastructure knowledge
Weaknesses
  • •PHP-only ecosystem limits addressable market compared to polyglot dependency management (npm, PyPI)
  • •Competing against Packagist's dominance and free SaaS tier; unclear differentiation for team growth scenarios
Target Audience

PHP development teams managing private packages; teams wanting self-hosted alternatives to SaaS registries

Similar To

Satis · Nexus Repository · Artifactory

Post Description

Pricore is a self-hosted private Composer registry for PHP teams. Built with Laravel, Apache 2.0 licensed, and now in public beta.

The problem it solves: managing private packages with VCS repositories in composer.json is slow, Satis requires manual rebuilds, and SaaS options get expensive. Pricore gives you a full Composer v2 registry on your own servers.

What it does:

- Mirrors GitHub/GitLab repos and serves them to Composer

- Webhook-driven updates, no manual rebuilds

- Token-based auth

- Web dashboard for packages, downloads, and activity

- Full Composer v2 metadata-url support

- Up and running in about 60 seconds with Docker.

GitHub: https://github.com/pricorephp/pricore

Blog post: https://pricore.dev/blog/introducing-pricore

Feedback and questions welcome.

Similar Projects