Open source · Laravel · MIT

The pieces every Laravel app ends up rebuilding.

Authorization, upstream updates, activity history, release notes, command tracking, extracted from the apps we run in production and published as plain Composer packages.

# 1. Setup (one-time)php artisan laravelplus:setup# 2. Check for updatesphp artisan laravelplus:check# 3. Apply updates (creates PR by default)php artisan laravelplus:update
Packages13
Installs5k+
Public repos25
Laravel12
A.After.siUsed across its production apps
laravelplus/laravel-updaterlaravelplus/fortresslaravelplus/version-platform-managerlaravelplus/user-historylaravelplus/commanderlaravelplus/feature-requestslaravelplus/installerlaravelplus/content-securitylaravelplus/attrifylaravelplus/etl-manifestolaravelplus/toonlaravelplus/repository-patternlaravelplus/automationslaravelplus/laravel-updaterlaravelplus/fortresslaravelplus/version-platform-managerlaravelplus/user-historylaravelplus/commanderlaravelplus/feature-requestslaravelplus/installerlaravelplus/content-securitylaravelplus/attrifylaravelplus/etl-manifestolaravelplus/toonlaravelplus/repository-patternlaravelplus/automations

Powerful packages, one job each.

Each one installs with Composer and follows Laravel's own conventions: service providers, config files, migrations, artisan commands.

The framework is enough. Almost.

Every app we shipped needed the same missing pieces.

Laravel covers routing, queues, auth and the database. What it leaves to you is the plumbing between the framework and the product: authorization rules, audit trails, release notes, keeping in step with a starter kit.

We wrote that plumbing once per app, then stopped. LaravelPlus is the version we keep: extracted, used in production, published.

More in the box.

Newer and more specialised packages. Smaller install counts, same rules: one job, Laravel-native, readable source.

How we build them.

01

Extracted, not invented

A package earns its place by being needed in a real app first. Nothing here started as a side project looking for a problem.

02

Laravel-native

No parallel framework, no new mental model. Service providers, config, migrations and artisan, the way Laravel already works.

03

Small enough to read

If you can't read the source in an afternoon, it is doing too much. Fork it, extend it, or delete it.

Start with composer require.

Everything installs on its own; nothing forces the rest along.

$ composer require laravelplus/fortress