EmDash CMS at WAYF
An Astro-native CMS with visual schema editing, generated TypeScript types, per-locale content, and built-in agent access. EmDash is in beta preview, and WAYF is evaluating it for new Astro projects.
EmDash CMS is an Astro-native content management system in beta preview. It runs inside the Astro application and gives editors a visual schema builder, while developers can generate TypeScript types from the live content model.
WAYF is evaluating EmDash for new Astro projects. We have not shipped it as a client production CMS yet, so this page describes why we are interested and what we would validate before recommending it.
Read our full EmDash CMS review and comparison with Payload.
Why EmDash has our attention
Content queries use Astro Live Collections in the same runtime as the site. EmDash also includes a scoped MCP server, so agent access goes through OAuth, tokens, permissions, and revision checks documented by the CMS.
Editors can create collections and fields in the admin. The resulting model can generate TypeScript types for the application and export to JSON as a seed. That combination could work well when editors need some control over the model and developers still want typed application code.
Where we would use it
The clearest current fit is a new Astro site with one known editorial team. EmDash keeps the CMS and frontend in one deployment, supports Cloudflare and Node hosting, and avoids adding a separate hosted content service.
What we would validate first
EmDash is young. Its public materials label it beta preview, and its current enterprise controls need project-specific review.
The documented permissions use five fixed hierarchical roles. EmDash’s documentation does not describe a first-class multitenancy feature, a public enterprise SLA, a compliance certification, or a support plan. Plugin secrets currently remain unencrypted in the database, guided JSON restore is still planned, and the Node plugin sandbox cannot enforce per-plugin CPU or memory limits.
Those gaps may be acceptable for a focused Astro publishing project. They matter for platforms with strict tenant isolation, detailed field-level permissions, contractual support, or formal recovery requirements.
We would begin with a small paid prototype using a representative content type, preview flow, authentication path, and backup and restore drill. Editors and the security team should test that implementation before the CMS decision is made.
WAYF currently treats EmDash as an available new-build option under evaluation. The requirements of the project decide whether we adopt it.
We're booking content platform
engagements for 2026.
Twenty-five minutes to walk through the work and decide if we're the right team for it. Scoping and a fixed price come after.