Serverless Functions across clouds

Event-driven function platforms (Lambda, Cloud Functions, Azure Functions, Workers) provisioned by verified modules.

10 verified modules, 3 of them live-tested apply→verify→destroy; the rest are static-validated, live-test pending.

Compare by provider

Provider	Module	Verification
Alibaba Cloud	A Function Compute 3.0 Function with Its Own Role, No Internet, and Logs to Log Service	static-validated
AWS	Lambda Function (Packaged & Wired)	✓ live-tested
Azure	Azure Functions App	✓ live-tested
Cloudflare	Cloudflare Workers Platform	static-validated
Google Cloud	Cloud Run Function (gen2)	✓ live-tested
Huawei Cloud	A FunctionGraph Function with Its Own Agency, LTS Logs, and Secrets Encrypted with Your Key	static-validated
IBM Cloud	A Code Engine Function in Its Own Project, Private, with a Compute Resource Token	static-validated
Oracle Cloud	Functions Application	static-validated
Scaleway	A Serverless Function in Its Own Namespace, Private, HTTP Redirected, Idling at Zero	static-validated
Tencent Cloud	A Serverless Cloud Function with Its Own Role, No Public Network, and Logs to CLS	static-validated

Match the runtime and event sources you need, then check cold-start behaviour and per-invocation pricing for your traffic shape.

For long-running, stateful, or high-throughput steady workloads, a container service or VM is cheaper and avoids timeout limits.