Skip to content

Billing

Billing is per-organization and managed from the Billing tab in the Avrea console. Admins and Billing admins can access billing. See Organizations for role details.

  1. Go to Billing > Settings.
  2. Click Add Payment Method.
  3. Enter your card details and click Save.

You can add multiple payment methods. The first card added becomes the default.

Organizations with no payment method on file run with lower limits: 64 vCPUs at once, 2 hours per job and 256 queued jobs. Sandboxes run for at most 2 hours from creation, and static IPs cannot be reserved. When their free monthly minutes run out, new jobs are cancelled, jobs already queued wait until you add a payment method or the minutes reset, and no sandbox can be created, started or forked. Adding a payment method raises the limits and lets new jobs and sandboxes run again.

Free minutes apply to one organization per admin. An organization whose admin already has them on another organization needs a payment method to run its first job.

Under Settings you can also configure:

  • Billing email: comma-separated list of addresses that receive invoices and payment notifications.
  • Tax ID: your VAT or tax identification number (included on invoices).
  • Billing address: street, city, postal code, and country.

Click Save Settings after making changes.

The Invoices tab shows your current-period usage and past invoices. Usage is metered per second of job run time, at per-minute rates. See Runners for available runner sizes and avrea.com/pricing for per-minute rates.

To see which runners, workflows and jobs your CI run time went to, open Settings > Usage > Runner. That page shows run time and is not a billing total; amounts are on the Billing page. See Runner usage.

These features are billed in addition to runner minutes:

FeaturePrice
Static IP$100 per reserved IP per month, metered per started UTC day ($3.33 per day)
Persistent disk$0.50 per provisioned GB per month, prorated

The Pay as you go and Team plans include free minutes every month. See avrea.com/pricing for the amounts. An organization does not get the allowance if one of its admins also administers another organization that already receives it.

Free minutes are measured on a 2 vCPU Linux x86 runner. Every other runner draws them down in proportion to its per-minute rate: a runner that costs twice as much per minute uses them twice as fast, and one that costs half as much uses them half as fast.

minutes covered = free minutes x (2 vCPU Linux x86 rate / runner rate)

For the 3,000 free minutes on Pay as you go, that gives:

RunnerMinutes covered
Linux x86, 1 vCPU6,000
Linux x86, 2 vCPU3,000
Linux x86, 4 vCPU, 8 GB2,000
Linux x86, 4 vCPU, 16 GB1,500
Linux x86, 8 vCPU, 16 GB1,000
Linux x86, 8 vCPU, 32 GB750
Linux ARM, 4 vCPU, 8 GB≈667
Linux ARM, 4 vCPU, 16 GB500
Linux ARM, 8 vCPU, 16 GB≈333

The allowance is a monthly credit on your invoice. Other metered usage, such as static IPs and persistent disks, draws on the same credit.

You can spread free minutes across any mix of runner types and sizes. They are used before paid usage, they reset every month, and unused minutes do not carry over. The Billing page shows how many remain in the current period, counted as 2 vCPU Linux x86 minutes.