Start with the essential. Add only what you need.
Splinter is a lightweight PHP micro-framework ecosystem built around a single principle: a service should contain only what it actually uses. No bloat, no forced opinions, no magic.
| Package | Description | Version |
|---|---|---|
| splinter/framework | Core: DI, routing, Eloquent ORM, console, Redis queues |  |
| splinter/skeleton | Application skeleton for composer create-project |
 |
| splinter/access | Access rule checking module |  |
| splinter/view | Twig view layer |  |
| splinter/auth | Authentication module (coming soon) | — |
composer create-project splinter/skeleton my-service
cd my-service
php splinter migrate
php -S localhost:8000 -t public/Modules are optional. Install only what the service actually needs.
Twig view layer:
composer require splinter/view
# add TwigServiceProvider to config/app.php → providers
php splinter vendor:publishAccess rule checking:
composer require splinter/access
# add AccessServiceProvider to config/app.php → providersModern microservice architectures don't need a full-stack framework on every service. Splinter gives you a minimal, composable core — each service pulls in only the modules it actually uses.
- Core is truly minimal — DI, routing, Eloquent ORM, Redis queues, console. Nothing else.
- Modules are optional — view layer, access rules, auth — each is a separate package, installed only where needed.
- No magic — configuration is plain PHP arrays, auto-loaded by convention from
config/. - One structure — every Splinter service looks the same: same layout, same entry points, same CLI.
Each module integrates through the same two-step pattern:
- Add a
ServiceProvidertoconfig/app.php→providers. - Run
php splinter vendor:publishif the module ships config files or views.
The core resolves everything else automatically — exception handlers, container bindings, published assets.
- PHP ^8.2
- MySQL / MariaDB
- Redis
MIT