Skip to content

hbmartin/comparison-hosts-serverless-cloud-function-faas-for-python

BranchesTags

Repository files navigation

Comparing hosts / providers for serverless cloud functions (FaaS) for Python

discord twitter

No Python support: Netlify Functions (JavaScript/TypeScript, plus Go and Rust via custom runtimes), Supabase Edge Functions (Deno/TypeScript), and Deno Deploy (JavaScript/TypeScript). IBM Cloud Functions (OpenWhisk) was shut down in October 2024 — IBM Code Engine is its replacement. AWS App Runner is excluded because idle services still incur provisioned-memory charges (no scale to zero cost) and it is now in maintenance mode — closed to new customers since April 30, 2026. StackPath EdgeEngine no longer exists.

This document provides a comparison between hosted, serverless (no cost or management to spin down to zero) providers of cloud function hosts with Python runtimes. Note the distinction between edge providers (execution at PoP) and non-edge (typically predetermined DS region), and between true FaaS (per-request billing), serverless containers (per-use vCPU-s/GiB-s billing: Google Cloud Run, Azure Container Apps), and scale-to-zero container/VM platforms (per-second or per-minute instance billing: Fly.io, Koyeb, Railway, Render).

Data last verified July 12, 2026. Sources for table data are cited as footnotes (rendered at the bottom of this page); broader reading is collected in References. Pricing is USD (except Scaleway in EUR and Huawei's China list prices in CNY) and subject to change — always confirm against the linked official pages. ❔ = could not be verified against official sources.

Please join our discussions or fix/update information by editing this doc!

See also the "one-click" container image deployment comparison (not Python specific) and the Serverless SQL DB Comparison

Recent Platform Changes (2024–2026)

Watchlist and reviewed-but-excluded

Promising platforms that are not (yet) full rows below:

Reviewed and excluded: Heroku (Eco dynos sleep but are a flat $5/mo subscription, and the new Fir generation has no Eco tier), Northflank (per-second billing but no wake-on-request scale to zero for web services), Zeabur (stopped accepting new usage-billed shared-cluster services Apr 1, 2026 — now fixed-price dedicated servers), PythonAnywhere (always-on hosting, not FaaS), Genezio (pivoted away from FaaS during 2025), and Deta Space (shut down Oct 2024).

DevEx

Python Version Status API Framework Requirements Local Testing Docs Hello World
Alibaba Cloud Function Compute 3.121 GA Plain object / WSGI Vend in zip or Serverless Devs ✅ 🎉 Link
Appwrite Functions 3.14 (Cloud: 3.9 / 3.12 / 3.14)2 GA (Cloud GA Aug 2025)2 def main(context) handler ✅ (requirements.txt build command)3 ✅ (appwrite run functions, Docker + hot reload) 👍 Link
AWS Lambda & Lambda@Edge 3.144 GA Plain object Vend in zip (SAM build automates) ✅ (SAM local) 🎉 Link
Azure Container Apps (containers) Any GA Any ✅ ✅ (any container runs locally) 👍 Link
Azure Functions 3.145 GA azure-functions v2 decorators, ASGI/WSGI6 ✅ ✅ (Core Tools) 🎉 Link
Cloudflare Workers (WASM) 3.13 (Pyodide 0.28)7 Beta8 fastapi and others pyproject.toml + pywrangler ✅ 🎉 Link
DigitalOcean Functions 3.139 GA Plain object requirements.txt + build.sh9 ☁️ (doctl serverless — dev runs in a cloud namespace)10 👍 Link
Fermyon (WASM) 3.10+11 Experimental SDK, Cloud in open beta12 Spin (componentize-py) ✅ ✅ (spin build --up) 🎉 Link
Fly.io (microVM) Any GA Any ✅ ✅ 👍 Link
Google Cloud Run 3.1413 GA functions-framework, Flask, FastAPI, or any container ✅ (requirements.txt or pyproject.toml)14 ✅ 🎉 Link
Huawei Cloud FunctionGraph 3.1215 GA Plain object / HTTP functions run web servers (WSGI/ASGI) Vend in zip or dependency packages ✅ (VS Code / PyCharm plugins) 👍 Link
IBM Code Engine 3.13 (3.11 deprecated)16 GA Plain object ✅ Manual (no emulator) 👍 Link
Koyeb (containers) Any GA Any ✅ ✅ 👍 Link
Modal 3.10–3.14 (per-image)17 GA @app.function() decorators, ASGI/WSGI In-code image definition (incl. pip_install_from_requirements) ☁️ (modal serve runs in cloud with live-reload) 🎉 Link
Oracle (OCI) Functions 3.1218 GA FDK ✅ (built into container) ✅ (Fn CLI) Min. Link
Railway (containers) Any (Railpack default 3.13)19 GA Any (Flask / FastAPI / Django auto-detected)19 ✅ (requirements.txt, pyproject, Pipfile)19 ✅ (railway run) 👍 Link
Render 3.1420 GA Any WSGI/ASGI ✅ ✅ 👍 Link
Scaleway Serverless Functions 3.1421 GA Handler function Vend in zip ✅ (local framework) 👍 Link
Tencent Cloud Functions 3.1022 GA (maintenance mode, see note) Plain object / Web functions Vend in zip ❔ Min. Link
Vercel Functions 3.14 (3.12 default)23 Beta23 HTTP handler or WSGI / ASGI (FastAPI/Flask/Django presets) ✅ ✅ (vercel dev) 👍 Link
Yandex Cloud Functions 3.14 / 3.1224 GA Plain object (async def supported; no WSGI/ASGI)24 ✅ (requirements.txt auto-installed)25 Manual (console test tab, no emulator) 👍 Link

Tencent note: no official discontinuation exists, but the Python runtime is stale (3.10, CentOS 7), the free tier is trial-only, API Gateway triggers were decommissioned in June 2025, and Tencent's serverless investment has shifted to CloudBase.

Region notes: Huawei Cloud has no US regions (China plus Asia-Pacific/EU/Middle East/Africa/LatAm). Yandex Cloud regions are in Russia and Kazakhstan; after the July 2024 Yandex/Nebius split international customers contract via non-Russian entities in USD — weigh data-residency and sanctions considerations.

Pricing

Note that the "Free Plan" is intended to represent ongoing free resources i.e. not trials or sign-up credits.

Free Plan Bill Limits First Paid Tier
Alibaba Cloud Function Compute 🚫 since Aug 2024; 3-month trial of 150k CUs / mo26 + 220 GB / mo egress via CDT27 🚫 (instance caps only)28 Tiered Compute-Unit billing: $0.000020 → $0.000017 → $0.000014 per CU29 + egress via CDT
Appwrite Functions 750k execs + 100 GB-hrs compute + 5 GB bandwidth / mo (free projects pause after 7 days of inactivity)30 ✅ (budget caps, paid plans)31 Pro $25 / mo / project incl. 3.5m execs + 1,000 GB-hrs + 2 TB bandwidth; then $2 per 1m execs + $0.06 per GB-hr + $15 per 100 GB32
AWS Lambda 1m reqs / mo + 400,000 GB-s / mo (always free)33 + 100 GB / mo egress34 🚫 (budget alerts only)35 $0.20 per 1m reqs + $0.0000166667 per GB-s x86 ($0.0000133334 Arm)36 + ~$0.09 per GB egress34; INIT phase billed since Aug 202537
AWS Lambda@Edge None38 🚫 $0.60 per 1m reqs + $0.00005001 per GB-s (1 ms granularity)38 + egress (~$0.09 per GB)
Azure Container Apps 180k vCPU-s + 360k GiB-s + 2m reqs / mo39; + 100 GB / mo egress40 ✅ only on credit-based subscriptions41 $0.000024 per vCPU-s ($0.000003 idle) + $0.000003 per GiB-s + $0.40 per 1m reqs over 2m39 + $0.087 per GB egress40
Azure Functions Consumption: 1m execs + 400k GB-s / mo; Flex: 250k execs + 100k GB-s / mo42; + 100 GB / mo egress40 ✅ only on credit-based subscriptions41 Consumption: $0.20 per 1m + $0.000016 per GB-s; Flex: $0.40 per 1m + $0.000026 per GB-s42; + $0.087 per GB egress (over 100 GB)40
Cloudflare Workers 100k reqs / day, 10ms CPU / req; egress always free43 🚫 (per-invocation CPU caps only)44 $5 / mo incl. 10m reqs + 30m CPU-ms; then $0.30 per 1m reqs + $0.02 per 1m CPU-ms (wall time & egress not billed)43
DigitalOcean Functions 90,000 GiB-s / mo45 🚫 (billing alerts only)46 $0.0000185 per GiB-s (no per-request fee, min. 100 ms billed per invocation)45
Fermyon 100k reqs + 5GB egress47 NA Growth $19.38 / mo: 1m reqs + 50GB egress48
Fly.io 🚫 for new orgs since Oct 2024 (one-time trial: 2 machine-hrs or 7 days)49 NA Per-second machine pricing (shared-cpu-1x 256 MB ≈ $2 / mo, region-dependent)50 + $0.02 per GB egress (NA/EU) + $0.15 per GB / mo stopped machine rootfs50
Google Cloud Run 2m reqs + 180k vCPU-s + 360k GiB-s RAM + 1 GiB NA egress / mo51 🚫 (budget alerts; programmatic cutoff possible)52 $0.40 per 1m reqs + $0.000024 per vCPU-s + $0.0000025 per GiB-s51 + egress at network rates
Huawei Cloud FunctionGraph 1m reqs + 400,000 GB-s / mo (permanent)53 🚫 (budgets alert-only)54 ≈$0.20 per 1m reqs + $0.0000167 per GB-s ❔ (intl rates in console calculator; CN list ¥1.33 per 1m + ¥0.00011108 per GB-s)55; egress billed via EIP/NAT55
IBM Code Engine 100k vCPU-s + 200k GB-s + 100k reqs / mo (shared across all Code Engine apps/jobs/fns)56 🚫 (spending notifications only)57 $0.00003431 per vCPU-s + $0.00000356 per GB-s + $0.538 per 1m reqs56
Koyeb One free instance (0.1 vCPU / 512 MB), scales to zero after 1 h idle58 NA Per-second instance billing from $0.0000006 / s (eco-nano, ≈ $1.61 / mo)59
Modal $30 / mo recurring usage credit (Starter plan)60 ✅ (prepaid credits) $0.0000131 per CPU core-s + $0.00000222 per GiB-s RAM (no per-request fee; egress not billed as a line item)60
Oracle (OCI) Functions 2m reqs + 400k GB-s / mo + 10 TB / mo egress61 🚫 (budget alerts only)62 $0.0000002 per req + $0.00001417 per GB-s + $0.0085 per GB egress61
Railway $1 / mo usage credit (0.5 GB RAM / 1 vCPU cap); "Serverless" sleep ≈ $0 compute while idle63 ✅ (hard usage limit stops workloads)64 Hobby $5 / mo (incl. $5 usage) + $10 per GB RAM / mo + $20 per vCPU / mo + $0.05 per GB egress (per-minute metering)65
Render Free instance (0.1 CPU / 512 MB), 750 hrs / mo, sleeps after 15 min idle66 NA $7 / mo Starter instance (0.5 CPU / 512 MB)67 + $0.15 per GB egress over included 5 GB (Hobby) / 25 GB (Pro) / 1 TB (Scale)68
Scaleway Serverless Functions 1m reqs + 400k GB-s / mo; free ingress/egress69 🚫 (billing alerts only)70 €0.15 per 1m reqs + €0.0000170 per GB-s69
Tencent Cloud Functions 🚫 (3-month trial only; free tier eliminated 2022–2024) ? Pay-as-you-go: GB-s + per-10k invocations + egress (price table)
Vercel Functions Hobby: 1m invocations + 4 active-CPU-hrs + 360 GB-hrs provisioned mem + 100 GB transfer / mo71 ✅ (hard caps on Hobby)71 Pro $20 / seat / mo (incl. $20 / mo usage credit) + $0.60 per 1m invocations + $0.128 per active-CPU-hr + $0.0106 per GB-hr provisioned mem72
Yandex Cloud Functions 1m invocations + 10 GB×hr / mo + 100 GB / mo egress73 🚫 (budgets notify; can trigger a cutoff function)74 $0.144 per 1m invocations + $0.049 per GB×hr (≈$0.0000137 per GB-s; 100 ms rounding)75

reqs = requests, m = million, mo = month, s = seconds, mem = memory, k = thousand, ms = milliseconds, CU = Alibaba Compute Unit

Runtime Limits

Memory Execution Time (s) Payloads (MB) Code Size (MB) Scale Limits
Default Max Default Max Request Response
Alibaba Cloud Function Compute 512 MB (console)76 32 GB76 3s76 86,400 (24 h)77 32 (sync) / 0.128 (async)78 not documented77 500 (zip, major regions)77 100 on-demand inst. / region default79
Appwrite Functions 512 MB (0.5 CPU; Free plan fixed)80 4 GB (4 CPU, Pro)80 - 900s (sync / HTTP capped at 30s)81 not documented not documented ❔ (30 MB self-hosted default) not published
AWS Lambda 128 MB 10 GB82 3s 15min82 682 6 (20 streaming)82 50 (zip) / 250 (unzip) / 10 GB (image)82 1k concurrent / region (soft)82
AWS Lambda@Edge 128 MB 3 GB (origin)83 - 5s viewer / 30s origin83 0.04 viewer / 1 origin (body exposed to fn)84 0.04 viewer / 1 origin (generated)84 1 (viewer) / 50 (origin) zip83 per CloudFront quotas83
Azure Container Apps configurable 8 GiB (4 vCPU) / replica85 NA (HTTP ingress 240s default)86 30 min idle (premium ingress)86 not documented not documented NA (image) 0–1,000 replicas (default max 10)87
Azure Functions 1.5 GB (Consumption, fixed)88 4 GB (Flex: 0.5 / 2 / 4 GB sizes)89 5min 10min (Consumption); no max on Flex (HTTP: 230s)88 21088 not documented88 1 GB (deployment package)90 100 inst. (Consumption) / 1,000 (Flex)89
Cloudflare Workers 128 MB (fixed)91 128 MB 10ms CPU (free) / 30s CPU (paid default) 300s CPU (paid); no wall-clock limit91 100 (zone-plan dependent)92 none enforced 3 (free) / 10 (paid), compressed91 100 / 500 Workers per account91
DigitalOcean Functions 256 MB93 1 GB 3s 15min (sync auto-converts to async at 30s)94 193 193 4893 120 concurrent / namespace93
Fermyon ? (Cloud); 128 MiB default on Wasm Functions95 ? 30s47 30s 1047 10 10047 1k RPS47
Fly.io 256 MB 128 GB (16 perf. vCPU)96 NA NA NA NA NA NA
Google Cloud Run 512 MiB97 32 GiB97 5min98 60min98 32 (HTTP/1 only)99 32 (unbounded if streamed)99 None 80×vCPU (CLI) or 80 (console) concurrent reqs / inst. default, max 1k100
Huawei Cloud FunctionGraph ❔ 10 GB101 3s102 259,200 (72 h async; 900s sync)102 6 (sync) / 0.25 (async)101 6101 40 (console zip) / 300 via OBS / 10 GB (image)101 400 fns; 1k concurrent inst. default103
IBM Code Engine 4 GB (1 vCPU)104 4 GB - 120s104 5104 5104 0.1 (inline) / 200 (source)104 20 fns / project; 250 inst.104
Koyeb per instance type - NA NA NA NA NA instance-based
Modal configurable 336 GiB (64 CPUs)105 300s105 86,400 (24 h)105 4 GiB106 unlimited (streamed)106 NA (image-based) 100 containers / 10 GPUs (Starter)107
Oracle (OCI) Functions 128 MB108 3 GB108 30s 300s (3,600s detached)109 6108 6108 ? 60 GB total mem / AD108
Railway per plan (0.5 GB free cap)110 8 GB / replica (Hobby); 24 GB (Pro)111 NA NA (HTTP: 15 min max, 5 min idle)112 NA NA NA (image: 4 GB free / 100 GB Hobby)110 ~10k conns / ~11k RPS per domain112
Render 512 MB (free) 32 GB (8 CPU, Pro Ultra; custom above)113 NA NA NA NA NA 100 inst. / service (autoscaling on paid)113
Scaleway Serverless Functions 128 MB (min tier)114 4 GB114 300s115 3,600115 6115 not documented115 100 (zip) / 500 (unzip)115 50 inst. / fn; 5k reqs / s115
Tencent Cloud Functions 128 MB116 3 GB (large-mem specs to 120 GB)116 3s117 900s (24 h async)117 6118 6118 500 (unzip)118 region-shared concurrency
Vercel Functions 2 GB (Standard, 1 vCPU)119 4 GB (Performance, 2 vCPU)119 300s120 800s Pro (300s Hobby; 1,800s beta)120 4.5120 4.5120 250 (500 for Python; 5 GB "Large Functions" beta)121 ~30k concurrent (Pro)122
Yandex Cloud Functions 128 MB123 8 GB (4 vCPU)123 ❔ 600s (3,600s long-lived)124 3.5123 3.5123 3.5 (console zip) / 128 via S3 / 680 unzipped123 10 fns / cloud; 10 concurrent / AZ default123

AWS allocates 1 vCPU per 1,769 MB of memory configured125. Cloudflare bills and limits CPU time only — wall-clock time (e.g. waiting on I/O) is unlimited and unbilled43. Modal, Fly.io, Koyeb, Railway, Render, and Azure Container Apps size CPU/memory per instance/replica rather than per invocation.

Other Platform Products

SQL DB No SQL DB Blob Store File Hosting GPU
Alibaba Cloud Function Compute ✅ ✅ ✅ ✅ ✅
Appwrite Functions 🚫 (document API over SQL)126 ✅ (TablesDB)126 ✅ (Storage) ✅ (Sites)127 🚫
AWS Lambda and Lambda@Edge ✅ ✅ ✅ ✅ ✅
Azure Container Apps ✅ ✅ ✅ ✅ ✅ (serverless GPUs)128
Azure Functions ✅ ✅ ✅ ✅ ✅
Cloudflare Workers SQLite (D1) ✅ ✅ ✅ ✅ (Workers AI)
DigitalOcean Functions ✅ ✅ ✅ (Spaces) ✅ ✅
Fermyon SQLite 🚫 🚫 🚫 ✅
Fly.io ✅ (Managed Postgres)129 ✅ ✅ (Tigris) 🚫 🚫 after Aug 2026
Google Cloud Run ✅ ✅ ✅ ✅ ✅
Huawei Cloud FunctionGraph ✅ ✅ (GeminiDB / DDS) ✅ (OBS) ✅ ✅ (incl. GPU functions)130
IBM Code Engine ✅ ✅ ✅ ✅ ✅
Koyeb ✅ (Serverless Postgres, GA)131 🚫 🚫 🚫 ✅
Modal 🚫 ✅ (Dicts/Queues) ✅ (Volumes) 🚫 ✅
Oracle (OCI) Functions ✅ ✅ ✅ ✅ ✅
Railway ✅ (templates, unmanaged)132 ✅ (Redis / Mongo templates)132 ✅ (Buckets)133 🚫 🚫134
Render ✅ (Postgres) ✅ (Key Value) 🚫 (object storage in alpha)135 ✅ (static) 🚫
Scaleway Serverless Functions ✅ ✅ ✅ ❔ ✅
Tencent Cloud Functions ✅ ✅ ✅ ✅ ✅
Vercel Functions ✅ ✅ ✅ (Blob) ✅ 🚫
Yandex Cloud Functions ✅ ✅ (YDB serverless) ✅ ✅ (static hosting)136 ✅ (GPU VMs)

Performance (median times)

TODO: Need a benchmark suite for Python, see this JS suite

PoPs (if edge) or regions Uptime Cold Response (ms) Warm Response (ms) Overhead (ms)
Alibaba Cloud Function Compute
Appwrite Functions
AWS Lambda ~2,500 (FastAPI, per Cloudflare's cross-vendor test)137
AWS Lambda@Edge
Azure Container Apps no official figure; ~15,000–30,000 commonly reported138
Azure Functions
Cloudflare Workers ~1,000 (with FastAPI, post-Dec-2025 snapshots)137
DigitalOcean Functions
Fermyon
Fly.io
Google Cloud Run ~3,100 (FastAPI, per Cloudflare's cross-vendor test)137
Huawei Cloud FunctionGraph
IBM Code Engine
Koyeb ~200 (Light Sleep) / 1,000–5,000 (Deep Sleep)139
Modal
Oracle (OCI) Functions
Railway
Render ~60,000 ("about one minute" free-tier spin-up)66
Scaleway Serverless Functions
Tencent Cloud Functions
Vercel Functions
Yandex Cloud Functions

Security Considerations

TODO: e.g. compliance certifications, data encryption, and network security options

See also awesome serverless security

Discussions, Community, and Support

Ours Forum GitHub SO Reddit
Alibaba Cloud Function Compute Link Forum SO r/AlibabaCloud
Appwrite Functions Discord GitHub SO r/appwrite
AWS Lambda and Lambda@Edge Link re:Post GitHub SO r/aws
Azure Container Apps Forum GitHub SO r/AZURE
Azure Functions Link Forum GitHub SO r/AZURE
Cloudflare Workers Link Forum GitHub SO r/CloudFlare
DigitalOcean Functions Community GitHub SO
Fermyon Link Discord Spin (CNCF) SO
Fly.io Link Forum SO
Google Cloud Run Link Group GitHub SO r/Firebase and r/googlecloud
Huawei Cloud FunctionGraph Forum GitHub SO
IBM Code Engine Link Slack GitHub SO
Koyeb Community
Modal Slack GitHub
Oracle (OCI) Functions Link Forum GitHub SO r/oraclecloud
Railway Central Station GitHub
Render Discord (forum retired Mar 2026) Feedback
Scaleway Serverless Functions Slack GitHub SO
Vercel Functions Link Help GitHub SO r/Vercel
Yandex Cloud Functions GitHub SO

References and Useful Links

All sources below were used to verify the data above and were accessed on July 12, 2026. Sources cited directly by table cells appear as numbered footnotes at the very bottom of this page.

Alibaba Cloud Function Compute

Appwrite Functions

AWS Lambda / Lambda@Edge

Azure Container Apps

Azure Functions

Cloudflare Workers (Python)

DigitalOcean Functions

Fermyon / Spin

Fly.io

Google Cloud Run

Huawei Cloud FunctionGraph

IBM Code Engine

Koyeb

Modal

Oracle (OCI) Functions

Railway

Render

Scaleway Serverless Functions

Tencent Cloud Functions

Vercel Functions

Yandex Cloud Functions

Watchlist platforms

Excluded platforms

Other comparisons

Footnotes

  1. Alibaba FC 3.0 Python runtimes ↩

  2. Appwrite function runtimes — Appwrite Cloud offers python-3.9/3.12/3.14 and python-ml-3.11; Appwrite Cloud GA (Aug 6, 2025) ↩ ↩2

  3. Developing Appwrite functions — def main(context), dependencies via a requirements.txt build command ↩

  4. Python 3.14 runtime now available in AWS Lambda (Nov 18, 2025); runtime list & deprecation schedule ↩

  5. Azure Functions supported languages — Python 3.14 GA (as of early July 2026; EOL Oct 2030) ↩

  6. AsgiFunctionApp / WsgiFunctionApp in the azure-functions Python library ↩

  7. How Python Workers work — Pyodide-based; released bundle is Pyodide 0.28 / CPython 3.13 per workerd python_metadata.bzl ↩

  8. Python Workers are in open beta ↩

  9. DigitalOcean Functions Python runtime reference — python 3.9/3.11/3.12/3.13, __main__.py, requirements.txt + build.sh ↩ ↩2

  10. doctl serverless workflow uses a connected cloud namespace; there is no offline emulator ↩

  11. spin-python-sdk requires Python 3.10+ (componentize-py) ↩

  12. Fermyon Cloud is an open beta; the Starter plan is free without expiration. The GA sibling is Fermyon Wasm Functions on Akamai. ↩

  13. Cloud Run functions runtime support — Python 3.14 GA; uv is the default installer from 3.14 onward ↩

  14. Python dependencies on Cloud Run — requirements.txt or pyproject.toml (GA July 2026) ↩

  15. FunctionGraph supported runtimes — Python up to 3.12 ↩

  16. IBM Code Engine function runtimes — Python 3.13; 3.11 deprecated with EOL Oct 2026 ↩

  17. Modal images — Python 3.10–3.14 (incl. 3.14t) selectable per image ↩

  18. Languages supported by OCI Functions; Python FDK supports 3.11/3.12 ↩

  19. Railpack Python — 3.10+, default 3.13; auto-detects Flask/FastAPI/Django; requirements.txt, pyproject (poetry/pdm/uv), or Pipfile ↩ ↩2 ↩3

  20. Render Python version docs — new services default to Python 3.14.3 with uv (since Feb 2026) ↩

  21. Scaleway function runtimes — Python 3.14 available (July 2026) ↩

  22. Tencent SCF Python runtime — capped at Python 3.10 ↩

  23. Vercel Python runtime (Beta) — 3.12 default; Python 3.13/3.14 available since Feb 2026 ↩ ↩2

  24. Yandex Cloud Functions runtimes — python312 and python314 supported (3.7–3.11 desupported); Python handler model — async supported; per-instance concurrency is not available for Python ↩ ↩2

  25. requirements.txt dependencies are pip-installed automatically when a function version is created ↩

  26. Alibaba FC trial quota — 150,000 CUs/mo for 3 months ↩

  27. CDT public-network free quota raised to 200 GB/mo (plus 20 GB CN) ↩

  28. No hard spending cap exists; Alibaba's cost-containment mechanism is capping maximum on-demand instances. ↩

  29. Alibaba Function Compute pricing — tiered CU billing ↩

  30. Appwrite pricing — Free plan includes 750k executions, 100 GB-hours, 5 GB bandwidth/mo; free projects pause after 1 week of inactivity (Feb 2026) and paused free projects are deleted after 90 days (Jun 2026) ↩

  31. Appwrite budget caps limit add-on spend on paid plans, with alerts from 75% ↩

  32. Appwrite pricing — Pro $25/mo/project; overages $2 per 1M executions, $0.06 per GB-hour, $15 per 100 GB bandwidth; Sept 2025 repricing details ↩

  33. AWS Lambda pricing — always-free tier of 1M requests + 400,000 GB-s/mo, retained under the July 2025 credits-based free plan ↩

  34. 100 GB/mo aggregate free data transfer out, then ~$0.09/GB (first 10 TB, us-east-1); see also data transfer charges for serverless ↩ ↩2

  35. AWS Budgets sends alerts (and can trigger actions) but AWS has no account-wide hard spending cap. ↩

  36. AWS Lambda pricing — GB-s rates are tiered, dropping above 6B GB-s/mo (x86); rates re-verified against the AWS Price List API publication of 2026-07-09. ↩

  37. AWS Lambda standardizes billing for the INIT phase, effective Aug 1, 2025 ↩

  38. Lambda@Edge pricing — $0.60/1M requests, $0.00005001/GB-s, metered at 1 ms granularity, excluded from the Lambda free tier ↩ ↩2

  39. Azure Container Apps pricing — Consumption: first 180k vCPU-s + 360k GiB-s + 2M requests/mo free, then $0.000024/vCPU-s active ($0.000003 idle), $0.000003/GiB-s, $0.40 per additional 1M requests; billing docs (idle rates, scale-to-zero = no charges) ↩ ↩2

  40. Azure bandwidth pricing — first 100 GB/mo free, then $0.087/GB (Zone 1) ↩ ↩2 ↩3 ↩4

  41. Azure spending limit — on by default for credit-based subscriptions only; not available on pay-as-you-go ↩ ↩2

  42. Azure Functions pricing — Consumption and Flex Consumption rates and monthly free grants ↩ ↩2

  43. Workers pricing — free 100k reqs/day + 10 ms CPU; paid $5/mo incl. 10M reqs + 30M CPU-ms; duration and egress unbilled ↩ ↩2 ↩3

  44. No spend cap exists; Cloudflare's cost-control mechanism is per-invocation CPU limits ↩

  45. DigitalOcean Functions pricing — 90,000 GiB-s/mo free, $0.0000185/GiB-s, no per-invocation fee, 100 ms minimum ↩ ↩2

  46. DigitalOcean billing alerts notify but cannot cap usage ↩

  47. Fermyon Cloud FAQ quotas — 100k requests + 5 GB egress/mo free, 30 s handler duration, 10 MB HTTP body, 100 MB app package, 1,000 req/s ↩ ↩2 ↩3 ↩4 ↩5

  48. Fermyon Cloud plans — Growth $19.38/mo with 1M requests + 50 GB egress ↩

  49. Fly.io free trial — 2 hours of machine runtime or 7 days, whichever comes first; no ongoing free allowances since Oct 7, 2024 ↩

  50. Fly.io pricing — per-second machine billing (region-dependent; shared-cpu-1x 256 MB from $1.94/mo), $0.02/GB NA/EU egress, $0.15/GB per 30 days stopped-machine rootfs ↩ ↩2

  51. Cloud Run pricing — request-based billing rates and always-free tier (us-central1) ↩ ↩2

  52. Google Cloud budgets alert but do not cap spending; billing can be disabled programmatically via budget notifications ↩

  53. FunctionGraph free tier — 1M requests + 400,000 GB-s per month, resets monthly (permanent, pay-per-use accounts) ↩

  54. Huawei Cloud budgets are alert-only — "budgets cannot stop consumption" ↩

  55. FunctionGraph billing overview — billed per request + GB-s duration; egress is billed by the attached network service (EIP/NAT/APIG), not FunctionGraph; international USD rates are only exposed in the console price calculator — China list prices shown for reference ↩ ↩2

  56. IBM Code Engine pricing; exact per-unit rates and free-tier scope in IBM's official cost scenario ↩ ↩2

  57. IBM Cloud spending notifications alert at thresholds but "don't stop charges from incurring" ↩

  58. Koyeb pricing — free instance 0.1 vCPU / 512 MB; free instances scale to zero after 1 hour without traffic ↩

  59. Koyeb instances — eco-nano $0.0000006/s (≈$1.61/mo), billed per second ↩

  60. Modal pricing — $30/mo recurring credit on Starter; $0.0000131 per physical CPU core-s, $0.00000222 per GiB-s; no per-request or data-transfer line items ↩ ↩2

  61. OCI price list — Functions: $0.0000002/invocation, $0.00001417/GB-s, 2M requests + 400k GB-s always free; 10 TB/mo free egress then $0.0085/GB ↩ ↩2

  62. OCI budgets are "soft limits" that alert but do not stop spending ↩

  63. Railway Serverless (app sleeping) — sleeps after ~10 min without outbound traffic (open DB connections or telemetry keep it awake); wakes on inbound request, which may return a 502 on first hit ↩

  64. Railway usage limits — a configurable hard limit stops all workloads (min $10), plus soft alert thresholds ↩

  65. Railway pricing — Hobby $5/mo incl. $5 usage; $10 per GB RAM/mo, $20 per vCPU/mo, $0.05/GB egress, metered by the minute ↩

  66. Render free instances — 0.1 CPU / 512 MB, 750 hrs/mo per workspace, spin down after 15 min idle, spin-up takes about one minute ↩ ↩2

  67. Render pricing — Starter instance $7/mo (0.5 CPU / 512 MB) ↩

  68. Render workspace plans (Apr 2026) — Hobby $0 / Pro $25 / Scale $499 with 5 / 25 / 1,000 GB included bandwidth, $0.15/GB overage ↩

  69. Scaleway serverless FAQ — free tier 1M requests + 400k GB-s/mo, €0.00000015/request + €0.0000170/GB-s beyond, free ingress/egress ↩ ↩2

  70. Scaleway billing alerts notify only; no hard cap ↩

  71. Vercel Hobby plan included usage — hard-paused when exceeded ↩ ↩2

  72. Vercel Pro plan — $20/seat/mo with $20/mo flexible usage credit; rates per usage & pricing docs; invocations billed per unit ($0.0000006) since May 2026 ↩

  73. Yandex serverless free tier — 1M invocations + 10 GB×hr per month, resets monthly; first 100 GB/mo of egress free ↩

  74. Yandex budgets are notification-only, but budget triggers can invoke a function that stops resources ↩

  75. Yandex Cloud Functions pricing — $0.144 per 1M invocations + $0.049230 per GB×hour (USD for international entities; RUB for Russian customers), rounded up to 100 ms ↩

  76. FC 3.0 CreateFunction API — memory 128–32,768 MB (no documented default; the console pre-fills 512 MB), timeout default 3 s / max 86,400 s ↩ ↩2 ↩3

  77. Alibaba FC 3.0 limits of usage ↩ ↩2 ↩3

  78. Alibaba FC synchronous invocations (32 MB) and async (128 KB) ↩

  79. Alibaba FC max on-demand instances (default 100/region) ↩

  80. Appwrite compute tiers — 0.5 CPU / 512 MB on Free (fixed), configurable up to 4 CPU / 4 GB on paid plans ↩ ↩2

  81. Appwrite function timeout — system-wide maximum 900 s; synchronous (HTTP) executions are capped at 30 s ↩

  82. AWS Lambda quotas; container images up to 10 GB; timeout configuration ↩ ↩2 ↩3 ↩4 ↩5 ↩6

  83. CloudFront quotas on Lambda@Edge — 128 MB viewer / 3,008 MB origin memory, 5 s viewer / 30 s origin timeout, 1 MB viewer / 50 MB origin package size ↩ ↩2 ↩3 ↩4

  84. Request bodies exposed to the function are truncated at 40 KB (viewer) / 1 MB (origin); generated responses are capped at the same sizes; see also generated-response size limits ↩ ↩2

  85. Container Apps CPU/memory — up to 4 vCPU / 8 GiB per replica on Consumption (workload-profiles environments; 2 vCPU / 4 GiB in legacy consumption-only environments) ↩

  86. Container Apps ingress — 240 s default request timeout; premium ingress allows a 4–30 min idle request timeout ↩ ↩2

  87. Container Apps scale rules — 0–1,000 replicas, default max 10; scaled-to-zero apps incur no usage charges ↩

  88. Azure Functions service limits — 1.5 GB Consumption memory, 210 MB max request size, timeouts per plan ↩ ↩2 ↩3 ↩4

  89. Flex Consumption plan — 512 MB / 2,048 MB / 4,096 MB instance sizes, scale to 1,000 instances ↩ ↩2

  90. Maximum deployment package size is 1 GB (run-from-package) ↩

  91. Workers limits — 128 MB memory, 5 min max CPU (30 s default), 3/10 MB gzip'd script size, 100/500 Workers ↩ ↩2 ↩3 ↩4

  92. Request-body limit follows the zone's Cloudflare plan: 100 MB Free/Pro, 200 MB Business, 500 MB Enterprise default ↩

  93. DigitalOcean Functions limits ↩ ↩2 ↩3 ↩4 ↩5

  94. Synchronous invocations are converted to asynchronous after 30 seconds ↩

  95. Fermyon Wasm Functions FAQ — 128 MiB default memory per instance, increasable on request ↩

  96. Fly machine sizing — largest preset performance-16x; RAM up to 8 GB per performance vCPU (128 GB) ↩

  97. Cloud Run memory limits — 512 MiB default, 32 GiB max ↩ ↩2

  98. Cloud Run request timeout — 5 min default, 60 min max ↩ ↩2

  99. Cloud Run quotas — 32 MiB request cap applies to HTTP/1 only; responses over 32 MiB must be streamed ↩ ↩2

  100. Cloud Run concurrency — default 80×vCPUs for gcloud/Terraform deploys (80 for console), maximum 1,000 ↩

  101. FunctionGraph notes & constraints — memory 128 MB–10,240 MB, 6 MB sync request/response (256 KB async), code 40 MB console zip / 300 MB via OBS / 10 GB images; memory options ↩ ↩2 ↩3 ↩4

  102. FunctionGraph timeout — default 3 s, configurable up to 259,200 s (72 h); synchronous invocations ≤900 s ↩ ↩2

  103. FunctionGraph quotas — 400 functions and 1,000 concurrent on-demand instances per region by default ↩

  104. IBM Code Engine limits — function memory/CPU combinations, 120 s timeout, payload and code size ↩ ↩2 ↩3 ↩4 ↩5 ↩6

  105. Modal resources — up to 64 CPUs / 336 GB per container; timeouts — default 300 s, max 24 h ↩ ↩2 ↩3

  106. Modal web endpoints — request bodies up to 4 GiB, response bodies unlimited (streamed) ↩ ↩2

  107. Modal plans — Starter: 100 containers, 10 concurrent GPUs ↩

  108. Customizing functions — memory 128 MB–3 GB; concurrency capped at 60 GB total function memory per AD ↩ ↩2 ↩3 ↩4 ↩5

  109. Detached (long-running) function invocations up to 3,600 s (Oct 2025) ↩

  110. Railway plans — Free plan: $1/mo credit with 0.5 GB RAM / 1 vCPU / 4 GB image caps (100 GB image on Hobby); free plan announcement (Aug 2025); Serverless sleep means no compute charges while asleep ↩ ↩2

  111. Railway scaling — per-replica up to 8 GB / 8 vCPU on Hobby and 24 GB / 24 vCPU on Pro ↩

  112. Railway public-networking limits — requests up to 15 min if data flows (5 min idle close), 32 KB headers, ~10k concurrent connections and ~11k RPS per domain ↩ ↩2

  113. Render scaling — autoscaling on paid instance types, max 100 instances/service; largest standard instance Pro Ultra 8 CPU / 32 GB, custom types above ↩ ↩2

  114. Scaleway memory/CPU tiers — 128 MB to 4,096 MB ↩ ↩2

  115. Scaleway function limitations — timeout 10 s–60 min (default 300 s), 6 MiB request payload, 100 MiB zip / 500 MiB code, 50 instances/function, 5,000 req/s ↩ ↩2 ↩3 ↩4 ↩5 ↩6

  116. Tencent SCF memory specs — 64–3,072 MB standard plus fixed large-memory specs of 6/14/30/60/120 GB ↩ ↩2

  117. Tencent SCF execution timeout — 1–900 s (default 3 s); asynchronous executions up to 24 h ↩ ↩2

  118. Tencent SCF quota limits ↩ ↩2 ↩3

  119. Vercel function memory — Standard 2 GB / 1 vCPU (Hobby fixed), Performance 4 GB / 2 vCPU ↩ ↩2

  120. Vercel function duration (default 300 s; max 300 s Hobby / 800 s Pro; 1,800 s beta for Node.js & Python); 4.5 MB request & response body limit ↩ ↩2 ↩3 ↩4

  121. 250 MB bundle standard; 500 MB for Python; "Large Functions" up to 5 GB in public beta ↩

  122. Vercel concurrency — 30,000 on Pro (burst 1,000/10 s per region), 100,000 on Enterprise ↩

  123. Yandex Cloud Functions limits — memory 128 MB–8 GB (4 vCPU at 8 GB), 3.5 MB request/response, code 3.5 MB console zip / 128 MB via bucket / 680 MB unzipped; default quotas: 10 functions per cloud, 10 concurrent calls and 10 instances per AZ (raisable) ↩ ↩2 ↩3 ↩4 ↩5 ↩6

  124. Maximum execution 10 min, or up to 1 h for long-lived functions ↩

  125. "At 1,769 MB, a function has the equivalent of one vCPU" ↩

  126. Appwrite TablesDB — document-style API backed by SQL (MariaDB) ↩ ↩2

  127. Appwrite Sites — static & SSR hosting (launched May 2025) ↩

  128. Serverless GPUs (A100/T4) GA on Azure Container Apps with scale to zero (Mar 2025) ↩

  129. Fly.io Managed Postgres ↩

  130. GPU-accelerated FunctionGraph functions ↩

  131. Koyeb Serverless Postgres GA (May 2025) ↩

  132. Railway database templates (Postgres/MySQL/Redis/Mongo) are explicitly "unmanaged services" ↩ ↩2

  133. Railway Storage Buckets — S3-compatible object storage, $0.015/GB-mo (GA Sept 2025) ↩

  134. Railway lists machine-learning compute as an unsupported use case (no GPUs) ↩

  135. Render object storage is in early access/alpha ↩

  136. Yandex Object Storage static website hosting ↩

  137. Cloudflare's Dec 2025 cold-start changelog — mean cold starts with httpx+FastAPI+Pydantic: Cloudflare 1,027 ms vs AWS Lambda 2,502 ms vs Google Cloud Run 3,069 ms (vendor-run benchmark) ↩ ↩2 ↩3

  138. Microsoft's cold-start doc describes the pull/provision/start delay without an official figure; Microsoft community guidance reports ~15–30 s for heavier images ↩

  139. Koyeb Light Sleep (~200 ms wake via snapshotting) vs Deep Sleep (1–5 s cold start) ↩

About

A comparison of hosts / providers for Python serverless functions (aka Faas)

Topics

python awesome cloud serverless hosting python3 comparison serverless-functions python-lambda

Resources

Readme

License

MIT license

Code of conduct

Code of conduct
Activity

Stars

49 stars

Watchers

1 watching

Forks

1 fork
Report repository

Contributors