Free application hosting
The developer-program commitment: we intend to host your Wasabe applications for free. The supported hosting services, allowances and operating terms still need definition before general availability.
Bring your web skills to a full operating system. We’re building AppKit for polished productivity tools, creative applications and SaaS alternatives — with shared OS services, native windows and optional, reviewed integration with the Wasabe agent. We plan to host your Wasabe applications for free. Join the developer preview to help shape the platform.
The invitation is for useful, polished products: creative tools, productivity apps, business software, collaboration tools and specialist applications. Premium describes quality and ambition. Free hosting does not mean every developer’s app must be free. Commercial terms, developer pricing and any revenue-sharing rules will be published as their own policy — they are not defined here.
The developer-program commitment: we intend to host your Wasabe applications for free. The supported hosting services, allowances and operating terms still need definition before general availability.
The user’s VM or installed device supplies desktop CPU, memory and storage. Free hosting does not mean a free cloud computer per user.
Backend compute, databases, storage, bandwidth, third-party APIs and AI usage need explicit coverage and terms. We do not imply unlimited provision of all of these before that offer exists.
Enrollment is a developer preview and an expression of interest until the actual onboarding and hosting service are available.
HTML, CSS, JavaScript and React are application technologies the OS supports. A native Wasabe app delivers its interface, logic and assets; the OS supplies the engine, native window and controlled system integration.
Sharing infrastructure does not mean sharing every app’s JavaScript context, credentials or mutable data. Apps keep distinct identities, isolated renderer execution and app storage.
An app may bundle a typed actions module. While that app is open, the Wasabe agent should discover the approved actions for that live instance. An app without the module remains a valid app.
A CRM could expose finding a contact or preparing a draft; a document app could expose reading a selection or applying an edit. Those are use cases, not claims that the integrations are already shipped. End-to-end conversation discovery and invocation are still pending.
Agent admission requires a valid developer signature bound to the exact package.
Wasabe review approval is bound to that same package and API. Unsigned or unreviewed apps must not access the agent channel. Updates need approval for the changed package.
Permissions and required confirmations still apply. Review establishes provenance and admission; it does not make application text immune to prompt injection.
The published app review process is not available yet, so there is no review-process link on this page.
Help shape AppKit, the agent contract and the hosting offer. We will write when onboarding is ready.