Skip to content
where do irun this.

A guide to choosing where to run

Serverless compute

Compare serverless compute destinations by execution limits, triggers, runtime constraints and state handling.

What to check before choosing

Start with what triggers execution and how long it must run. HTTP requests, queues and scheduled tasks have different timeout, concurrency and retry requirements. Verify those limits in the product documentation instead of treating serverless as one execution model.

Check runtime and resource constraints: supported languages, native dependencies, CPU and memory allocation, cold starts and outbound network access. Work that needs an always-on process or durable local files may fit an application host or persistent environment better.

This list includes products classified as serverless compute. It is not a list of every platform with a function feature. Use each profile to inspect evidence, state storage options and billing units; request, duration and resource charges are not interchangeable.

How we assess products · Explore this type in the atlas

Products in this category

where do i run this.

An independent spec sheet for places to run code, and the code your agents write. Facts come from each product's public pages; every capability is a count, never a grade.

Verify

Pages change; so do prices. Verify on the vendor's site before you commit; every product page shows when it was read.

Where Do I Run This © 2026counts, not grades · public pages only