Deploy to cloudflare workers?

[magick93]

Hello

I'm assuming that, being this is wasm, it could be deployed to a cloudflare worker?

If that is correct, are you able to give some guidance on how to do that?

Thanks

[Mohamed Mansour (mohamedmansour)]

Hello! You can use cloudflare worker in rust which is way better performance wise. WebUI has WASM as well if you want to use that which is useful for offline mode with Service Workers.

[Dotoryman (Dotoryman)]

WASM alone does not make the current WebUI bundle a Cloudflare Workers server-side bundle.

WebUI currently documents its WASM output as a browser-ready wasm-bindgen bundle. The official serverless example runs that bundle inside a browser Service Worker:

1. protocol.bin, the handler WASM, JavaScript glue and static assets are served from a CDN.
2. The browser Service Worker loads those files.
3. It fetches JSON state from an API.
4. WebUI renders and streams the HTML in the browser.

So a Cloudflare deployment can use this architecture:

• Cloudflare Pages or Workers Static Assets for the static app, protocol.bin and WebUI WASM;
• a Cloudflare Worker for /api/*.json;
• WebUI's browser Service Worker example for rendering.

That is different from importing the current WebUI WASM package into a Cloudflare Worker and doing edge SSR. I could not find a documented Cloudflare Workers adapter or Worker-targeted WebUI WASM build for that path.

The relevant examples are:

• docs/guide/integrations/wasm.md
• docs/guide/serverless-architecture.md
• examples/app/service-worker

If your goal is simply to host a WebUI application on Cloudflare, the static-assets + browser Service Worker design should fit. If the requirement is specifically to render WebUI inside the Worker isolate, that appears to need a separate integration rather than the existing browser bundle.

[Mohamed Mansour (mohamedmansour)]

Yes, Cloudflare Workers should support server-side WebUI rendering through Rust. The existing WebUI WASM package is currently packaged for browser and Service Worker usage, so it is not directly importable as a Cloudflare Worker unchanged.

The intended Cloudflare integration would use workers-rs and compile the WebUI handler to wasm32-unknown-unknown. The application would build protocol.bin ahead of deployment, load and decode it once per Worker isolate, render requests using JSON state, and serve the remaining JS, CSS, and images through Cloudflare Static Assets.

So there are two possible architectures:

1. Browser rendering using the existing WebUI Service Worker example.
2. Edge SSR inside a Cloudflare Worker using a small workers-rs host adapter.

The second option is technically viable and aligns with WebUI's protocol/handler separation, but we do not currently have a documented Cloudflare adapter or example. We should add one to make deployment turnkey. Thanks for raising this.