Orca Orchestrator Treats WebAssembly Modules as Equals to Containers

Orca, a lightweight single-binary orchestrator, is being built to run both containers and WebAssembly modules as first-class workloads using a unified configuration and reconciliation system. A shared internal Runtime trait allows the scheduler to handle containers via Docker and Wasm modules via wasmtime interchangeably, without treating either as a special case. Unlike containers, Wasm modules are typically a few hundred kilobytes in size and start in milliseconds, making them structurally cheaper for lightweight, infrequently triggered workloads such as webhooks and edge functions. The architecture is designed to eventually support true scale-to-zero behavior for Wasm functions, meaning a module consumes no memory until a request arrives, which is particularly valuable for self-hosters running many rarely-used endpoints on modest hardware. The project aims to let users run always-on containers alongside an arbitrary number of scale-to-zero Wasm functions, all managed through a single configuration file and the same proxy and TLS layer.