Case study
Private Laravel package system for an agency
Six to seven private Laravel packages — blog, comments, invoicing, CRM — on a private Composer registry, so a Belgian contractor could assemble applications for UK customers by installing only the modules each one needs.
At a glance
- Client
- Software contractor, Belgium, serving UK customers
- Delivered
- 6–7 private Laravel packages
- Distribution
- Private Composer registry
What the client needed
He sold similar applications to many customers and was rebuilding the same features each time. He wanted to install only what a given customer paid for.
What we built
A set of installable Laravel packages (blog, comment management, invoicing, a small CRM and others), each with its own migrations, config, views and tests, published to a private Composer registry.
A new client app starts from a clean Laravel install and requires only the modules it needs through Composer. Updates ship to every installation through the registry.
What it shows
Laravel package architecture done properly: isolation, versioning and a private registry, so an agency can productise its own features.
Related services and industries
Services
Industries
Have a similar project?
Tell us what you need to build or change. We reply within one business day (IST).