Limits, credits, and what an operation costs
Flowyn plan allowances in credits, how operations consume them, what happens when the allowance is used, and the main per-product limits.
Plan allowances
| Plan | Price | Credits a month | History |
|---|---|---|---|
| Starter | $0 | 10,000 | 3 days |
| Production | $9/month | 200,000 | 14 days |
| Capacity | $39/month | 1,000,000 | 30 days |
What an operation costs
Durable HTTP executions, event deliveries, scheduled executions, and monitor checks use the lightweight class. Automatic retries are included. Reading resources with GET does not consume credits.
| Class | Credits | Examples |
|---|---|---|
| Lightweight infrastructure | 1 | HTTP jobs, event delivery, schedules, monitors, heartbeats |
| Standard document | 5 | PDF merge, split, extract, compression |
| Parse or conversion | 10 | PDF and DOCX parse, HTML and DOCX to PDF |
| Intelligent | 20 | Intelligent PDF split |
What happens at the allowance
New billable creates return HTTP 402 with credit_limit_exceeded, the usage, the limit, and the reset time until the next reset or an upgrade. There is no automatic overage. Existing resources, attempts, and history remain readable.
Per-product limits
| Product | Limit |
|---|---|
| Requests | JSON bodies up to 1 MiB |
| Documents | 50 MB per file, 200 pages per operation, no OCR, up to 3 attempts |
| HTTP jobs and schedules | Timeout 100–30,000 ms, 1–20 attempts, body up to 65,536 characters |
| Events | Up to 8 delivery attempts, HTTPS endpoints, at most 50 endpoints per event |
| Monitors | Interval 30 s to 24 h, up to 20 assertions |
| Flags | Up to 20 attributes, 20 rules per flag, values up to 10 KB |
| Agents | 100 active agents per environment, 50 spans per telemetry batch, 30-day telemetry retention |
| Approvals | 10 pending per run, 500 pending per environment, expiry up to 7 days |
Next step
See Pricing or start with the Quickstart.