blog.dopana

Back

EmDash is a modern CMS built on TypeScript and Cloudflare, designed as a “spiritual successor” to WordPress. After using both, I’ve found that EmDash offers significant advantages in the AI era.

Why Consider EmDash Over WordPress?#

WordPress has dominated the web for over 20 years, but it was built for a different era - when PHP and LAMP stacks were the standard. EmDash is designed from the ground up with serverless, TypeScript, and AI agents in mind.

Quick Comparison Table#

CriteriaEmDashWordPress
LanguageTypeScript / AstroPHP
HostingCloudflare Workers (serverless)Any PHP server
DatabaseD1 (serverless SQLite)MySQL
Plugin securitySandboxed Dynamic WorkersFull server access
EcosystemBeta v0.1 (2026)20 years, 60,000+ plugins
TTFB (cached)10-30ms200-500ms
Hosting cost$0/month (free tier)$25-50/month (managed)
AI integrationBuilt-in MCP serverREST API (bolt-on)

1. Security: Plugin Security Model#

This is the most important reason I’m considering EmDash.

The WordPress Plugin Problem#

According to Patchstack, 96% of WordPress security vulnerabilities originate from plugins, not WordPress core. On average, over 333 new WordPress plugin vulnerabilities are discovered per week, and often over 200 are disclosed without a patch available at time of disclosure.

WordPress plugins run as PHP scripts on your server with the same permissions as WordPress itself. This means:

  • Direct read/write access to your entire database
  • Can read every post, user record, password hash
  • Can execute arbitrary SQL queries
  • Can read and write files on your filesystem
  • Can make outbound HTTP requests

All of this is available by default, with no permission system or isolation.

EmDash Sandboxed Plugins#

EmDash runs every plugin in an isolated sandbox called a Dynamic Worker (V8 isolate). Each plugin must declare its capabilities upfront in a manifest file, similar to how mobile apps request permissions.

WordPressEmDashEmDashAdd feature to websitePluginRun plugin in WordPressecosystemDependency + Update +CompatibilitySecurity & MaintenanceSandboxed PluginRestrict access permissionsIsolated RuntimeContain impact when plugin hasissuesDevelopment

A plugin that sends emails after content is saved must declare exactly two capabilities: read:content and email:send. It cannot:

  • Touch the database
  • Access the filesystem
  • Make network requests to any domain not explicitly declared

If a plugin is compromised, the blast radius is contained to its own sandbox. It cannot reach other plugins, your data, or your infrastructure.

[!NOTE] Cloudflare’s announcement led with security for a reason - it’s the most defensible technical argument EmDash has.

2. Basic Functionality#

Functionally, EmDash and WordPress are quite similar for basic features:

  • Content Management (CMS): Both have admin interfaces for managing content
  • SEO: Both support SEO basics (meta tags, sitemaps, structured data)
  • Blog: Both have blog functionality with posts, categories, tags
  • Media Library: Both have media management

For general content sites, both can be used equivalently.

3. Developer Experience#

WordPress Challenges#

From a developer perspective, WordPress is quite difficult to work with:

  • Large codebase: Very difficult to understand and modify existing code
  • Git integration: Version management is complex with plugins
  • Dependency management: Plugin dependencies cause conflicts
  • PHP performance: Compared to Node.js, PHP can be at a disadvantage in many cases
  • Update compatibility: WordPress updates can break old plugins
  • Legacy codebase: Understanding and fixing existing WordPress code is challenging

EmDash Advantages#

  • TypeScript: Type-safe from the start
  • Modern tooling: npm, modern build systems
  • Git-native: Version control is a first-class citizen
  • No legacy debt: Modern architecture from the start
  • Astro SSR/SSG: Better performance with modern rendering strategies

4. Infrastructure Costs#

WordPress Hosting#

For general content sites that don’t need massive traffic:

  • Server/hosting cost: $5-20/month is typical
  • Managed hosting: $25-50/month
  • Need to maintain server, PHP updates, MySQL optimization
  • Need caching layers, CDN setup

EmDash on Cloudflare#

EmDash uses Cloudflare infrastructure:

  • Free tier: Can run small sites within free tier
  • Serverless: No server to crash or patch
  • Global edge: Runs in 300+ data centers worldwide
  • Deployment: git push - Cloudflare builds and deploys automatically
  • No operating system: No OS to patch
  • No MySQL optimization: D1 handles database at the edge

Trade-off: locked into Cloudflare ecosystem. But for many sites, that’s an acceptable trade-off for cost and performance benefits.

5. AI Era Development Costs#

In the era of AI-driven development, EmDash has significant advantages:

WordPress Challenges#

  • Plugin dependency: Often have to rely on existing plugins
  • Legacy codebase: AI struggles with understanding massive WordPress codebase
  • Update issues: Plugin updates can break existing logic
  • Complex debugging: Understanding existing plugin logic is challenging

EmDash Advantages#

  • Custom development: Don’t need to rely entirely on plugins
  • Modern stack: AI works better with TypeScript/Astro codebase
  • Flexible architecture: Can build exactly what’s needed
  • Optimized solutions: Can optimize performance for specific requirements
  • No legacy debt: Starting fresh with modern patterns

6. AI Agent Content Management#

This is a major advantage of EmDash.

EmDash MCP Support#

EmDash has built-in MCP (Model Context Protocol) server, allowing AI agents to:

  • Create content directly from the CMS
  • Update content programmatically
  • Manage content via AI agents
  • New CMS usage patterns beyond traditional admin UI

WordPress AI Integration#

WordPress can integrate with AI agents, but:

  • Need to build REST API integration
  • Need custom plugins
  • Need additional infrastructure
  • Not native - bolt-on solution

[!TIP] EmDash is AI-native - MCP support is built-in from day one.

7. User Permission Management#

EmDash has a simpler, more intuitive permission system:

UserRoleSubscriberContributorAuthorEditorAdminView published contentCreate contentRequires approvalCreate, edit, publish owncontentManage team-wide contentAccess all featuresUsers / Settings / Plugins /Schema

EmDash permissions are:

  • More intuitive
  • Easier to understand
  • Simpler to configure
  • Better aligned with modern RBAC patterns

8. Backup#

WordPress backup can be complicated. You need to back up both the database and the files. Each time you update something, you need to back up again. When website bigger, 3 GB or 5 GB, you need external tools to backup your data. It take so much time to do a simple backup. This is pain point for many WordPress users.

EmDash is even simpler to back up. You can use git to back up your entire site, including uploaded files. Your database is just a single SQLite file. Each time you git commit, you have a full backup of your site. Backup is as simple as git push, restore is as simple as git checkout.

Conclusion: Why EmDash?#

I’m not attracted to EmDash just because it has “more features than WordPress.” The main reasons are:

  1. Modern Architecture: Cloudflare + TypeScript + Sandboxed Plugins + AI-native
  2. Security First: Plugin sandboxing solves the fundamental WordPress security problem
  3. Performance: Serverless edge deployment with global distribution
  4. Developer Experience: Modern tooling, type-safe, git-native
  5. Cost Effective: Can run on free tier for many use cases
  6. AI Native: Built-in MCP support for AI agents
  7. No Legacy Debt: Starting fresh with 2026 standards

EmDash is “WordPress would look like if built from scratch today” - and that’s a good thing.

References#