Skip to content

# Comparing pgflow to Other Systems

This section compares pgflow to other workflow orchestration systems, helping you understand the architectural differences, trade-offs, and when to choose each approach.

## Comparison Guides

Section titled “Comparison Guides”
pgflow vs DBOS How pgflow compares to DBOS for Postgres-based workflow orchestration
pgflow vs Trigger.dev How pgflow compares to Trigger.dev for workflow orchestration
pgflow vs Inngest How pgflow compares to Inngest for workflow orchestration

## Key Differences

Section titled “Key Differences”

When comparing pgflow to other workflow systems, these are the most important architectural differences:

1. Database-Centric Orchestration - pgflow puts PostgreSQL at the center, using it not just for storage but for orchestration logic
2. Supabase Integration - Built specifically for the Supabase ecosystem with zero additional infrastructure
3. Explicit Data Dependencies - Flow steps connect through explicit data dependencies rather than procedural control flow
4. PostgreSQL State Storage - All workflow state remains directly queryable in your Supabase database

These guides help you decide which tool is best for your specific use case based on your requirements, preferences, and existing infrastructure.