App Architecture

WebbiOS embraces an innovative App-as-Worker architecture. Rather than running a monolithic codebase where third-party plugins can crash the entire system, WebbiOS treats every app as an isolated microservice running on the edge.

App-as-Worker Model

When you build an app for WebbiOS, you are building a standalone Cloudflare Worker.

1. Isolation: Your app runs in its own V8 isolate. A memory leak or crash in your app will never take down the merchant’s Core API.
2. Speed: Apps run on Cloudflare’s global edge network, meaning they execute extremely close to the user.
3. Integration: Apps communicate with the WebbiOS Core API via HTTP requests using our @webbi/sdk.

The Installation Flow

When a merchant installs your app from the WebbiOS Marketplace:

1. The merchant’s Core API sends a license check request to the Platform Gateway (platform.webbios.dev).
2. The Platform verifies the subscription/purchase.
3. If valid, the Platform provides a secure download link to your app’s pre-compiled ZIP bundle from Cloudflare R2.
4. The merchant’s Core API automatically calls Cloudflare’s provisioning API to deploy a brand-new Worker running your code.
5. The new Worker is hooked up to the merchant’s store via Webhooks.

Data Storage

Because your app is deployed to the merchant’s Cloudflare account, you do not need to host your own database for standard app functionality! You can store your app’s specific data directly inside the merchant’s D1 Database by defining custom schemas in your app bundle.

This guarantees data localization and privacy out-of-the-box.

Development Workflow

1. Use the @webbi/cli to scaffold a new app.
2. Develop locally against a mock Core API or a staging shop.
3. Run webbi publish. The CLI bundles your app, uploads the ZIP to the WebbiOS Platform R2, and creates a new version in the Marketplace.
4. Merchants click “Update”, triggering the automated Cloudflare deployment pipeline for their specific instance.