WordPress has launched my.WordPress.net, a browser-native WordPress environment built on the WordPress Playground technology that requires no sign-up, no hosting plan, and no domain to get started. Announced on March 11, 2026 by Automattic engineer Brandon Payton, the platform runs a complete, persistent WordPress instance entirely within the browser using a PHP interpreter compiled to WebAssembly via Emscripten. All data is stored locally and never uploaded anywhere, making sites private by default and inaccessible from the public internet. The port — which achieves 99% compatibility with the top 1,000 WordPress plugins — was years in the making under the leadership of WordPress core committer Adam Zieliński, who began the Playground project in 2022 to eliminate the friction of local WordPress development environments.
The AI Workspace feature positions a local WordPress installation as a personal knowledge base that an AI assistant can safely read from and write to. According to the announcement, users can ask the AI to modify existing plugins, generate new ones, or query data stored in their local WordPress instance. Because the environment is sandboxed in the browser, the AI can operate with broader permissions than would be prudent on a public server. Contributor Alex Kirk described the broader vision as moving WordPress from "democratizing publishing" to "democratizing digital sovereignty" — the idea being that your data stays on your own machine, and AI tools work against that local store rather than a remote service.
The platform ships with an App Catalog offering single-click, self-configuring applications designed for personal use. Two initial offerings are a Personal CRM — a private relationship manager with contact grouping, communication pattern analysis, and locally stored chat data — and a Personal RSS Reader built on the Friends Plugin, providing an algorithm-free feed experience. These apps illustrate the intended use case: WordPress as a private, extensible data environment rather than a publishing tool. The storage budget starts at roughly 100 MB, with a one-time initialization download required on first launch — costs that Zieliński's team addressed directly by cutting PHP.wasm binary sizes by 122 MB through aggressive linker-level symbol stripping, announced the same day as the my.WordPress.net launch.
Reaction from the developer community, including on Hacker News, has been mixed. Skeptics question whether WordPress's architecture is too heavyweight compared to simpler alternatives like static site generators, local desktop apps, or AI-assisted workflows built on tools like <a href="/news/2026-03-14-emacs-vim-ai-terminal-native-advantage">Claude Code</a> and Cloudflare. They also ask whether a product historically synonymous with public internet publishing can reinvent itself as a permanently private tool — and whether enough users will bother when lighter-weight options already exist. The more credible near-term use case may be among the existing WordPress developer community, who gain a zero-friction sandboxed environment for plugin development and testing — a use case Zieliński himself cited as the original motivation for the Playground project.