Why Pricore exists
Private PHP package management has been broken for too long. Pricore is the fix.
The problem
PHP's ecosystem has a gap. Public packages have Packagist, which is fast, reliable, and free. But the moment you need to host private packages, your options become limited.
Some solutions are static and require manual rebuilds. Others are SaaS-only, meaning your private code lives on someone else's servers. And some promising open-source projects have gone unmaintained.
I wanted something different: a self-hosted registry that's easy to set up, actively maintained, and built on a stack PHP developers already know.
My philosophy
I believe private package management should be:
- Self-hosted. Your packages live on your infrastructure. Period.
- Simple to run. If you can deploy a Laravel app, you can run Pricore.
- Open source. Apache 2.0 licensed. Fork it, extend it, contribute back.
- Familiar. Built on Laravel, the framework PHP developers already love.
The vision
Pricore isn't trying to replace Packagist. It's the missing piece for teams that need private packages without the compromises. I want every PHP team, from two-person agencies to hundred-developer enterprises, to have a registry they can trust.
Fast resolution, webhook-driven updates, a clean web UI, and the security of keeping everything on your own servers. That's what Pricore delivers.
About me
I'm Maarten Bode. I've been writing PHP and Laravel for over 10 years, and currently work as Lead Software Engineering at Zonneplan. After years of dealing with clunky private package setups across different teams and projects, I decided to build the tool I wished existed.