oden is a language-neutral application runtime for WebAssembly components. odenctl is its control plane and deployment CLI. This repository contains both. The runtime embeds Wasmtime 48.0.2 and runs components built from Rust, MoonBit, or another language with compatible Component Model bindings.

The product workspaces are crates/oden and crates/odenctl. Build either independently with just oden-build or just odenctl-build; see the workspace guide for shared code and development tasks.

Documentation · Runtime quickstart · Deploy with odenctl · Rename guide

oden fills the application-runtime role of Node.js for Wasm components. It does not currently execute JavaScript/TypeScript, resolve npm packages, or implement Node.js APIs. Running a compiled component with oden does not require Node.js. The management CLI and deployment gateway require Node.js 24 or later.

Install Git, Rust/Cargo 1.95 or later, and a native linker:

git clone https://github.com/mizchi/odenctl.git
cd odenctl
bash install.sh
export PATH="$HOME/.local/bin:$PATH"
oden --version
oden run examples/minimal-command/command.wat

The WAT command exits successfully without output. oden accepts .wasm and .wat files in Component Model format directly. A bare core Wasm module must first be adapted into a component.

The installer builds this checkout. Use --prefix for another location, --with-odenctl to include the management CLI, and --force when updating an existing installation. See installation.

To start a Rust application with retained state and background tasks:

rustup target add wasm32-wasip2
oden dev examples/service-rust/app.json

From another terminal, run curl http://127.0.0.1:8080 twice. The JSON count increases while starts stays at 1. Ctrl-C drains accepted requests and stops the service. For MoonBit setup and the equivalent app, follow the quickstart.

Generate an independent app with oden init my-app --language rust or --language moonbit. Each project includes its SDK and WIT contracts. See writing services.

Resident memory is lost on restart. The standalone runtime can call celld Durable Objects through oden:durable/objects@0.1.0; that does not persist a Wasmtime instance or provision a celld fleet. See Durable Objects.

The control plane stores projects, immutable artifacts/deployments, and mutable route pointers. Runtime gateways consume route snapshots; guest requests do not need a control-plane database query. Install the management CLI with bash install.sh --with-odenctl --force, or run it from this checkout with pnpm:

pnpm install --frozen-lockfile
pnpm odenctl --help

Follow the local deployment walkthrough to start both processes, create a project, publish a standard WASI HTTP component, and request it through the gateway. odenctl dev creates a deployment preview; oden dev app.json builds and watches a local application.

The static-site example demonstrates embedded HTML/CSS/JavaScript/PNG assets, gateway caching, release updates, and rollback.

Control-plane KV, secret, and Durable Object records remain management APIs. Their removed guest bindings are not supported by the standard WASI deployment adapter. Use the runtime configuration for standalone permissions and the deployment guide for gateway limits.

• CLI and runtime configuration
• Writing services and packaging SDKs
• Component tests
• Telemetry
• Gateway response cache
• Operations and AWS deployment
• Control-plane API and operations reference
• Examples

For development setup, TDD, repository tests, and WIT/SDK changes, see the contribution guide and developer documentation.

Upgrading from wasmplane changes command names, environment variables, and custom WIT package names. Existing components using those WIT contracts must be rebuilt. Read the migration guide before upgrading a running system.