Skip to main content
Comparison

SpinKube vs wasmCloud

Compare categories, runtimes, pricing, regions, infrastructure, and platform trade-offs.

Comparison space

Updated

Comparison facts

Platform

Hosting model
Self-Hosted
Supported
Self-Hosted
Supported
Open source / license
Apache License 2.0
Open source / license
Apache License 2.0

Development & Execution

Deployment & packaging
Bare metal / VM
Not supported
Bare metal / VM
Supported
Docker / OCI
Supported
Docker / OCI
Supported
Kubernetes
Supported
Kubernetes
Supported
Local Emulator
Supported
Local Emulator
Supported
Architecture / GPU
ARM
Supported
ARM
Supported
x64
Supported
x64
Supported
Runtimes
WebAssembly
Supported
WebAssembly
Supported
Languages
C#
Supported
C#
Supported
Go
Supported
Go
Supported
JavaScript
Supported
JavaScript
Supported
Python
Supported
Python
Supported
Rust
Supported
Rust
Supported
TypeScript
Supported
TypeScript
Supported

Pricing

Billing basis
Plan based SpinKube Software
Plan based wasmCloud Software
Software charge
Users fund Kubernetes clusters, compute, networking, registries, storage, monitoring, backups, and operations.
Users pay for compute, Kubernetes, networking, storage, observability, and operations; third-party commercial services are separate.
Free entry / commitment
Free plan Available in public plans
Free plan Available in public plans

Infrastructure & Availability

Infrastructure provider
  • Amazon Web Services
  • Microsoft Azure
  • Google Cloud Platform
  • DigitalOcean
  • Any compatible self-managed or hosted Kubernetes infrastructure
  • Amazon Web Services
  • Microsoft Azure
  • Google Cloud Platform
  • DigitalOcean
  • Any compatible Kubernetes, virtual-machine, bare-metal, or edge infrastructure
Infrastructure target
  • Self-managed
  • Self-managed

Security & Compliance

Access & identity
Access Control
Unknown
NATS JWT/NKey authentication and policy-service authorization wasmCloud lattice; operator configures NATS accounts, credentials, and policy service
Encryption & secrets
Secrets Management
Kubernetes Secret references and external variable-provider bindings SpinApp configuration; secret storage and encryption remain Kubernetes or external-provider operator responsibilities
Entity- and link-scoped secret delivery wasmCloud secrets interface; backend and root-key operation remain deployment-owner responsibilities
Encryption in Transit
Unknown
TLS for NATS RPC and control traffic wasmCloud deployment; operator must enable and configure TLS