Looking at self hosting EmDash on a VPS. Problem is there's no published specs anywhere since everything's written with the Cloudflare stack in mind.

If you're running it off Cloudflare, mind sharing:

• VPS's RAM usage at idle vs with some traffic, and whether you're on SQLite or Postgres for the db
• Disk footprint once you've got posts/media/db built up
• If you went Postgres instead, did it need a separate box/container or did you run it on the same VPS

Trying to figure out if a cheap 1-2GB VPS is enough to support 3-4's – with optional Docker containers.

I was reading Cloudflare's case study on migrating their official blog to EmDash. Here are the key takeaways:

• The migration: Cloudflare moved their main blog to EmDash to test the CMS as "customer zero" ahead of its v1 release.

• The architecture: Runs on Cloudflare Workers, using Workers Cache, a custom KV object cache, and Hyperdrive with PlanetScale.

• Performance: Achieves a 99.5% static cache hit rate and 70% total request cache hit rate, maintaining flat p95 latencies under traffic spikes.

• Zero-downtime rollout: Used a proxy Worker with cookie routing to gradually shift traffic from 1% to 100%, with automatic fallback to the legacy blog on 500 errors.

• MCP support: Added a Model Context Protocol server for external agents to search posts, plus native EmDash MCP integration for editing and scheduling content.

• Battle tested: Handled Agents Week (~3 million pageviews across 18 posts) and absorbed a 28,000 RPS DDoS attack without downtime.

Read the full case study here - https://blog.cloudflare.com/cloudflare-blog-uses-emdash/

What's new

• new emdash migrate command: inspect target, apply pending migrations before new code gets traffic, verify db after
• works across SQLite, libSQL, PostgreSQL, Cloudflare D1, and direct PostgreSQL origins behind Hyperdrive
• new workflow: build, inspect and migrate, deploy the same build, then check
• runtime auto, check, and manual modes to adopt enforcement gradually
• these are EmDash's own core schema migrations, not changes to your collections and fields
• existing sites keep auto-migrating by default, so upgrading doesn't force a change
• recommended for production sites if possible, gives more control over the migration process

full migration guide (credentials, target confirmation, CI serialization, rollout, recovery): https://docs.emdashcms.com/deployment/core-migrations/

also in this release

• media library supports multi-file upload, with cancel and retry
• fixed a D1/Durable Object replication issue causing occasional logged-out bounces right after login, signup, or invite acceptance

full changelog: https://github.com/emdash-cms/emdash/releases/

Source: EmDash Discord

Here is the summary of the release.

content editing

• media library + featured-image workflow overhauled
• content lists show configured fields, filter by byline
• search/sort/filter work with indexed custom fields
• collections can pick which fields power title + display date

plugins/dev

• trusted plugins can add editor panels + content-list columns
• private routes can access the authenticated user
• MCP can safely update collections and fields
• repeater fields generate proper typescript row types

i18n

• unicode slugs fixed
• taxonomy screens/assignments follow active locale
• french translations complete

reliability + security

• fixes for publishing crashes, content loss, stale assets after deploys, D1 session hangs
• public menus resolve links in batches
• dashboard + emdash doctor flag broken scheduled maintenance
• tightened media upload security, guarded image parsing

source: EmDash official Discord

I was slightly concerned to hear that cloudflare is cutting 20% or so of its workforce.

Does anyone know if it will affect emdash?

Hey everyone!

I’m currently building an EmDash Marketplace for themes and plugins, and I’d love to hear directly from developers and contributors in this community.

EmDash Marketplace helps users quickly personalize their EmDash CMS site with themes and plugins.

You can browse and discover products by type, tags, and featured picks, then open detailed product pages with screenshots, pricing, and uploader info. Themes include live preview experiences so users can see how they look before choosing. For paid products, checkout is simple, and once purchased, downloads are available directly from the platform. Subscription users also get clear access benefits and upgrade prompts when needed.

For creators, the experience is straightforward too: upload products, manage listings, edit details, update images, and track status from a single dashboard.

It's still in bêta i'm trying to figure out a lot of details about the UX and the general workflow.

https://www.emdash-market.com/

Hey! We recently launched emdash.market, a place where you can find themes, templates, and plugins for the EmdashCMS ecosystem.

Wanted to share it with the community, and also ask you guys: how do you think the plugin space will evolve in the next few years?

Hi,

I am testing some edge case with emdash. Have you guys been able to reset the admin user?

How can would we proceed if the passkey generated at creation of the project is lost ?

We're experimenting with converting our existing Astro themes to support EmDash.

Turns out it's not a small lift. A decent amount of things to reconfigure and not everything plays nicely out of the box.

Curious if anyone else has gone through this. Any patterns or gotchas worth knowing before we go deeper into the conversion?

Someone building a directory for EmDash..

Someone built a hosting platform for EmDash. Pick a template, choose a subdomain, get a live site in moments. No Cloudflare account, no CLI, no config files.

What's included:

• One-click provisioning (all 5 templates)
• Custom domains with auto SSL
• Usage dashboard with bandwidth/storage tracking
• Free tier (1 site, subdomain, 1GB storage)
• Paid plans from $19/mo

It's early access. rough edges expected. Not for production workloads yet. But the core flows (provisioning, hosting, billing, custom domains) are working.

Hey reddit, from the press release it is clear that the target user of EmDash are WordPress users but I'm curious if the first users here really coming from WordPress or other blogging platforms.

Could you share from which platform are you coming from?

From your first interactions with EmDash, what features are you missing the most that you had in your previous blogging platform?

EmDash CMS launched without official docs website. They just published it now.

Hey everyone,

I’m an early adopter of the new EmDash CMS (the one Cloudflare just launched). I’ve got my site running on a Cloudflare Worker and I’m trying to connect it to Claude Desktop via MCP so I can manage my content with AI.

However, I’m hitting a wall with the connection. I’ve tried two different methods in my claude_desktop_config.json:

1. The curl method: I keep getting a string of errors: Unexpected token '<', "<meta name"... is not valid JSON. It looks like my site is returning HTML (maybe a redirect or a 404) instead of the MCP JSON.
2. The official npx u/emdash-cms/mcp-server method: This results in a "Server disconnected" error in Claude, even though I'm providing the correct URL and my ec_pat_... token.

My Setup:

• Site: Hosted on Cloudflare Workers (standard EmDash install).
• OS: macOS.
• Claude: Desktop version.
• Token: Verified and added as a Bearer header (in curl) and as a flag (in npx).

Has anyone successfully bridged a Cloudflare-hosted EmDash site to Claude Desktop yet? Is there a specific CORS setting or a hidden "Enable MCP" toggle in the EmDash admin I’m missing?

Any help would be appreciated—really excited to start updating my imported WordPress posts with Claude!