Meta tags:
description= Glossary of wasmCloud and WebAssembly terminology: components, hosts, capabilities, providers, interfaces, the Wasm Component Model, capability-based security, deny-by-default, MCP, and AI sandboxing.;
Headings (most frequently used words):
webassembly, host, interface, capability, component, model, glossary, based, security, ambient, authority, deny, by, default, blast, radius, group, plugin, context, protocol, mcp, nats, service, ai, sandbox, vibe, coding, agentic, workloads, wash, wasm, wasmtime, module, system, wasi, type, wit, workload,
Text of the page (most frequently used words):
the (45), webassembly (37), for (29), and (28), wasmcloud (20), component (18), components (18), that (17), model (16), see (15), #interface (14), more (14), wasi (13), are (13), host (11), information (11), with (10), can (10), capability (9), code (9), wit (8), wasm (8), wash (8), interfaces (8), default (7), language (7), may (7), security (6), workload (6), wasmtime (6), workloads (6), runtime (6), community (5), nats (5), group (5), deny (5), used (5), type (4), system (4), service (4), mcp (4), level (4), documentation (4), such (4), through (4), specification (4), entities (4), many (4), glossary (4), foundation (3), trademarks (3), page (3), terms (3), agentic (3), vibe (3), sandbox (3), context (3), protocol (3), plugin (3), blast (3), radius (3), ambient (3), authority (3), from (3), define (3), high (3), defined (3), standard (3), binaries (3), process (3), you (3), core (3), using (3), which (3), run (3), given (3), binary (3), what (3), open (3), shell (3), systems (3), natural (3), examples (3), plugins (3), functionality (3), granted (3), where (3), 2026 (2), all (2), linux (2), uses (2), list (2), trademark (2), usage (2), org (2), built (2), maintainers (2), slack (2), contributing (2), github (2), module (2), coding (2), based (2), faq (2), this (2), application (2), abstraction (2), one (2), optionally (2), stands (2), apis (2), refers (2), use (2), maintained (2), sometimes (2), proposals (2), they (2), multi (2), modules (2), conforming (2), these (2), but (2), additional (2), layer (2), written (2), rust (2), shared (2), functions (2), about (2), runs (2), bytecode (2), virtual (2), set (2), serve (2), any (2), machine (2), environment (2), servers (2), source (2), tool (2), shorthand (2), cli (2), developing (2), step (2), execution (2), requirements (2), authored (2), bounds (2), stateless (2), same (2), data (2), authorization (2), contracts (2), like (2), http (2), key (2), value (2), storage (2), other (2), files (2), several (2), note (2), different (2), hosts (2), logic (2), cause (2), capabilities (2), permissions (2), explicitly (2), via (2), platform (2), reference (2), copyright, llc, rights, reserved, has, registered, please, our, https, www, linuxfoundation, docusaurus, swag, contact, mailing, conditions, privacy, policy, assessment, organization, youtube, linkedin, twitter, social, meeting, notes, calendar, wednesdays, next, inject, configuration, configmaps, secrets, previous, last, updated, liam, randall, jun, edit, consists, included, description, dev, developed, subgroup, w3c, called, move, stage, proposal, before, being, accepted, second, major, release, referred, variously, preview, units, contrasted, enables, them, meaning, example, communicate, another, types, when, talk, simply, talking, anywhere, else, interoperate, format, paired, instruction, architecture, compilation, target, developers, compile, very, small, essentially, tiny, enabling, including, browsers, edge, devices, clouds, wrapped, crate, alliance, standalone, publishing, build, view, publish, oci, registry, autonomously, plan, decide, execute, actions, response, goals, lightweight, scoped, fits, per, isolation, assistants, generate, prompts, minimal, manual, review, coded, artifacts, fit, sandboxing, isolated, generated, llm, untrusted, construction, reach, without, trusting, generating, acts, persistent, stateful, companion, connective, technology, distributed, transport, production, deployments, governed, cloud, native, computing, anthropic, connecting, models, external, tools, standardized, server, because, grants, align, directly, api, relationships, between, providers, often, defining, functionalities, vendor, agnostic, describe, provider, imports, exposed, exports, find, directory, repository, src, extend, specific, implementation, according, resources, providing, applications, consisting, layers, multiple, single, ephemeral, refer, implements, typically, enacts, important, implemented, well, services, sandboxed, interoperable, compiled, various, programming, languages, javascript, include, definitions, relate, scope, damage, vulnerability, misconfiguration, boundary, posture, starts, zero, must, each, needs, anti, pattern, inherits, its, parent, root, container, failures, explicit, alternative, access, unforgeable, tokens, rather, than, identity, checks, opposite, only, sees, was, handed, connection, over, utilized, distinct, meanings, ecosystem, entries, below, cross, project, canonical, structured, entity, dictionary, json, links, schema, reinforces, overviews, knowledge, graph, elsewhere, site, sameas, version, roadmap, governance, migration, troubleshooting, recipes, templates, support, introduction, developer, guide, kubernetes, operator, overview, quickstart, installation, get, started, search, star, 1500, docs, blog, skip, main, content,
Text of the page (random words):
glossary wasmcloud and webassembly terms 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 glossary version v2 on this page glossary wasmcloud uses several terms with distinct meanings in the context of the platform and the webassembly ecosystem many entries below cross reference the project s canonical structured data entity dictionary via json ld sameas links the schema layer reinforces the same entities ai overviews and knowledge graph see elsewhere on the site capability an abstraction for a given functionality such as key value storage or connection over http utilized by a webassembly component capability based security security model where access is granted via unforgeable tokens rather than identity checks the opposite of ambient authority code only sees the capabilities it was explicitly handed ambient authority anti pattern where code inherits the permissions of its parent process by default the root cause of many container and vm security failures webassembly s deny by default model is the explicit alternative deny by default authorization posture where code starts with zero permissions and must be explicitly granted each capability it needs blast radius the scope of damage a vulnerability or misconfiguration can cause webassembly s component boundary bounds the blast radius to the component s granted capabilities component components are sandboxed interoperable webassembly binaries that can be compiled from various programming languages such as rust go and javascript components are wasm files that include interface definitions which define the contracts through which they may relate to other entities in a wasmcloud workload we use component to refer to the binary that implements stateless logic and typically enacts the core logic of an application but it is important to note that services are implemented as wasm components as well for more information see workloads host a wasmcloud host is a process consisting of a webassembly runtime wasmtime and additional layers of security and functionality multiple hosts may run on a single machine and can be ephemeral host group a host group is a set of wasmcloud hosts host plugin host plugins extend a wasmcloud host with a specific implementation of a given capability according to an interface and may optionally serve as shared resources providing functionality to many different components for many different applications you can find several examples of host plugins in the wash runtime src plugin directory of the wash repository note that these plugins are built in by default interface interfaces are contracts that define the relationships between entities like components and providers often defining functionalities like http or key value storage at a high and vendor agnostic level interfaces describe a component or provider s requirements imports and exposed functions that may be used by other entities exports interfaces are defined in webassembly interface type wit files see the webassembly system interface wasi api proposals for examples of interfaces defined in wit model context protocol mcp anthropic s open protocol for connecting ai models to external tools and data through a standardized server interface wasmcloud is a natural sandbox runtime for mcp servers because deny by default capability grants align directly with mcp s authorization model nats nats is a connective technology for distributed systems that can be used as a transport in production wasmcloud deployments nats is governed by the cloud native computing foundation for more information see the nats documentation service in a wasmcloud workload service refers to a webassembly binary that acts as a persistent stateful companion to stateless components in the same workload for more information see workloads ai sandbox isolated execution environment for ai generated llm authored or untrusted by construction code webassembly s deny by default capability model bounds what ai authored code can reach without trusting the generating model vibe coding using ai assistants to generate code through natural language prompts with minimal manual review vibe coded artifacts are a natural fit for webassembly sandboxing agentic workloads ai systems that autonomously plan decide and execute multi step actions in response to high level goals wasmcloud s lightweight capability scoped execution model fits the per step isolation requirements of agentic systems wash wash is shorthand for wasm shell the open source cli tool for developing and publishing webassembly components using wash you can build components view component interfaces publish components to an oci registry and more for more information see wasm shell wasm wasm is shorthand for webassembly wasmtime wasmtime is an open source webassembly runtime wrapped by wasmcloud s wash runtime crate wasmtime is maintained by the bytecode alliance and may be used as a standalone tool for more information see the wasmtime documentation webassembly webassembly is a bytecode format paired with a virtual instruction set architecture that can serve as a compilation target for any language developers can compile code from a given language to a very small binary that runs on what is essentially a tiny virtual machine enabling that code to run in any environment including browsers servers edge devices clouds and more for more information see webassembly org webassembly component model the webassembly component model is a specification for webassembly binaries that enables them to interoperate meaning that a component written in one language rust for example can communicate with a component written in another language such as go using shared types and functions when we talk about components in wasmcloud we are simply talking about standard webassembly components conforming to the component model which may run anywhere else that runs components for more information on components and the component model see components or the component model documentation webassembly module webassembly modules are units of code conforming to the core webassembly specification these are sometimes contrasted with components but components are modules with an additional layer of specification to the component model for more information see the webassembly core specification webassembly system interface wasi wasi stands for webassembly system interface and refers to a group of standard apis for use by webassembly binaries wasi is developed and maintained by the wasi subgroup in the w3c webassembly community group wasi interfaces are sometimes called proposals as they move through a multi stage proposal process before being accepted as a standard you may see the second major wasi release referred to variously as wasi 0 2 wasi p2 or wasi preview 2 for more information see wasi dev webassembly interface type wit wit stands for webassembly interface type wit is an interface description language used to define the high level interfaces used by components such as the apis included in wasi in wasmcloud all interfaces are defined in wit for more information on wit see the component model documentation workload a wasmcloud workload is an application level abstraction that consists of one or more components and optionally a service for more information see workloads edit this page last updated on jun 10 2026 by liam randall previous inject configuration from configmaps and secrets next faq capability capability based security ambient authority deny by default blast radius component host host group host plugin interface model context protocol mcp nats service ai sandbox vibe coding agentic workloads wash wasm wasmtime webassembly webassembly component model webassembly module webassembly system interface wasi webassembly interface type wit workload 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
|
