Serverless Pricing

How is serverless compute priced, by the task or by the hour?

Serverless compute is billed in small slices of time, so a task costs its length times the rate for what it holds. The hard part is knowing what each vendor counts.

Compare per-task prices

rent.dev's price board prices longer tasks too, with the source of each vendor's rates linked.

What the meter counts

Most serverless platforms charge for vCPU time and memory time, often counted by the second. Some charge for the CPU you reserved, whether or not it worked; others charge only for the CPU your code really used. Memory is usually billed for as long as it is held.

Minimums and rounding

A meter may round each start up to a minimum, such as a whole minute. Short tasks feel this most: a burst of tiny tasks can cost more than one longer task doing the same work.

Idle time and keeping warm

A sandbox that is waiting still holds its memory, so it still costs money. Some platforms keep a container warm after a request so the next one starts faster, and bill for that wait. End a sandbox when its task is done.

Fees on top of the rate

Look for a fee per sandbox started, a monthly plan, storage that keeps billing after the task ends, and data sent out. Add them to the cost of the task, not to the hourly rate.

Pricing one task yourself

Write down the task's length, its vCPUs and memory, and how busy its CPU is. Multiply each rate by what that vendor counts for that time, then add the fees. Do this for each vendor and compare the totals, not the rates.

How rent.dev bills

rent.dev's own sandboxes bill by the second from one prepaid balance, on the memory they hold plus the CPU they use, so an idle task costs mostly its memory. A sandbox at another vendor is billed by that vendor, on your account there.

Questions

Is serverless priced per request or per second?

Functions are often priced per request plus the time each request runs. Sandboxes and containers are usually priced by the second for vCPU and memory. Read which one a vendor uses before you compare two of them.

Why do two vendors with the same rate charge different amounts?

Because they count different things. One bills the CPU you reserved, the other the CPU you used, and one may add a fee per start. Price a whole task to see the real gap.

What makes a serverless task cost more than expected?

Idle time with memory held, a minimum charge per start, cold starts on the meter, and storage or data fees that keep running after the task ends.

How does rent.dev price a sandbox?

By the second, from a prepaid balance, on the memory a sandbox holds plus the CPU it uses. The most it could cost is held at start, and what it did not use goes back to the balance when it stops.

Run a per-second sandbox

Agents can start at rent.dev/llms.txt, which lists every route.