Wasabe Runtime
The installed host software that runs the persistent Wasabe OS VM on an existing computer. Documented on the Wasabe OS page. Not the engine that executes your app UI.
Wasabe Runtime on the OS pageAppKit
Build a Wasabe application with web technology.
AppKit is the platform for real Wasabe applications. We’re building signed packages, isolated storage, native windows, lifecycle handling, permission-controlled services, updates, resource management and shared visual components. This page states the contracts and the current evidence — not a finished SDK.
Names that matter
Wasabe Web Runtime
The shared web engine inside the OS. The current implementation uses WPE WebKit. Fedora Chromium is a separately installed Linux application. These are implementation facts, not a consumer headline, and not a performance claim.
What “web-native” means
The OS owns the engine. The app owns its product.
What the app brings
Interface, logic and assets. Existing remote services and backend business logic can remain part of an app. AppKit does not automatically move every SaaS database or server process into the OS.
What the OS supplies
Wasabe Web Runtime — the shared, system-managed web engine — plus a native window and controlled system integration. The app does not need to boot its own container, local HTTP server or separate browser engine.
Heavy work
Media processing, indexing, large file operations, databases and GPU work belong in approved native services or workers where appropriate — not on the React UI thread by default.
Intended offering
Platform contracts we are building.
Signed packages
Intended: identity-bound packages the OS can install, update and admit. Signed packaging exists on an isolated AppKit branch; integration and release acceptance are pending.
Isolated storage
Each app keeps its own storage. Sharing the engine is not sharing credentials or mutable data.
Native windows
The OS supplies the native window. Apps must respect the reserved top bar and dock area.
Lifecycle and updates
Packaging, launch, teardown and updates are platform contracts. Broader lifecycle work remains open.
Permission-controlled services
Native operations go through the Rust System Bridge. The full permissions and resource-enforcement matrix is incomplete and is not advertised as available.
Shared visual components
AppKit is intended to include shared visual components and materials. Native liquid glass is in development; it is not a shipped effect to build against yet.
Agent API
Typed actions, reviewed before they can speak.
Optional module
An app may bundle an optional api/ module containing typed actions. /api describes a bundled module and runtime contract, not a requirement to start an HTTP server in every app.
Live instance only
While the app is open, the Wasabe agent should discover the approved actions for that specific live instance and use them in response to the user’s request.
Admission
Requires both a valid developer signature and independent Wasabe review, bound to the exact package and API. Signed declaration and review-verification foundations exist; end-to-end conversation discovery and invocation are pending.
A published development example and onboarding commands are not on this site yet. Until they are, the developer preview is the destination.
Help finish the contracts.
Join the developer preview. We will share package structure, development commands and a worked example when those materials are ready to publish.