Meta tags:
description=Frequently asked questions about wasmCloud v2 — WebAssembly vs containers, sandboxing AI / LLM-generated code, the Component Model, Kubernetes integration, AIOps, and getting started.;

Headings (most frequently used words):

wasmcloud, does, what, and, webassembly, how, is, to, the, for, vs, kubernetes, use, with, workloads, do, v2, containers, open, source, when, or, mean, in, model, it, fit, work, are, happened, faq, positioning, security, trust, architecture, developer, experience, operations, scaling, governance, ecosystem, comparisons, frequently, searched, general, questions, migrating, from, v1, replace, should, choose, over, container, compare, docker, deny, by, default, secure, ai, llm, generated, code, suitable, running, untrusted, context, protocol, mcp, servers, component, why, languages, can, build, components, wasi, support, integrate, scale, zero, aiops, observability, relationship, between, cncf, bytecode, alliance, get, started, wasmtime, they, same, thing, knative, openfaas, serverless, not, good, have, capability, providers, wadm, still, part, of, application, abstraction, distributed, applications,

Text of the page (most frequently used words):
the (83), wasmcloud (72), and (58), for (37), with (25), webassembly (25), kubernetes (24), what (22), #component (21), does (20), #components (19), wasm (19), are (17), model (17), containers (17), workloads (16), how (15), runtime (15), capability (13), use (12), same (11), that (11), without (11), see (9), can (9), default (9), security (8), distributed (8), work (8), wasi (8), when (8), code (8), deny (8), providers (7), wasmtime (7), zero (7), mcp (7), this (7), through (7), where (7), applications (6), cncf (6), scale (6), support (6), running (6), servers (6), generated (6), container (6), operator (6), migration (6), than (6), page (5), migrating (5), fit (5), open (5), source (5), observability (5), aiops (5), architecture (5), context (5), protocol (5), workload (5), side (5), host (5), other (5), cold (5), start (5), runs (5), each (5), composition (5), language (5), community (4), happened (4), application (4), from (4), have (4), questions (4), they (4), frequently (4), get (4), started (4), between (4), bytecode (4), ecosystem (4), mean (4), untrusted (4), docker (4), over (4), more (4), you (4), api (4), native (4), capabilities (4), existing (4), guide (4), per (4), rather (4), grants (4), polyglot (4), granted (4), faq (4), 2026 (3), foundation (3), has (3), trademarks (3), maintainers (3), github (3), not (3), knative (3), openfaas (3), serverless (3), comparisons (3), alliance (3), governance (3), operations (3), languages (3), developer (3), secure (3), llm (3), trust (3), choose (3), interfaces (3), like (3), deployments (3), appropriate (3), plugin (3), service (3), external (3), specific (3), containerized (3), but (3), deployment (3), scheduling (3), any (3), your (3), environment (3), server (3), memory (3), rewriting (3), schedules (3), sub (3), millisecond (3), layer (3), under (3), must (3), makes (3), via (3), oci (3), services (3), teams (3), its (3), because (3), enabling (3), sandboxing (3), explicitly (3), linux (2), uses (2), list (2), trademark (2), usage (2), built (2), policy (2), slack (2), contributing (2), abstraction (2), still (2), part (2), wadm (2), general (2), good (2), thing (2), searched (2), relationship (2), scaling (2), integrate (2), build (2), why (2), experience (2), suitable (2), compare (2), should (2), replace (2), positioning (2), troubleshooting (2), next (2), glossary (2), networking (2), communicate (2), process (2), 000 (2), rps (2), explicit (2), comparison (2), now (2), instructions (2), designed (2), operate (2), details (2), examples (2), critical (2), long (2), step (2), who (2), implementations (2), deploying (2), most (2), while (2), edge (2), down (2), version (2), includes (2), deep (2), level (2), dependencies (2), data (2), remain (2), cost (2), exceeds (2), efficiency (2), gain (2), better (2), them (2), schedule (2), isolation (2), across (2), based (2), dominant (2), requirements (2), top (2), adding (2), distribution (2), wash (2), cli (2), quickstart (2), incubating (2), project (2), specifications (2), those (2), yes (2), opentelemetry (2), otel (2), standard (2), pipelines (2), installation (2), capacity (2), detection (2), execution (2), run (2), starts (2), true (2), economics (2), apis (2), operators (2), already (2), pods (2), cluster (2), interface (2), rust (2), python (2), typed (2), written (2), call (2), trusting (2), network (2), filesystem (2), platform (2), permissions (2), access (2), blast (2), radius (2), different (2), focuses (2), packaging (2), infrastructure (2), choice (2), right (2), asked (2), copyright, llc, all, rights, reserved, registered, please, our, https, www, linuxfoundation, org, docusaurus, swag, contact, mailing, terms, conditions, privacy, assessment, organization, youtube, linkedin, twitter, social, meeting, notes, calendar, wednesdays, previous, last, updated, eric, gregory, jul, edit, within, communication, needed, manual, serialization, deserialization, messaging, intentionally, manifest, been, replaced, which, may, include, one, placed, linked, architectural, changes, manage, acts, reconciler, giving, hosts, match, state, specified, though, way, restricted, guidance, choosing, were, processes, communicated, nats, provided, recommended, shared, performance, functionality, minimal, change, plugins, comprehensive, diagrams, info, maintainer, time, focused, prevailing, case, love, hear, folks, interested, scenarios, strongly, encourage, contributors, would, involved, real, world, found, vast, majority, users, aiming, align, smoothly, common, scenario, preserving, flexibility, variety, patterns, including, environments, exposed, orchestrator, create, solution, suits, also, stripped, only, k8s, straightforward, lightweight, approach, kernel, modules, syscalls, beyond, surface, very, large, sets, linear, caps, restrictive, 4gb, pending, wasm64, significantly, these, served, pair, don, force, functions, seconds, artifact, cloud, rebuilding, fast, engine, actually, executes, integration, embeds, standalone, embedding, own, features, walks, installing, first, seeing, serve, traffic, usually, ten, minutes, equivalent, projects, stewards, themselves, core, implements, contributes, back, licensed, apache, development, happening, publicly, commercial, managed, offerings, available, cosmonic, vendors, emits, traces, metrics, logs, natively, annotated, instrumentation, flow, into, agent, recent, releases, add, something, implement, applies, incident, response, planning, anomaly, runbook, automation, provides, agnostic, platforms, need, remediation, customer, supplied, logic, pluggable, routines, operational, overhead, tenant, times, orders, magnitude, faster, practical, torn, completely, idle, instantiated, request, user, visible, latency, event, driven, bursty, cuts, compute, spend, dramatically, compared, keeping, warm, ships, brings, registries, scheduled, ingress, observed, prometheus, mix, operating, two, control, planes, current, major, revision, system, async, streams, futures, starting, tinygo, typescript, javascript, increasingly, java, toolchains, produce, compliant, artifacts, documentation, quickstarts, specification, composing, isolated, defined, wit, types, enables, contract, either, internals, sharing, unit, preserves, guarantees, cross, modern, require, high, value, target, bridge, models, tools, category, authorization, scoping, method, least, privilege, itself, structurally, riskier, human, reviewed, volume, outpaces, review, threat, unfamiliar, sandbox, authored, cannot, reach, unless, team, vibe, coded, prototypes, generating, needs, variables, contrasts, ambient, authority, vms, inherits, parent, bounds, vulnerability, exactly, was, much, layers, together, lets, declarative, reuses, registry, replacing, following, every, escalation, bounded, stateful, complementary, technologies, solve, problems, alongside, letting, adopt, strengths, apply, startup, disrupting, their, answers, about, relates, useful, getting, specifics, roadmap, reference, recipes, templates, developing, introduction, shell, overview, search, star, 1500, docs, blog, skip, main, content,

Text of the page (random words):
faq frequently asked questions wasmcloud skip to main content wasmcloud blog community docs v2 v2 v1 0 82 star us 1500 github slack search get started what is wasmcloud installation quickstart platform overview wasm shell wash cli runtime kubernetes operator developer guide introduction developing workloads language support templates examples recipes reference glossary faq troubleshooting migration to v2 community governance contributing maintainers roadmap faq version v2 on this page faq this page answers frequently asked questions about wasmcloud how it relates to containers and kubernetes what makes it a useful runtime for sandboxing ai and model context protocol mcp servers the webassembly component model and getting started for wasmcloud v1 v2 migration specifics see the migration to v2 guide webassembly vs containers positioning does webassembly replace containers no webassembly and containers are complementary technologies that solve different problems wasmcloud is designed to run wasm components alongside containerized workloads in the same kubernetes cluster letting teams adopt wasm where its strengths apply deny by default security scale to zero startup polyglot composition without disrupting their existing container infrastructure the right architecture for most teams in 2026 runs wasm components and containers side by side when should i choose webassembly over a container webassembly is the better choice when any of the following are dominant requirements 1 deny by default capability based security where every external call must be explicitly granted 2 sub millisecond cold start enabling true scale to zero economics 3 polyglot composition across languages without trust escalation between components 4 running untrusted or ai generated code with bounded blast radius containers remain the right choice for long running stateful services workloads with deep os level dependencies and existing applications where rewriting cost exceeds the security or efficiency gain how does wasmcloud compare to docker or kubernetes wasmcloud is a cncf runtime that schedules webassembly components much as kubernetes schedules containers they operate at different layers and work together wasmcloud s runtime operator lets kubernetes schedule wasm workloads through the same declarative apis pods deployments services operators already use for containers docker focuses on container packaging and runtime wasmcloud focuses on wasm component packaging distribution via oci and runtime and reuses docker oci registry infrastructure rather than replacing it security and trust what does deny by default mean in webassembly in a deny by default model a component starts with zero permissions and must be explicitly granted each capability it needs network access filesystem access environment variables and so on this contrasts with the ambient authority model of containers and vms where code inherits the permissions of its parent process by default deny by default bounds the blast radius of any vulnerability to exactly the capabilities the component was granted how does wasmcloud secure ai and llm generated code ai generated code is structurally riskier than human reviewed code because the volume outpaces review capacity and the threat model is unfamiliar wasmcloud runs each ai generated component in a wasm sandbox with deny by default capability grants the llm authored code cannot reach the network filesystem or other components unless the platform team explicitly grants those capabilities this makes wasmcloud a foundation for sandboxing ai workloads vibe coded prototypes and model context protocol mcp servers without trusting the generating model is wasmcloud suitable for running untrusted model context protocol mcp servers yes mcp servers are a high value target for sandboxing because they bridge ai models to external tools and data a category where authorization and capability scoping are critical wasmcloud runs mcp servers as wasm components with explicit capability grants per protocol method enabling least privilege mcp server deployment without rewriting the server itself architecture and developer experience what is the webassembly component model and why does wasmcloud use it the component model is a webassembly specification for composing isolated components through typed interfaces defined in wit webassembly interface types it enables polyglot composition a component written in rust can call a component written in python through a typed contract without either side trusting the other s internals or sharing memory wasmcloud uses the component model as its native unit of work because it preserves wasm s isolation guarantees while enabling the cross language composition modern applications require what languages can i use to build wasmcloud components rust go via tinygo python typescript javascript c and increasingly java each language has webassembly toolchains that produce component model compliant artifacts the wasmcloud documentation includes language specific quickstarts what is wasi 0 3 and when does wasmcloud support it wasi 0 3 wasi p3 is the current major revision of the webassembly system interface adding native async support streams and futures to the component model wasmcloud runs on wasi 0 3 starting in 2 5 0 on top of wasmtime 46 see the runtime page for details how does wasmcloud integrate with kubernetes wasmcloud ships a runtime operator that brings wasm component workloads under kubernetes scheduling components are distributed via oci registries scheduled through standard kubernetes apis deployments services ingress and observed through the same prometheus opentelemetry pipelines operators already use for containers teams can mix wasm components and containerized pods in the same cluster without operating two control planes operations and scaling what does scale to zero mean for webassembly workloads wasm components have sub millisecond cold start times orders of magnitude faster than container cold starts this makes true scale to zero economics practical a component can be torn down completely when idle and re instantiated on the next request without user visible latency for event driven and bursty workloads scale to zero with wasm cuts compute spend dramatically compared to keeping containers warm what is aiops and how does webassembly fit aiops applies ai to it operations incident response capacity planning anomaly detection runbook automation webassembly provides the secure language agnostic execution layer that aiops platforms need to run untrusted ai generated remediation code customer supplied policy logic and pluggable detection routines without the operational overhead of per tenant containers wasmcloud is a runtime for the aiops execution layer how does wasmcloud observability work wasmcloud emits opentelemetry traces metrics and logs natively components annotated with otel instrumentation flow into standard observability pipelines without per component agent installation recent releases add wasi otel host plugin support so observability is a host capability granted to components rather than something each component must implement open source governance ecosystem is wasmcloud open source yes wasmcloud is an open source cncf incubating project licensed under apache 2 0 with development happening publicly on github commercial support and managed offerings are available from cosmonic and other vendors in the ecosystem what is the relationship between wasmcloud the cncf and the bytecode alliance wasmcloud is a cncf incubating project the runtime equivalent in the wasm ecosystem of projects like kubernetes cncf for containers the bytecode alliance stewards the webassembly specifications themselves wasm core wasi the component model wasmcloud implements those specifications and contributes back to them how do i get started with wasmcloud start with the wasmcloud quickstart it walks through installing the wash cli running a host deploying your first component and seeing it serve traffic usually in under ten minutes comparisons frequently searched wasmcloud vs wasmtime are they the same thing no wasmtime is a webassembly engine the layer that actually executes wasm bytecode wasmcloud is a runtime built on top of wasmtime adding scheduling distribution capability providers observability and kubernetes integration wasmcloud embeds wasmtime you can use wasmtime standalone for embedding wasm in your own application without wasmcloud s distributed runtime features wasmcloud vs knative or openfaas for serverless workloads knative and openfaas schedule containers as serverless functions wasmcloud schedules wasm components with the same model but cold start is sub millisecond rather than seconds capability grants are deny by default rather than container isolation and the same component artifact runs across cloud edge and kubernetes without rebuilding for each environment wasmcloud is appropriate when fast cold start polyglot composition or capability based security are dominant requirements what workloads are not a good fit for wasmcloud workloads with deep os level dependencies kernel modules os specific syscalls beyond the wasi surface workloads with very large in memory data sets wasm linear memory caps remain restrictive at 4gb per component pending wasm64 and existing applications where rewriting cost significantly exceeds the security or efficiency gain these are better served by containers pair them with wasmcloud where appropriate don t force fit general questions do i have to use kubernetes with wasmcloud v2 no the workload api exposed by the runtime can work with any orchestrator so you can choose or create the solution that suits your environment you can also use the operator with a stripped down version of kubernetes that includes only the k8s api server for a straightforward but lightweight kubernetes native approach in real world implementations wasmcloud maintainers have found that the vast majority of users are deploying wasmcloud on kubernetes for wasmcloud v2 we re aiming to align smoothly to this most common scenario while preserving flexibility for a variety of deployment patterns including distributed edge environments for now maintainer time is focused on the prevailing kubernetes use case but we d love to hear from folks who are interested in other deployment scenarios and we strongly encourage contributors who would like to work on other scheduling implementations to get involved migrating from wasmcloud v1 info for a comprehensive migration guide with architecture comparisons diagrams and step by step instructions see the migration to v2 guide what happened to capability providers in v1 capability providers were external processes that communicated over nats in v2 capabilities are provided through host plugins recommended for shared performance critical capabilities service components for workload specific long running functionality or containerized providers for minimal change migration of existing providers for details and examples see migrating capability providers for guidance on choosing between a plugin and a service see plugin or service is wadm still a part of wasmcloud v2 no the runtime operator and the kubernetes api now manage deployments the operator acts as a reconciler giving hosts the appropriate instructions to match the state specified to the kubernetes api though wasmcloud v2 is designed to operate in a kubernetes native way it is not restricted to kubernetes for more on the architectural changes see architecture comparison what happened to the application abstraction the v1 application has been replaced by the workload which may include one or more components that communicate over interfaces components in the same workload are placed on the same host and linked at runtime for a side by side manifest comparison see migrating applications to workloads how do distributed applications work in wasmcloud v2 in v2 distributed networking is intentionally more explicit components within the same workload communicate in process 30 000 rps when distributed communication is needed you ll use interfaces like wasmcloud messaging with manual serialization deserialization 5 000 rps for more context see migrating distributed networking edit this page last updated on jul 1 2026 by eric gregory previous glossary next troubleshooting webassembly vs containers positioning does webassembly replace containers when should i choose webassembly over a container how does wasmcloud compare to docker or kubernetes security and trust what does deny by default mean in webassembly how does wasmcloud secure ai and llm generated code is wasmcloud suitable for running untrusted model context protocol mcp servers architecture and developer experience what is the webassembly component model and why does wasmcloud use it what languages can i use to build wasmcloud components what is wasi 0 3 and when does wasmcloud support it how does wasmcloud integrate with kubernetes operations and scaling what does scale to zero mean for webassembly workloads what is aiops and how does webassembly fit how does wasmcloud observability work open source governance ecosystem is wasmcloud open source what is the relationship between wasmcloud the cncf and the bytecode alliance how do i get started with wasmcloud comparisons frequently searched wasmcloud vs wasmtime are they the same thing wasmcloud vs knative or openfaas for serverless workloads what workloads are not a good fit for wasmcloud general questions do i have to use kubernetes with wasmcloud v2 migrating from wasmcloud v1 what happened to capability providers is wadm still a part of wasmcloud v2 what happened to the application abstraction how do distributed applications work in wasmcloud v2 community github contributing slack calendar wasmcloud wednesdays community meeting notes maintainers social twitter linkedin youtube organization security assessment privacy policy terms and conditions contact mailing list wasmcloud swag copyright 2026 wasmcloud llc all rights reserved the linux foundation has registered trademarks and uses trademarks for a list of trademarks of the linux foundation please see our trademark usage page https www linuxfoundation org trademark usage built with docusaurus