View as Markdown

Billing

Forkline bills for runner usage time, measured per minute.

How Usage Is Counted

  • Billing starts when a runner begins initializing
  • Billing ends when the runner stops
  • The minimum charge is 1 minute
  • Larger runner sizes apply a higher usage multiplier

Info: Billing is based on compute time, not AI token usage. You can still bring your own model keys or use Forkline’s free OpenCode Zen models.

Billing page

Usage Multipliers

Usage multipliers
Basic

Baseline rate

Good for short edits and lightweight automation where you want the lowest per-minute burn.

1 minute = 1 minute billed
Advanced

Balanced throughput

Most teams should expect Advanced to be the default tradeoff between speed and cost.

1 minute = 2 minutes billed
Pro

Fastest but most expensive

Reserve Pro for workloads where runtime savings justify the higher multiplier.

1 minute = 4 minutes billed
Billing scales with runner size, so the right choice depends on whether faster completion offsets a higher minute rate.

Usage Tracking

View your usage in Settings -> Billing:

  • Total hours this month
  • Hours per repository
  • Current plan limits

Minimum Balance

You need at least 5 minutes of balance to start a runner.

When Balance Reaches Zero

  1. All your runners stop immediately
  2. Tasks that were running are suspended, and new webhook-triggered tasks are not started while your balance is zero
  3. You receive an email notification
  4. Suspended tasks resume automatically once you have at least 5 minutes of balance again, for example after a top-up, a new or upgraded plan, or your plan’s daily credit refresh
  5. A task that stays suspended for more than 7 days is cancelled
  6. Tasks that were not started while your balance was zero are not guaranteed to restart, so trigger them again, for example with a new comment or push

Separately, when you already have the maximum number of pending tasks (50 by default), new webhook tasks are not created. Nothing is suspended for that reason.

Next Steps