WordPress powers a huge part of the web, but it also comes with growing concerns around security and maintenance. According to W3Techs, WordPress is used by over 43% of all websites.

At the same time, plugin-related issues remain a major risk. A report by Patchstack found that around 96% of WordPress vulnerabilities come from plugins.

This is where Cloudflare steps in with EmDash, a new CMS built to fix these gaps using a different approach. It focuses on security, performance, and a more controlled plugin system.

In this blog, you will learn what EmDash is, why teams are preferring it over WordPress, and how to get started with EmDash.

Table of Contents

What is EmDash?

EmDash is an open-source CMS built by Cloudflare. It is designed as a modern alternative to traditional systems like WordPress.

At a basic level, EmDash helps you create and manage websites, just like WordPress. The difference is in how it works behind the scenes.

It uses a serverless model, which means your site runs only when needed. You do not have to manage servers or worry about traffic spikes. The system scales automatically based on demand.

EmDash is also built using modern tools and frameworks. This makes it more suitable for current web development practices, especially for teams working with JavaScript and TypeScript.

Another key focus is security. Plugins run in controlled environments with limited access, which reduces common risks seen in older CMS platforms.

Overall, EmDash aims to offer a faster, more secure, and scalable way to build websites without the usual overhead.

Why Cloudflare Built EmDash

Cloudflare did not build EmDash just to create another CMS. It comes from years of observing how sites break, slow down, or get exposed when running on WordPress. The goal is simple: reduce risk, cut overhead, and give developers more control without adding complexity.

• Plugin security risks: Most issues in WordPress come from plugins. Many plugins get deep access to the system, which increases the chances of attacks, data leaks, or broken functionality.
  
• High maintenance and hosting overhead: Running a WordPress site means handling updates, backups, server setup, and performance tuning. This adds ongoing effort, even for small websites.
  
• Scaling challenges during traffic spikes: Traffic spikes can slow down or crash sites if hosting is not configured well. Scaling often requires manual setup or higher hosting costs.
  
• Need for a more secure and flexible system: Modern teams want better control, cleaner architecture, and safer extensions. EmDash is built to meet these needs with a more controlled and structured approach.

Core Architecture of EmDash

EmDash is not just a redesign of a CMS. It changes how websites are built and run at a system level. The architecture focuses on control, efficiency, and safer execution.

Serverless Model

Instead of running on fixed servers, EmDash works on a serverless setup powered by Cloudflare. Your site runs only when a request comes in.

There is no need to manage uptime, patches, or server scaling. This removes a lot of operational work that usually comes with traditional CMS platforms.

Cost also changes here. You pay based on usage, not for idle infrastructure sitting in the background.

• No always-on servers
• Runs only when needed
• Handles traffic spikes automatically

Plugin Isolation

Plugins in EmDash do not get full system access. Each plugin runs in a controlled environment with clear boundaries.

This means a plugin cannot freely access your database or other parts of the system unless explicitly allowed. It limits the blast radius if something goes wrong.

Compared to WordPress, this is a big shift in how extensions are handled.

• Sandbox execution model
• Permission-based access
• Reduced risk from third-party code

Modern Tech Stack

EmDash is built using tools that many developers already use today. The backend uses TypeScript, while the frontend is powered by Astro.

It runs on Cloudflare Workers, which allows fast response times across global locations.

This setup makes development more structured and easier to maintain over time.

AI-Ready System

EmDash is designed with AI use cases in mind. It is not something added later, but part of the system from the start.

It supports automation, content generation, and agent-based workflows. This opens up use cases beyond simple content publishing.

• Built to support AI workflows
• Enables automation at different stages
• Suitable for agent-based systems and integrations

Key Features of EmDash

EmDash focuses on fixing common pain points seen in traditional systems like WordPress. Here are the key features that define how it works:

• Secure plugin system: Plugins run in isolated environments with strict permissions. They cannot access everything by default, which lowers the chances of security issues.
• Serverless deployment: No need to manage servers or hosting setups. The platform runs on demand and scales automatically without manual effort.
• Fast performance: Built on edge infrastructure by Cloudflare, sites load quickly across regions with low latency.
• Open-source (MIT license): Developers can use, modify, and extend EmDash freely without strict licensing limits.
• No central plugin marketplace: There is no single controlled store. Developers can build and distribute plugins independently, which keeps the ecosystem open.
• Built for modern web development: Uses current tools and practices like TypeScript and component-based frontend frameworks, making it easier for modern teams to work with.

EmDash vs WordPress: What Actually Changes?

Aspect	EmDash	WordPress
Hosting model	Serverless, runs on demand	Requires always-on hosting
Setup effort	Minimal infra setup	Needs server, database, configs
Plugin system	Sandbox with limited access	Full system access
Security approach	Permission-based execution	Depends on plugins and updates
Scaling	Auto scaling built-in	Manual or hosting dependent
Performance	Edge-based, low latency	Depends on hosting and caching
Cost model	Pay for usage	Fixed hosting cost
Tech stack	TypeScript, modern frameworks	PHP-based
Ease of use	More developer-focused	Beginner-friendly
Ecosystem	Very limited (early stage)	Large plugin and theme ecosystem
AI readiness	Built with AI workflows in mind	Limited native support

How to Use EmDash (Step-by-Step)

Getting started with EmDash is different from using WordPress. It follows a more developer-first setup. Here is a clear step-by-step flow.

Step 1: Set up your environment

First, make sure your system is ready.

You will need:

• Node.js installed
• A Cloudflare account
• Basic understanding of JavaScript or TypeScript

Then install the CLI tool provided by Cloudflare. This tool helps you create and manage your project from the terminal.

Step 2: Create a new EmDash project

Once the CLI is ready, create a new project.

• Run the project creation command
• Choose a project name
• Select basic configuration options

This sets up your project structure, including folders for pages, components, and configuration files.

Step 3: Connect to Cloudflare Workers

Next, link your project to Cloudflare.

• Authenticate your account from the CLI
• Bind your project to Workers
• Set up environment variables if required

This step allows your project to run on Cloudflare’s infrastructure.

Step 4: Build your frontend

EmDash uses Astro for frontend development.

Start by creating:

• Pages like home, blog, and about
• Reusable components such as headers and cards
• Layouts to keep design consistent

You write clean, structured code instead of editing directly in a UI.

Step 5: Add and manage content

Content in EmDash is structured.

• Define content types (posts, pages, etc.)
• Add entries using the system
• Keep data separate from design

This makes it easier to reuse content across pages.

Step 6: Install and configure plugins

Plugins work differently here.

• Add a plugin to your project
• Define what it can access
• Run it inside a controlled environment

This keeps your system stable even when using third-party code.

Step 7: Test your site locally

Before going live, test everything.

• Run the local development server
• Check pages, components, and content
• Fix any issues in layout or logic

This step helps avoid errors after deployment.

Step 8: Deploy your project

When ready, deploy using Cloudflare.

• Run the deploy command
• Push your project to Workers
• Your site goes live globally

There is no manual scaling or server setup required.

Step 9: Monitor and update

After deployment, keep things updated.

• Track performance and usage
• Update content or components
• Add or modify plugins as needed

Since the system is serverless, most infrastructure concerns are already handled.

Moving from WordPress to EmDash: What You Need to Know

Shifting from WordPress to EmDash is not a one-click process. The structure, plugin system, and setup are different, so migration needs a bit of planning.

Start by exporting your existing content from WordPress. This usually includes posts, pages, media, and basic metadata. You can use standard export tools to generate a file that holds your content.

Next, import this data into EmDash. Since EmDash follows a structured content model, you may need to map your WordPress content into defined types such as posts or pages. This step may require small adjustments.

Themes do not carry over. You will need to rebuild your frontend using modern tools like Astro. This gives more control, but it also takes effort.

Plugins also need attention. WordPress plugins cannot be reused directly. You either replace them with EmDash-compatible options or build custom logic based on your needs.

Keep these points in mind:

• Content can be migrated, but structure may change
• Design needs to be rebuilt from scratch
• Plugins must be replaced or recreated
• Some manual work is expected

For smaller sites, this process is manageable. For larger sites, it is better to move step by step instead of shifting everything at once.

Should You Use EmDash Today?

Choosing EmDash depends on what you need right now. It brings a fresh approach, but it is still evolving. For many users, WordPress remains the safer and more practical choice today.

You can consider EmDash if:

• You have a technical background: If you are comfortable working with code, CLI tools, and modern frameworks, EmDash gives you more control over how your site is built and managed.
• You want to experiment with a modern setup: It is a good fit for side projects, prototypes, or internal tools where you want to test a new way of building and deploying websites.
• Security and control matter to you: The plugin system is more restrictive by design, which helps reduce common risks seen in traditional CMS platforms.
• You already use Cloudflare services: If your stack is already connected with Cloudflare, getting started with EmDash becomes more straightforward.

You should avoid it for now if:

• You need a fast and simple website setup: Unlike WordPress, there are no ready-made themes or simple setup flows. Building even a basic site takes effort.
• You are not from a technical background: The workflow is not designed for beginners. It expects some level of development knowledge.
• You depend heavily on plugins: The ecosystem is still small, so you may not find ready solutions for common features.
• You are running a business-critical website: Since EmDash is still early, it is safer to rely on more stable platforms for production use.

Future of EmDash

EmDash is still early, but the direction is clear. Instead of following the path of WordPress, it focuses on fixing core issues like security, scaling, and system control.

For long-term growth, the ecosystem will matter most. WordPress grew because of its large plugin and theme network. EmDash needs similar support to attract wider adoption.

Ease of use is another key area. Right now, it suits developers more than general users. If Cloudflare improves onboarding, it can reach a broader audience.

The shift toward serverless and edge-based systems also works in its favor. If it builds strong tools, better usability, and a reliable plugin ecosystem, EmDash can become a serious option in the CMS space.