The core architectural difference
EmDash's bet is that the future of publishing is serverless and edge-native. It is MIT-licensed and built on Astro, content lives in a SQL database (Cloudflare D1, SQLite, Turso or Postgres) with media in R2 or S3-compatible storage, and plugins run in isolated sandboxes with capabilities declared up front. Cloudflare released it as a developer preview in April 2026 and it is still a beta preview. There's genuinely good thinking here — plugin sandboxing in particular is a smart answer to the plugin CVE problem that damaged WordPress's security story.
VeloCMS's bet is the opposite: that the average creator running a newsletter, paywall, and AI-assisted blog doesn't want to host, deploy, or configure a CMS. We run on Railway — traditional containers, a stateful PocketBase process, and all the platform infrastructure handled. You get a subdomain, a login, and a working blog in under a minute. Railway issues the Let's Encrypt certificate when you bring a custom domain. You never touch a wrangler.toml.
The multi-tenancy gap
This is the starkest difference on the feature list. VeloCMS was designed for multi-tenancy from day one — agencies running client blogs, SaaS founders managing reader communities for multiple products, teams that need isolated client content under one billing roof. You get tenant_id-scoped records in one PocketBase database, wildcard subdomain routing, and tenant-scoped API rules that isolate each tenant's data by design. EmDash does not document multi-tenancy, so the safe assumption is one deployment per site: ten blogs means ten deployments to configure and monitor. That's fine for a solo developer who wants full control over each site. It's not ideal for an agency billing 40 clients.
Bundled vs. pluggable commerce and newsletter
VeloCMS ships native member paywalls (Stripe BYOK, magic-link auth, HMAC-signed unsubscribe), newsletter blast, and a Resend email layer out of the box. If you want to charge readers for a premium post, that's a toggle in the post editor — no plugin install, no third-party email service to connect. EmDash keeps its core small: its README lists a TipTap editor, passkey-first authentication, a media library and search in core, with forms and SEO as first-party plugins. A reader paywall or newsletter is not among the listed core features, so expect to add a plugin or custom code. The sandboxed model is secure, but it adds friction: find the right plugin, audit it, configure it. For writers and creators who just want it to work, that's overhead they didn't sign up for.
Where EmDash genuinely wins
Edge-native latency is real — Cloudflare Workers at the edge is faster than a Railway container in a fixed region for globally distributed readers. If your audience spans five continents and milliseconds matter, EmDash's architecture has a structural advantage. Plugin sandboxing is also a legitimately better security model than VeloCMS's approach (we ship first-party plugins only and have no third-party plugin marketplace, which sidesteps the problem rather than solving it). EmDash is also open source under the MIT license, which VeloCMS is not. And for developers who want to extend a CMS with custom JavaScript running in isolation — EmDash is the better playground.