DATA FLOWS
Fair-use policy
Better Analyst prices Data Flows by understandable product limits—saved flows, destinations, and refresh frequency. Row allowances are a transparent infrastructure safeguard, not a surprise overage charge.
| Plan | Rolling 30-day allowance | Technical per-run ceiling |
|---|---|---|
| Free | 10 successful test deliveries | 5,000 rows per test |
| Starter | 10 million processed source rows | 500,000 rows per run |
| Max | 100 million processed source rows | 2 million rows per run |
| Enterprise | 500 million processed source rows | 4 million rows per run |
| Custom | Contracted capacity | Contracted capacity |
How processed rows are calculated
We count rows returned by source systems before filters, joins, or other transformations, once per successful logical run. If the final output has more rows, the larger number controls the per-run ceiling. Automatic retries keep the same logical-run identity and never count twice. A successful result with zero rows counts as a Free test.
Reservations and rolling usage
Before a run is queued, Better Analyst reserves an estimate based on the flow’s previous successful run or its bound source artifact. When neither estimate exists, it reserves the plan’s per-run maximum. Success replaces the estimate with actual source and output rows; terminal failure or cancellation releases it. Usage continuously falls out of the window 30 days after it was recorded—there is no fixed calendar reset day.
Warnings and pauses
Workspace owners see warnings at 70% and 90%. At 100%, new manual runs are rejected with the next relief time. Scheduled occurrences are skipped while their next scheduled time continues to advance, then resume automatically when rolling usage falls below the limit. We do not bill automatic overages.
Atomic delivery and lower limits
The effective limit is always the most restrictive of the Better Analyst plan, connector, source API, and destination. If a run exceeds its ceiling, it fails before the destination write. We never truncate a result or partially replace a destination to fit a quota. Provider latency, API quotas, spreadsheet cell limits, and database constraints can impose lower limits.
Questions about unusually large workloads? Contact Better Analyst.