Package Status

DBFlow is currently in public alpha. The Core and Filament Standard packages are intended for evaluation, demos, and early integration feedback. Pro Builder is not generally available yet.

This page describes the maturity of each DBFlow package. Pin exact tags in production until stable releases are announced.

Package maturity

Package Status License Purpose
dbflowlabs/core Alpha · Open Source MIT Workflow runtime — instances, tasks, approvals, audit logs
dbflowlabs/filament Alpha · Free MIT Filament UI — My Tasks, timelines, resource actions
dbflowlabs/filament-pro Private Preview · Commercial Commercial Visual workflow builder (not GA)
Enterprise / White Label Future Custom Not offered today

Core (dbflowlabs/core)

  • Alpha / Open Source — runtime engine on Packagist
  • Suitable for local evaluation, staging pilots, and integration feedback
  • Breaking changes may occur between alpha tags — see Release Policy
  • Does not require Filament or Pro

Filament Standard (dbflowlabs/filament)

  • Alpha / Free — MIT-licensed admin UI layer
  • Depends on Core and Filament 5.6+
  • Optional — Core runs workflows without any Filament pages

Pro Builder (dbflowlabs/filament-pro)

  • Private Preview / Commercial — visual definition authoring
  • Not generally available; no live checkout today
  • Core still executes workflows — Pro helps design definitions
  • See Pro Preview Limitations

Enterprise / White Label

  • Future — custom licensing for large deployments or source buyouts
  • Contact [email protected] for early conversations only

Compatibility

Requirements below match the published Installation docs and current package constraints.

Package PHP Laravel Filament
dbflowlabs/core 8.3+ 13.x N/A
dbflowlabs/filament 8.3+ 13.x 5.6+
dbflowlabs/filament-pro 8.3+ 13.x 5.6+

Database (Core): MySQL 8.0+, PostgreSQL 16+, or SQLite for development.

Composer: 2.x

Pro Builder targets the same Laravel and Filament baseline as Core and Filament Standard. When Pro leaves preview, compatibility will be documented per tagged release.

Safe to evaluate?

Yes — for side projects, staging environments, and demos:

  • Core and Filament Standard install via Composer without a Pro license
  • Local and *.test / *.local hosts do not consume production entitlement during evaluation
  • Workflow state lives in dedicated dbflow_workflow_* tables — your domain models stay separate

DBFlow is not positioned as production-hardened until stable releases are published. Treat alpha integrations as reversible pilots.

Related

Something wrong? Open an issue on GitHub