I built a model-first approval workflow package for Laravel and Filament

Hi everyone,

I’m building DBFlow, a model-first approval workflow engine for Laravel and Filament.

It helps developers add approval workflows to Eloquent models such as refunds, purchase requests, expense claims, orders, and other business records.

The Core package is open source, and the Filament integration has been approved and listed on the Filament Plugins Directory.

The Filament plugin provides:

• Workflow tasks
• Approval actions
• Workflow instance views
• Audit timelines
• Filament panel integration
• Code-first workflow definitions

DBFlow is not trying to replace BPMN or become a full low-code BPM platform. The goal is to provide the workflow layer Laravel apps usually need inside business systems.

I’d love to hear feedback from Laravel / Filament developers:

• Does the model-first approach make sense?
• What approval workflow features do you usually need in Laravel projects?
• Would you prefer code-defined workflows, UI-defined workflows, or both?

You can find it by searching for DBFlow in the Filament Plugins Directory or on GitHub under dbflow-labs.