Earlier quoted context omitted.
The architecture is a fairly straightforward WebAssembly-native monolithic kernel. Most of the complexities come from making things work well within the browser constraints for real world, large apps. We have quite a bit of experience on the topic however, these are previous projects of ours: WebVM ( https://webvm.io ): x86 Debian shell running client-side in the browser via x86 -> WebAssembly JIT compilation Browser…
Oh, you are the author of WebVM, pretty cool! I looked at it while choosing the stack for our project and it seems very solid. Keep up the great work
WebVM uses x86 virtualization and hence has a significant performance penalty, with the upside of running any existing software without needing the source code.
BrowserPod on the other hand runs WebAssembly binaries at almost native speed. Source code is required, but that is a fair compromise in the world of sandboxing. Most language runtimes and CLI tools are FOSS anyway, and many closed-source tools (such as Claude Code) are written in scripting languages and run on top of FOSS engines.