Preview
Sign inSign up

Pricing

Pay for CPU, not for waiting.

Every plan starts with 600 free CPU-seconds a month. After that, you pay only for the CPU time your programs use.

Free

For trying the API and small projects.

$0forever

  • 600 CPU-seconds a month
  • Timeouts up to 5 s
  • 64 MB memory, 60M steps
  • 60 requests a minute
  • 4 evaluations in flight

Pay as you go

Price coming soon

For production traffic. Same 600 free CPU-seconds, then billed by use.

Meteredper CPU-second

  • 600 CPU-seconds included each month
  • Then billed per CPU-millisecond
  • Timeouts up to 10 s
  • 128 MB memory, 120M steps
  • 300 requests a minute
  • 8 evaluations in flight
  • Hard cap at 10 CPU-hours a month

01Metering

Rounded up to the millisecond.

Each response reports stats.cpu_ms. That's the number you're billed on, rounded up, with a 1 ms minimum.

charged_ms = max(1, ceil(cpu_ms))

cpu_mscharged
0.041 ms
1.001 ms
12.313 ms
840.7841 ms

02Limits

Every limit, per plan.

The playground in the app and the try-it box on this site run with their own, tighter limits.

LimitFreePay as you goPlaygroundTry-it demo
Wall-clock timeout1 s default, 5 s max1 s default, 10 s max1 s500 ms
Steps60M120M2M1M
Memory64 MB128 MB32 MB16 MB
Integer size100k bits100k bits20k bits10k bits
Compound expressionsNo capNo cap20050
Source size64 KB64 KB16 KB4 KB
Output (stdout)64 KB64 KB16 KB4 KB
Printed value, per result16 KB16 KB8 KB2 KB
Rate limit60 / min per key300 / min per key20 runs / min10 / min, 100 / day per IP
Concurrent requests4 per account8 per account––
Monthly CPU600 s600 s included, 10 h capNot meteredNot metered

03Questions

Billing, answered.

What counts as CPU time?
The CPU time of the process that runs your program. Time spent waiting for a free slot, or anything else that isn't your program running, isn't counted.
Do failed programs cost anything?
They're charged the CPU time they used before they failed, the same as a program that finished. Requests turned away before running, like a 401 or a 429, cost nothing.
What happens when the free allowance runs out?
On the free plan, API calls get 429 cpu_quota_exceeded until the start of the next UTC month. On pay as you go, usage keeps going and is billed, up to 10 CPU-hours a month.
Is the playground metered?
No. Runs in the app's playground and the try-it box on this site have their own, tighter limits and aren't billed.
When is pay as you go billed?
Usage is reported to Stripe daily and invoiced monthly, on a cycle that starts on the 1st, so invoices line up with the monthly allowance.
esc