Performance
Core operations are optimized with batching, proper indexing, and declarative SQL. However, large-scale workloads may reveal additional optimization opportunities. Start with your expected workload and scale as needed.
Project Status
Public Beta
Section titled “Public Beta”pgflow is in public beta and being used in production by early adopters. Core functionality is stable and reliable.
Known Limitations & Active Work
Section titled “Known Limitations & Active Work”Fair Processing
Fair processing across flows is not currently implemented. A flow with many tasks (especially map steps processing large arrays) can fill the queue ahead of other flows. This is more noticeable with the introduction of map steps in 0.7.0. For multi-tenant or multi-flow scenarios where fairness is important, join Discord to discuss approaches and workarounds.
Permissions
pgflow ships with zero built-in permissions or access controls. Database permissions must be manually configured when using the TypeScript Client or Supabase RPC from client applications. In a future release, pgflow will support custom start functions for the TypeScript Client, enabling authorization logic at the database level and supporting multi-tenant scenarios.
Breaking Changes
Section titled “Breaking Changes”During beta, breaking changes may be introduced for critical fixes or significant improvements. All changes are documented in release notes with migration guides. See updating pgflow for the update process.
Production Recommendations
Section titled “Production Recommendations”Getting Support
Section titled “Getting Support” GitHub Issues Report bugs or request features
FAQ Common questions about Edge Worker functionality, usage, and billing
Join the Community
Connect on Discord
Have questions or need help? pgflow is just getting started - join us on Discord to ask questions, share feedback, or discuss partnership opportunities.