Apps
WebAssembly Component Model
Typed components — WIT, WASI 0.3 — portable by construction. Compile from q64, Rust, Zig, and many more — any language that targets the Component Model becomes a standard component. Run it here, or take it anywhere.
Lean hosting · Capability-secured · WASM components
Sweet dreams on laser beams
Create web apps and personal agents by chatting with AI.
$ qube deploy→ https://your-app.qubepod.appWebAssembly Component Model · WASI 0.3 · q64 · Wasmtime 46 · OpenShell-compatible
Live · WebAssembly · Computational Frontend Example
Live animations, rendered in real time by our wasm engine, built by AI.
Two open standards
Bet on standards, not a proprietary runtime.
Agents
OpenShell
Bring your own agent, bring your own model. OpenShell is NVIDIA's open sandbox runtime for autonomous coding agents — OpenCode, Claude Code, Codex — running whatever model you choose, frontier or open-weight, through OpenRouter.
The differentiator
The type is the policy.
A component's WIT interface is its capability grant. What a qube imports is the exhaustive list of what it may do — enforced by the runtime, deny-by-default.
"Your app physically can't touch what you didn't grant." One type is the single source of truth: runtime effects for the app, and a sandbox policy for the agent that builds it. Author once, enforced two ways.
// everything this qube may do — its entire permission set world member-portal { import wasi:http/incoming-handler; // serve requests import qube:store/kv; // its own key–value store import qube:store/sql; // its own SQL database import qube:mail/send; // send email import qube:ai/inference; // call approved AI models }
Qube + Pod
One standard core. Any runtime, any cloud.
Qube — the portable core
A Qube is a portable WebAssembly component defined by open standards: WASM the code, WASI the runtime, WIT the typed contract. The deployable unit that runs anywhere.
Pod — the extension layer
A Pod connects a Qube to the real world: provider bindings, cloud services (KV, SQL, R2, queues), config & secrets, assets, observability. Extend without touching the core.
Write once. Package WASM components as a Qubepod. Run anywhere.
The platform
Everything a component and its agent need — on one substrate.
The loop
The workspace that builds a qube and the qube it ships are neighbours — one capability model, one bill.
Develop anywhere
OpenShell-compatible sandboxes on Mac, Windows, and Linux — or fully in the browser: on mobile, on the go, anywhere. Switching location is a resume, not a migration.
Pay for milliseconds
Dynamic Workers scale to zero; idle agents hibernate to disk and resume sub-second. Compute exists only while something runs.
Run anywhere
The Cloudflare edge, your own hosts (BYOH), or IoT devices — one enrollment, joined by a capability-brokered service mesh.
Ship to production
Run qube deploy from anywhere with our remote terminal, Qubonaut. Blue-green slots and rule-based weighted canary deployments.
Agentic by default
OpenCode in the cloud and an MCP any agent can drive: build, deploy, observe. Write → deploy → observe → fix, in one session.
For the enterprise
Customer-facing agents, secured and governed.
Secured & governed
Every action is journaled — an append-only, exactly-once audit trail. One policy model spans the sandbox and the workload. Governance as a runtime guarantee.
The context layer
MCP tools, capability-bounded state, and policy-governed egress connect agents to enterprise systems. When data must stay in the building, run the same qube on an on-prem host.
Customer-owned discovery
Customers decide what becomes discoverable from their own verified domain; agents connect through signed, typed contracts. You decide what to expose — qubepods makes it safe to publish.
Ship your first qube in minutes.
Under the hood — WebAssembly Component Model (WASI 0.2/0.3, WIT-typed capabilities), the q64 language, Wasmtime 46, V8 isolates, Dynamic Workers and web security provided by Cloudflare, OpenShell-compatible agent sandboxes, Firecracker microVMs on NixOS hosts, and micro-billing metered per request and per second.