Open source · case study

TomatoPHP — a Filament plugin ecosystem for Laravel

Ready-made Laravel and FilamentPHP modules — CMS, CRM, commerce, users, translations, media — each installable on its own.

Creator and maintainer
  • Laravel
  • FilamentPHP
  • PHP
  • MIT

The problem

Every Laravel admin project rebuilds the same furniture: users and roles, a CMS, a media library, translations, a CRM, billing. Teams either copy it between projects or buy a closed product they cannot extend.

What I did

Each feature is its own composer package that registers itself with Filament when installed, so a project takes only the modules it needs, and a module can be replaced without touching the rest. Everything is MIT-licensed and maintained in the open.

Technical detail

Install what you need

One composer require per module, and it registers itself — no fork, no scaffolding to maintain by hand.

A marketplace, generated

The plugin listings on the site are generated from the GitHub organisation rather than typed, so what is published and what exists cannot drift apart.

Bilingual from the start

English and Arabic across the modules and the documentation — the ecosystem is used by Arabic-speaking teams, not translated as an afterthought.

Where it stands

The TomatoPHP organisation carries 2,434 GitHub stars across its repositories and 178 packages in the generated marketplace, all MIT-licensed. Counts come from the GitHub API and the generated listings, checked on 2026-09-16.

All projects