DBFlow Pricing

Reference pricing doc. Full page: /pricing.

DBFlow Pro is available for purchase. Start with free Core and Filament before adding Pro.

DBFlow Core and Filament are open-source packages on Packagist. DBFlow Pro is a commercial annual license. Purchases use secure checkout through our payment provider.

Plans

DBFlow Core — Free

Open-source workflow runtime for Laravel applications (dbflowlabs/core). Available on Packagist — use ^1.0 in production.

  • Full workflow runtime (approvals, tasks, reject strategies)
  • active_key concurrency guard
  • Append-only audit logs
  • Unlimited local and staging environments
  • Community support

Best for: Evaluating DBFlow before purchasing Pro.


DBFlow Filament — Free

Standard Filament integration for DBFlow Core (dbflowlabs/filament). Available on Packagist.

  • My Tasks and workflow instances
  • Timelines and resource actions
  • Filament-native admin surfaces

Best for: Teams that want Filament UI on top of Core without Pro.


DBFlow Pro — $99 for the first year

Commercial visual workflow builder (dbflowlabs/filament-pro). Stable 1.0 — annual license with private Composer access.

  • Visual workflow builder
  • Visual workflow definition tooling
  • Private Composer package access for active license holders
  • License key for production deployments
  • Access to Pro updates released during the active license period
  • Email support for license, Composer access, and Pro installation
  • One production domain registration during the active license period

DBFlow Pro is available at $99 for the first year. The standard price is $129/year after the first year. Use Get DBFlow Pro — $99 on the Pricing page. Private Composer access, Pro updates released during the active license period, scoped email support, and one production domain registration are provided during the active license period.

Best for: Laravel and Filament teams that need the LogicFlow visual builder in addition to Core and Filament.

Launch offer

DBFlow Pro is available for $99 for the first year. See the Pricing page for current launch offer terms.

The standard price is $129 per year. After the first year, the license renews at that price.

You may continue using the last DBFlow Pro version installed during your active license period if you choose not to renew. Private Composer access, new downloads, newly released updates, support, and license management require an active license.

Entitlement Comparison

Capability Core Filament Pro
Workflow runtime (dbflowlabs/core)
Filament Standard UI (dbflowlabs/filament)
Visual workflow builder
Private Composer package access during active license period
Commercial license key
Access to Pro updates released during active license period
Email support for license, Composer access, and Pro installation
One production domain registration during active license period

Before You Buy Pro

Start on Core. Install dbflowlabs/core and dbflowlabs/filament, run workflows locally, and validate approvals on staging. The full evaluation stack does not require a Pro license.

Step Action
1. Try Live Demo demo.dbflow.dev
2. Install Core Installation
3. Buy Pro $99 for the first year on Pricing when you need the visual builder

Billing

DBFlow Pro is an annual license. Payments are handled securely by our payment provider.

After payment is confirmed:

  1. Receive your DBFLOW-PRO-* license key by email after payment confirmation.
  2. Set DBFLOW_LICENSE_KEY in your production .env.
  3. Private Composer package access will be provided to active Pro customers.
  4. Register one production domain in the Customer Portal.

The checkout success page is not proof of license delivery — wait for your license key email confirmation.

What happens when a Pro license expires?

DBFlow Pro uses a perpetual-use-with-renewal-benefits model. You may continue using the last DBFlow Pro version installed during your active license period, including in existing production deployments.

After the license expires:

  • Existing applications and previously registered production domains will continue to work.
  • Access to the private Composer repository and new package downloads will be suspended.
  • Newly released Pro updates and email support will no longer be available.
  • New production domains cannot be added, and existing domain registrations cannot be changed without renewal.

Renewing your license restores private Composer access, newly released Pro updates, support, and production domain registration changes. License expiration will not disable or interrupt an existing deployed application.

Benefit Active license Expired license
Use the last installed Pro version Yes Yes
Existing production deployments Yes Yes
Existing registered domains Yes Yes
Private Composer access Yes No
New package downloads Yes No
Access to Pro updates released during active license period Yes No
Email support for license, Composer access, and Pro installation Yes No
Add or change production domain registration Yes No
Renew the license Yes Yes

FAQ

Does Core require a license key? Core and Filament Standard do not require a Pro license key in your application.

Is the launch price permanent? No. The launch offer is $99 for the first year. After the first year, the license renews at the standard price of $129 per year. If you choose not to renew, you may continue using the last DBFlow Pro version installed during your active license period.

What counts as a production domain? Any public hostname that is not localhost, 127.0.0.1, or a *.test / *.local development TLD.

What happens when my DBFlow Pro license expires? You may continue using the last DBFlow Pro version installed during your active license period. Existing applications and previously registered production domains will continue to work, but private Composer access, new package downloads, newly released Pro updates, email support, and production domain changes require renewal.

How do I purchase Pro? Visit /pricing and use Get DBFlow Pro — $99. DBFlow Pro is available at $99 for the first year, then $129/year after the first year.

Something wrong? Open an issue on GitHub