Alex Martinez manages 12 client websites. For years, that meant 12 separate WordPress installations, 12 databases to patch, and a monthly hosting bill that kept climbing. Every site ran an average of 14 plugins. Every plugin was a potential entry point.<\/p>\n
Then Cloudflare launched EmDash. Alex decided to test whether its plugin-sandboxed, serverless architecture could handle a multi-site network without the traditional overhead. The results surprised even him.<\/p>\n
Alex\u2019s clients included a local bakery, a real estate agency, two e-commerce stores, and eight small business blogs. Each site needed different plugins. The bakery site used a contact form plugin that had been flagged for a high-severity vulnerability in early 2025. The real estate site ran a membership plugin with a known SQL injection vector.<\/p>\n
He spent roughly six hours per month on security updates alone. That\u2019s on top of the three hours for plugin compatibility checks after core updates. His hosting bill across all sites ran $480 per month on managed WordPress hosts.<\/p>\n
The math was simple: he was paying $5,760 per year in hosting and losing 108 hours annually to maintenance. For a solo freelancer, that time was better spent on new projects.<\/p>\n
Alex chose EmDash for three specific architectural reasons.<\/p>\n
Plugin sandboxing via dynamic workers.<\/strong> EmDash runs every plugin in its own V8 isolate. The plugin declares its capabilities in a manifest \u2014 read content, send email \u2014 and literally cannot touch anything else. Compare that to WordPress, where a single plugin with a bug can read the entire database. Alex estimated that 96% of his past security incidents were plugin-related, a figure that matches Cloudflare\u2019s own research.<\/p>\n Serverless scaling with D1 and R2.<\/strong> EmDash uses Cloudflare\u2019s D1 database (SQLite at the edge) and R2 storage (zero egress fees). For Alex\u2019s multi-site network, this meant each site\u2019s data lived in separate D1 databases, but all sites shared a single R2 bucket for media. No more per-site storage limits. He could spin up a new site in minutes by cloning a content type template.<\/p>\n Built-in MCP server for AI-assisted content management.<\/strong> EmDash ships with an MCP server and agent skills files. Alex pointed Cursor at his EmDash instance and asked it to \u201ccreate a new content type called \u2018Listing\u2019 for the real estate site with fields for price, address, and images.\u201d The agent generated the schema, the admin UI, and the front-end component in under two minutes. That same task in WordPress would have required installing Advanced Custom Fields, configuring it in the dashboard, and writing PHP in functions.php \u2014 roughly 45 minutes.<\/p>\n