articles
Practical writing on Node.js and Python in the browser, package installs, isolated previews, and server execution when the workload needs it.
A practical comparison of WebContainers and Verklet for teams choosing between an in-browser Node.js runtime and a browser-first runtime with Python and server fallback.
Read articleA practical tour of the browser primitives that make a real development loop possible inside a tab.
Read articleVerklet gives agents, demos, docs, tutorials, and support tools a runtime that starts in the browser and promotes to a server when needed.
Read articleUse Vercel AI SDK tool calling with Verklet so an agent can write JavaScript, call Open-Meteo, run the code in the browser, and promote to the server only when needed.
Read articleHow browser-first runtimes change the default architecture for agent workspaces, tests, previews, and native-tool fallback.
Read articlePackage installation is where browser runtimes meet real npm behavior: lockfiles, tarballs, native packages, lifecycle scripts, and performance.
Read articleA practical checklist for adding an editable project, terminal, persistence, previews, and server fallback to documentation.
Read articleWhy Verklet starts with browser execution for Node.js-style and supported Python workloads, then promotes to a managed server when needed.
Read articleWhy embedded runtimes need previews on a product-owned isolated origin instead of the application origin.
Read article