Directory Cloud InfrastructureServerless & Edge ComputingwasmCloud

wasmCloud

Open Source

About wasmCloud

wasmCloud offers an open source orchestration platform for building, managing, and scaling WebAssembly applications. It is a project from the Cloud Native Computing Foundation that enables teams to build polyglot applications composed of reusable Wasm components. Applications run across any cloud, Kubernetes, datacenter, or edge. The platform supports first-tier integration with Kubernetes, AWS, Azure, GCP, Jenkins, GitHub Actions, ArgoCD, Backstage, Chainguard, databases, and messaging systems. It is listed as a Cloud Native Computing Foundation Incubating project.

Products

wash CLI: Provides development tooling for working with wasmCloud.

Used for

Building polyglot applications composed of reusable Wasm components.
Maintaining thousands of diverse apps centrally using version-controlled components.
Running the same Wasm application across operating systems and architectures without new builds.
Extending the wasmCloud host at runtime to support custom dependencies, hardware, or business contracts.
Distributing applications across clouds, regions, clusters, and edges.

Who it is for

Platform engineering teams.
American Express uses it for an enterprise multi-tenant Function-as-a-Service platform.
Adobe and Akamai use it to run WebAssembly across cloud services, Kubernetes clusters, and edges.
Machine Metrics uses it to move platform capabilities across edges and clouds on the factory floor.

From wasmCloud's own website, read 2026-10-24. How we build listings.

How to evaluate Serverless & Edge Computing

This is how the CIOPages Research Team evaluates this category. It is not an assessment of wasmCloud. It comes from our Serverless & Function-as-a-Service (FaaS) buyer guide.

25%

Workload Fit & Execution Limits

Max execution duration, memory and payload ceilings, concurrency model and account limits, support for long-running and stateful work (Durable Functions, Durable Objects), and whether your traffic is bursty enough to suit FaaS or steady enough to favor a container

20%

Cold-Start & Latency Behavior

Cold-start profile by runtime (V8 isolate, Wasm, container, JVM), mitigations such as SnapStart, provisioned/always-ready instances, and scale-to-zero startup time, plus regional versus edge placement for user-facing paths

20%

Event Model & Lock-In / Portability

Breadth of native event sources and triggers, depth of managed-service bindings, how proprietary the function packaging is, and the realistic exit path — portable containers or WebAssembly versus a provider-specific event fabric you would have to rewrite

15%

Integration & Ecosystem Depth

First-class ties to the surrounding cloud (IAM, queues, streams, databases, API gateway), orchestration and workflow tooling, language and runtime coverage, and the maturity of IaC and CI/CD support

10%

Observability & Operations

Distributed tracing across functions and event sources, structured logging and metrics, local emulation and testability, deployment and rollback model, and how hard it is to debug a failure that spans several triggers

10%

Security, Compliance & Cost Model

Per-function least-privilege IAM, network isolation (VPC/private networking), secrets handling, SOC 2 / ISO 27001 / regional residency, and whether the billing unit (per-invocation, GB-second, CPU-time, per-request) matches your traffic shape

Other Serverless & Edge Computing Vendors

View all

Alibaba Cloud Serverless Workflow

CIOPages put this listing together from public sources. It’s information, not an endorsement. How we build listings. Work here? Claim this listing or .