Scheduling + credit-based pricing
Time-based triggers, and the credit model that defines how OpFlow bills.
Scheduling
A schedule trigger backed by Supabase pg_cron — recurrence rules down to the minute. The schedule-tick and retry cron endpoints were hardened behind API-key auth.
Credit-based pricing
OpFlow meters operations as credits, priced for capability. The model, in a few lines:
- 1 credit = 1 operation (one node execution).
- Retries inside a run are free; disabled nodes don't count.
- Every paid tier starts at the same 10,000 operations / month baseline.
- You pay for capability; usage beyond the baseline is metered per 1k at your tier's rate.
AI nodes are the one weighted exception — bring your own key for 1 credit, or use managed models at a multiplier that covers the token cost.