Pricing units
What each unit measures, how a charge is computed and rounded, and worked examples at the prices of rate card 2026-10-10.sandbox-1.
Units
| Price key | Unit | Price | In micro-euro |
|---|---|---|---|
capture.fetch | one published result | €0.12 per 1,000 | 120 per result |
capture.browser-fetch | one published result | €0.80 per 1,000 | 800 per result |
capture.render-fetch | one published result | €0.80 per 1,000 | 800 per result |
capture.capture | one published result | €1.00 per 1,000 | 1,000 per result |
session.browser | browser-hour, accrued per millisecond | €0.07 per hour | 70,000 per hour |
job.vcpu | vCPU-hour, accrued per millisecond | €0.04 per vCPU-hour | 40,000 per hour |
job.memory | GiB-hour, accrued per millisecond | €0.0064 per GiB-hour | 6,400 per hour |
These are the low end of the market-typical price band for each kind of service, as consulted on 9 October 2026.
Micro-euro
All amounts are whole micro-euro (µ€): €1 is 1,000,000 µ€. The API's credit errors and the panel's statement use them so that no amount is ever rounded twice.
How a charge is computed
- Per result. A published capture item is charged its script's price, once.
- Per time. A session or a job attempt is charged its hourly rate times its duration in milliseconds, rounded half up to the micro-euro once, at settlement:
(rate per hour × milliseconds + 1,800,000) ÷ 3,600,000, keeping the whole part. - A job attempt's duration runs from its container's start to its finish and stops at
runningDeadlineSeconds. It counts only when the attempt ended for a reason you caused (your code's exit, your own memory limit, your own deadline, your cancellation); an attempt that ended for a reason on our side counts zero milliseconds. See Analytical jobs. - Never above the reservation. A charge never exceeds the part of the reservation set aside for that item, session or attempt.
- A job's rate is the CPU you request in vCPU times €0.04 plus the memory you request in GiB times €0.0064, per hour.
500mis 0.5 vCPU;512Miis 0.5 GiB.
Worked examples
| Work | Computation | Charge |
|---|---|---|
| 10,000 rendered fetches, all published | 10,000 × 800 µ€ | €8.00 |
| 10,000 rendered fetches, 300 failed | 9,700 × 800 µ€ | €7.76 |
| One browser, ready for 30 minutes | 70,000 µ€ × 0.5 hour | €0.035 |
| One browser leased for 30 minutes, released after 12 minutes of use | 70,000 µ€ × 0.2 hour | €0.014; the other €0.021 of the reservation is released |
| A 2 vCPU / 4 GiB job running 10 minutes | (2 × 40,000 + 4 × 6,400) µ€ × ⅙ hour | €0.0176 |
The same job with a 10-minute deadline, stopped at it (RUNNING_DEADLINE_EXCEEDED) | (2 × 40,000 + 4 × 6,400) µ€ × ⅙ hour | €0.0176, however late the stop |
The same job evicted after 10 minutes (PLATFORM_EVICTED) | 0 ms | €0 |
The same job's reservation with a one-hour deadline, whatever its retries | 105,600 µ€ × 1 hour, one attempt | €0.1056 reserved |
Coming
Shown for planning; not offered yet: Actions runners (2 vCPU) at €0.0036 per minute, website route audits at €0.22 per 1,000 URLs, and managed applications priced per plan.
See Credit and billing.