FOUNDATION · BUILT ON EMDASH AND CLOUDFLARE
EmDash is Cloudflare's own CMS, published under the MIT licence. Praxis runs its core unmodified, as a pinned dependency, and builds everything else around it: the platform for many sites, the experience layer and the governed copilot, on Cloudflare's network.
What EmDash gives, and what Praxis adds
The content model and its collections, with relations; the editor and the admin application; the media library; users, roles, passkeys and sessions; revisions and scheduling; the content calendar; taxonomies; menus, widgets, reusable sections and bylines; comments; redirects with a 404 log; site settings, backups and site export; the plugin system and its registry; API tokens; and its own WordPress import.
Hosting for many sites, each with its own database and routed by its address; sign-up, accounts, teams and billing through Stripe; your own domain from one record; the governed copilot and its gateway; the experience layer, from events and analytics to experiments and their statistics, audiences, personalization, consent, the affinity engine, live slots and exports; the Composer, sections, themes and site templates; native commerce and paid access; native forms, spam protection and the SEO workspace; the WordPress migration engine and its exporter; and the nine rooms of the admin.
Built on EmDash, Cloudflare's own CMS. Everything above the CMS, from the platform for many sites to the AI copilot and the experience layer, is Praxis.
Through EmDash's own doors
On Cloudflare
Every request arrives on Cloudflare's network, where our front Worker reads the hostname and sends the request to the right site. An unknown or suspended address is refused.
EmDash and Praxis render each page in Cloudflare Containers, and every decision about what a visitor sees is made there, before the page is sent.
Each visitor's live state sits in a Durable Object of its own, named by site and visitor so that no two sites ever mix. It holds the affinity engine's scores and the live channel to the page.
The channel is a WebSocket held by the visitor's Durable Object with Cloudflare's hibernation API. The server pushes, and the page listens.
Analytics Engine holds our own platform telemetry, and your analytics are counted from your site's own database.
Uploaded and migrated files and your data exports are kept in Cloudflare's object storage.
Your own domain from one record, with its certificate issued and renewed for you.
Every call the copilot makes to an AI model passes through Cloudflare's AI Gateway, authenticated, with payload logging switched off.
An optional challenge on your forms, checked on the server.
Our account service reaches its own database through Hyperdrive, and our scheduled sweeps run on Cron Triggers: site health every hour, backups twice a day, and experiment results each night.
The front Worker reads the hostname, which picks your site and your site's own database. An unknown or suspended address is refused.
Redirects run before any page is built.
The visitor's region gives the regime. A Global Privacy Control signal outranks the visitor's own record, which outranks the regional default.
An identity only where consent allows; the platform holdout and the visitor's audiences; any experiment; then the page itself, with the visitor's version, the sections arranged or swapped for their audience, a ticket for a live offer, and recommendations ranked for them. Members-only sections are removed from the page itself.
The consent runtime, your consent-gated tags, the measurement beacon, the notice, and, for visitors who allow personalization and have a visitor id, a record of every decision and why.
The notice, the beacon and your deferred tags; and, where a live offer applies, a channel to the visitor's own Durable Object, opened with a sealed ticket that must be used within 120 seconds.
Every step catches its own errors and serves the ordinary page. A newly activated test or piece of targeted content reaches visitors as the containers and the edge cache refresh.
A database for every site
No site's content or events share tables with another customer's.
An unknown or suspended hostname reaches no site at all.
Each visitor's Durable Object is named by site and visitor, so sites never share one.
Model calls pass through Cloudflare's AI Gateway with payload logging switched off.
Each script the platform puts on a served page carries a nonce made for that response alone.
In our platform's audit log, each entry is linked by a SHA-256 hash to the one before it, so editing or deleting an earlier entry breaks the chain, and the platform checks the whole log every night.
No. EmDash's core runs unmodified, as the published package, at a fixed version.
EmDash 1.4.0, as of October 2026.
No. Praxis is its own product, made by Amadalis, built on EmDash and running on Cloudflare.
On the server that renders the page, before it is sent. Cloudflare's network holds each visitor's live state and the live channel.
No. Admins can manage the installed plugins on EmDash's own Plugins screen. When the copilot changes one, it asks first, and it never grants a plugin new powers.
Praxis is a hosted platform: we run it for you, on Cloudflare.
In your site's own Postgres database, with your files in Cloudflare's object storage.
Cloudflare's edge cache holds eligible public pages. Sign-in and cart cookies, and active personalized or experiment responses, bypass it.