Skip to main content

wasmCloud

Developer Tool · Framework

Build and operate distributed WebAssembly component applications across cloud and edge infrastructure.

wasmCloud runs applications made from WebAssembly components across Kubernetes, cloud, and edge infrastructure. Each component declares the interfaces it needs. The runtime connects those interfaces to implementations chosen for the deployment, so application code can remain stable as the surrounding infrastructure changes.
Best for

Cloud-native teams that want portable WebAssembly components, capability-based interfaces, declarative deployments, and distributed execution across Kubernetes, virtual machines, bare metal, and edge devices.

Watch out for

Operators supply and run the infrastructure beneath wasmCloud. Hosts, NATS, Kubernetes where used, networking, storage, observability, security, availability, and upgrades remain their responsibility.

Provides
  • CLI Tool
  • Local Development
Interfaces
  • CLI
  • Web Dashboard
Works with
  • Datadog
  • GitHub
  • Redis

Development & Execution

Supported platform capabilities, execution environments, development technologies, deployment models, integrations, and triggers.

Runtime, language, architecture, and event availability depends on the selected deployment target.

Deployment & packaging

  • Bare metal / VM
  • Docker / OCI
  • Kubernetes
  • Local Emulator

Integrations

  • Datadog
  • GitHub
  • Redis

Triggers

  • Scheduled Invocation
  • Database Events
  • Publish-Subscribe Topics
  • HTTP Requests
  • Direct Invocation
  • Queue Messages
  • Storage Events

Target runtimes

  • WebAssembly

Target languages

  • C#
  • Go
  • JavaScript
  • Python
  • Rust
  • TypeScript

Target architectures

  • x64
  • ARM

Pricing

Published pricing structure, representative costs, and material billing factors.

Primary Billing
Plan based wasmCloud Software
Free Access
Free plan Available in public plans
Self-Hosted
Self-hosted pricing available

wasmCloud Software

Primary Pricing

wasmCloud is free Apache-2.0 software operated on user-selected infrastructure.

Self-Hosted

Free

Run wasmCloud directly on hosts or in Kubernetes environments.

  • No wasmCloud license fee
  • No first-party hosted subscription price identified
  • Infrastructure and operations billed separately

Self-Hosted Pricing

Users pay for compute, Kubernetes, networking, storage, observability, and operations; third-party commercial services are separate.

Infrastructure & Availability

Where workloads run, how deployment is scoped, and what underlying infrastructure the platform depends on.

Self-managed

wasmCloud runs on user-selected Kubernetes, virtual-machine, bare-metal, or edge infrastructure. It does not operate a proprietary geographic region network.

Deployment model

  • Self-managed

Infrastructure providers

  • Amazon Web Services
  • Microsoft Azure
  • Google Cloud Platform
  • DigitalOcean
  • Any compatible Kubernetes, virtual-machine, bare-metal, or edge infrastructure

Availability reviewed · Availability source

Security & Compliance

Security Controls

Access Control
NATS JWT/NKey authentication and policy-service authorization wasmCloud lattice; operator configures NATS accounts, credentials, and policy service
Code Signing
Cosign/OIDC component signatures Operator-configured wasmCloud policy can enforce trusted issuers during component admission
Encryption in Transit
TLS for NATS RPC and control traffic wasmCloud deployment; operator must enable and configure TLS
Secrets Management
Entity- and link-scoped secret delivery wasmCloud secrets interface; backend and root-key operation remain deployment-owner responsibilities

FAQ

Do I have to use Kubernetes with wasmCloud?
No. wasmCloud’s workload API can work with other orchestrators, so the runtime is not dependent on Kubernetes. The project focuses most maintainer effort on Kubernetes because most users deploy wasmCloud there.
Is wasmCloud free?
Yes. wasmCloud is free Apache-2.0 software that you run on your own hosts or Kubernetes environment; infrastructure and operational costs remain separate.

Explore