Pricing, entitlements, and usage
One Developer project is free with Schedules, Approvals, and Bulk. Upgrade any component to unlock Audit; there is no platform base fee or seat multiplier.
Developer — free forever
| Component | Monthly allowance | Limit behavior |
|---|---|---|
| Schedules | 1,000 runs | New runs wait for reset or upgrade |
| Approvals | 100 requests | New requests are rejected |
| Bulk | 10,000 items | New operations exceeding the remainder are rejected |
| Audit | Not available | Unlocks with any paid component |
Developer needs no card and applies to the first project on an account. Limits reset monthly in UTC. Reads, decisions, cancellations, and exports remain available after a limit is reached.
Component pricing
| Component | Monthly price | Included usage | Overage |
|---|---|---|---|
| Schedules | $49 | 50,000 runs | $1 per additional 5,000 runs |
| Approvals | $39 | 10,000 requests | $1 per additional 1,000 requests |
| Audit | $0 | Included with any paid component | No usage overage |
| Bulk | $69 | 1,000,000 items | $2 per additional 100,000 items |
Prices are per project, per month, in USD and replace the free allowance only for the upgraded component. Every active paid component also unlocks Audit.
What is metered
| Component | Usage event |
|---|---|
| Schedules | A run is metered when a durable schedule run is created for execution. |
| Approvals | A request is metered once when the approval resource is created. |
| Bulk | Each submitted item is metered once when the operation is accepted. |
| Audit | System and manual events are not separately billed. |
Retries do not create a second billable unit for the same run, request, or item. Idempotent retries with the same key return the existing resource and do not double count.
Subscription lifecycle
-
01
Start or upgrade
The first project starts on Developer. Checkout upgrades one component through Polar.
-
02
Track usage
The dashboard warns at 70%, 90%, and 100% and shows the reset date or paid overage rate.
-
03
Cancel or keep
Cancellation is scheduled for period end. When the paid period ends, Developer restores that component's free allowance.
-
04
Reach a free limit
New billable work is blocked with free_tier_limit_exceeded; existing data and non-billable actions remain available.
Free is native; paid is Polar-managed
Estimate a bill
Monthly total = active component subscriptions + rounded-up overage blocks
Example: Schedules + Approvals, 62,000 runs, 12,600 requests
Base: $49 + $39 = $88
Runs: ceil(12,000 / 5,000) × $1 = $3
Requests: ceil(2,600 / 1,000) × $1 = $3
Total: $94 USD
The dashboard is the source of truth for the current billing period and subscription dates. The public pricing page and this reference use the same component registry as dashboard billing.