// the find
orchidsoftware/platform
Orchid is a @laravel package that allows for rapid application development of back-office applications, admin/user panels, and dashboards.
Orchid is a Laravel package for building admin panels and back-office dashboards by writing PHP classes instead of Blade views - you define Screens and Layouts and it renders the CRUD UI for you. It's aimed at Laravel shops that need an internal admin panel fast and don't want to hand-roll one or pull in a heavier stack like Filament or Nova.
Screens are plain PHP classes with a query/layout/commandBar structure, so you can keep admin logic in version-controlled, testable code rather than scattered Blade templates. It uses Turbo/Hotwire for page transitions, giving SPA-like navigation without writing any JS. Access control (permissions tied to roles) and Eloquent-based filtering/sorting are built in rather than bolted on. CI is real - phpunit, coverage tracking, static analysis (psalm), and a code-style check all run on every push, and the project has 25+ translated language files, which signals actual production use beyond a toy project.
The Screen/Layout abstraction is the whole value prop but also the trap - once you outgrow its conventions (custom bulk actions, non-trivial nested forms) you're fighting the framework instead of writing HTML. It's Eloquent-only; there's no path if your data layer isn't straight Eloquent models. The README's live demo is commented out, so evaluating the actual admin UI before committing means reading docs or cloning the repo and wiring it up yourself. Coupling presentation logic into Screen classes makes them harder to unit test than a thin controller + Blade view - you end up testing Orchid's rendering indirectly rather than your business logic directly.