psyao / kami

v0.2.1 2026-10-30 17:04 UTC

Requires

• php: ^8.5
• filament/filament: ^5.10
• laravel/framework: ^13.32
• spatie/laravel-package-tools: ^1.93

Requires (Dev)

• driftingly/rector-laravel: ^2.7
• evilmartians/lefthook: ^2.2
• larastan/larastan: ^3.13
• laravel/pint: ^1.32
• orchestra/testbench: ^11.3
• pestphp/pest: ^5.3
• pestphp/pest-plugin-browser: ^5.1
• pestphp/pest-plugin-laravel: ^5.0
• phpstan/phpstan-deprecation-rules: ^2.0
• rector/rector: ^2.8.3

MIT

• Steve Aguet

• cms
• laravel
• filament
• filament-plugin

Published on Packagist.org on 2026-10-30 17:04 UTC

README

A Laravel and Filament CMS for developers, at home on shared hosting.

Psyao Kami, Kami for short, is a Composer package. Its admin is a plugin on your own Filament panel, and a site's content model is PHP code: Kami adds what a site needs without taking over the application. Everything runs on shared hosting with no cron, queue worker, Redis or Node on the server, and nothing essential depends on a remote service.

Kami is in early development: so far it covers installation, the environment check and the admin's wiring.

Requirements

• PHP 8.5 or later, with the extensions listed in Installation
• Laravel 13.32 or later and Filament 5.10.2 or later
• SQLite, MySQL 8.4, MariaDB 10.11 or PostgreSQL 15 or later

Install

A new site starts from the starter kit:

laravel new site --using=psyao/kami-starter
cd site
php artisan kami:install
php artisan serve

kami:install asks for the first administrator, who signs in at /admin. To add Kami to an application you already have, see Existing application.

Documentation

• Installation: requirements, creating a site, kami:doctor and kami:install
• Existing application: adding Kami to a Laravel application and its panel
• Content types: declaring a type and its Fields, writing and reading Entries
• Multilingual: Locales, Translations, Shared Fields and Fallback with lang
• Publishing: Draft, Scheduled and Published, validation, slugs, Content events, and why SaveEntry does not authorise
• Users and roles: KamiUser, Roles in config/kami.php, Permissions and strict authorization
• Routing and rendering: Kami::routes(), Paths and a type's render()
• Security: the front and admin Content Security Policies, extending them, and the options that weaken them
• Hosting: what Kami needs from shared hosting and from a server
• Deployment: the first deploy and every later one, on Infomaniak shared hosting or a server
• Decision records: why Kami is built the way it is

Contributing to Kami itself: Development.

Licence

MIT, see LICENSE.md.