On April 1, 2026, Cloudflare launched EmDash—a modern, open-source CMS built on Astro 6 and TypeScript. Within the first week, we realized something: the plugin ecosystem was empty. There were only three plugins available. One of those core gaps? E-commerce. There was no way to add a store to an EmDash site.

We decided to fix that. Today, Ritely is building the first e-commerce plugin for EmDash CMS. This post explains why we’re doing it, how it works, and what it means for creators and merchants using EmDash.

What Is EmDash?

If you’re not familiar with EmDash, think of it as the WordPress equivalent for the modern web. It’s a content management system built on Astro (a modern static site generator) and TypeScript, designed for creators, agencies, and merchants who want a fast, developer-friendly alternative to traditional platforms.

Cloudflare built it as an open-source project with a plugin ecosystem. Unlike WordPress, which has thousands of plugins and a massive community, EmDash is brand new. The ecosystem is intentionally minimal. There’s no bloat, no legacy code. Just clean abstractions and room to build.

That blank slate is both a challenge and an opportunity. Someone has to build the foundational plugins first. Ecommerce is table stakes for any CMS—it’s the layer that turns content into revenue.

Why Build an E-Commerce Plugin for EmDash?

Three reasons:

First, the timing. Cloudflare launched EmDash on April 1, 2026. The community is actively looking for plugins. There are no competitors in the e-commerce space yet. Being first doesn’t guarantee success, but it’s a structural advantage. We can define what “good” looks like for e-commerce on EmDash.

Second, the philosophy alignment. EmDash’s core design is minimal and pragmatic. No bloat. Fast by default. Extensible via a clean plugin API. That’s exactly how we build products at Ritely. We don’t believe in addons, marketplace fees, or complex tiering models. One product. Multiple tiers. Done. An e-commerce plugin for EmDash should follow the same philosophy: simple, powerful, and not trying to be everything.

Third, the merchant overlap. Creators and merchants using content-driven storefronts are our core user. Content matters to them. SEO matters. Product descriptions matter. If we build an e-commerce plugin for EmDash, we can integrate Ritely’s AI capabilities directly into the plugin’s Pro tier. AI product descriptions, brand voice, bulk generation—all native to the platform. No third-party integrations. No API keys. Just value.

What’s in Ritely eCommerce?

We’re building two tiers:

Free Tier (Unlimited): Complete e-commerce foundation. Products and collections. Shopping cart. Checkout powered by Stripe. Order management. Customer accounts. Storefront components you can drop into any page. Basic analytics (views, conversion rate, average order value). Digital downloads. Email notifications. Everything a content creator or small merchant needs to sell.

The free tier is genuinely free. No limits on products, orders, or transactions. No overages. No feature gates. This tier is designed to feel complete, not crippled.

Pro Tier ($29/month): Everything in Free, plus:

We chose $29/month because it mirrors the value of the AI features. If you’re generating 100 product descriptions a month, that’s work you’re not doing manually. The math is simple. If the plugin pays for itself in time saved, it’s a no-brainer.

Why Not Addons or a Marketplace?

We considered a more complex model—plugins with addons, or a marketplace where third-party developers could build extensions. We rejected both.

Here’s why: addons and marketplaces create fragmentation. They require managing an ecosystem of developers, different quality standards, compatibility testing. They’re great for platforms with thousands of extensions (WordPress, Shopify). But for a new CMS with a small initial user base, they’re overhead you don’t need. They also introduce pricing complexity. Do you charge per addon? Per transaction? Both? That complexity is corrosive—it obscures the value proposition.

Instead, we’re doing what Ritely does best: one product, multiple tiers, ruthless focus on what matters. If there’s a feature that proves essential, we add it to Free or Pro. If there’s something niche that only a few users need, we’ll revisit it when we have the data to justify it.

This keeps the plugin simple and the pricing honest.

Building as a Solo Developer

We’re doing this in the evenings. No funding. No team. Just pragmatic, iterative development.

The EmDash plugin API is well-designed. It’s not WordPress-level complexity. You get:

Those primitives are enough to build a complete e-commerce system. We’re not fighting the framework. We’re using it.

The tradeoff is scope. We’re not building a SaaS with thousands of features. We’re building the core e-commerce experience: products, cart, checkout, orders, analytics. Everything else comes after we have merchant feedback.

The Landing Page is Already Converting

We put up a simple landing page at ritely.dev/ecommerce/ on April 2, 2026. Zero promotion. No Reddit posts, no community outreach, no press.

Within four days, we had two signups from merchants interested in the plugin.

Two signups from pure organic discovery suggests there’s genuine demand. People are using EmDash. They want to sell. They’re looking for plugins. We’re building the answer.

What’s Next?

We’re targeting a v1 release in late May 2026. Public beta before that, probably mid-May. Early adopters get to shape the product. Their feedback will tell us what features matter and which ones are nice-to-have.

In parallel, we’re building the marketing landing page and writing integration guides. We’re also documenting the plugin thoroughly—not just API docs, but tutorials on how to customize the storefront, how to optimize for SEO, how to use the analytics.

If you’re building on EmDash or considering it for a content-driven store, sign up at ritely.dev/ecommerce/. You’ll be among the first to try the plugin when it launches.

And if you’re a solo developer building plugins for EmDash, we’d love to hear what you’re working on. The ecosystem is wide open right now. There’s room for many good tools.