CI usage
Runner-minute metering, monthly credits, queueing, and practical cost estimates.
Trylle charges CI by runner type and rounds runtime up to whole minutes. Linux AMD64 and ARM64 currently share the same price; macOS uses a higher rate.
Minute calculation
Each job is metered independently:
billed minutes = ceil(job runtime in seconds / 60)
cost = billed minutes × runner rateA matrix with four 20-second jobs bills four minutes, not one aggregate minute. Consolidating very short setup jobs can reduce rounding overhead when it also keeps the workflow clear.
Current rates
| Runner | Rate | $1 funds approximately |
|---|---|---|
| Linux ARM64 | $0.006/minute | 166 minutes |
| Linux AMD64 | $0.006/minute | 166 minutes |
| macOS ARM64 | $0.075/minute | 13 minutes |
Credits and wallet order
Personal plans and Team organizations receive monthly CI credit. Free organizations do not. CI uses the CI category credit first and then eligible unrestricted credit and wallet funds.
Queueing and admission
Current service admission protects shared capacity with global, architecture, triggering-user, and organization scopes. Jobs remain queued until every applicable scope has room. Queue time is not runner time and is not billed as execution.
The platform currently caps concurrent admitted jobs at 16 per triggering user and 32 per organization, with additional global and runner-pool limits. Treat these as service safeguards rather than plan entitlements; they may change as capacity changes.
Inspect usage
try ci usage -R OWNER/REPOSITORYUse repository and organization billing pages for wallet-level totals. The CLI repository usage view is best for investigating which CI activity is driving spend.