The public site.
At <name>.sites.amadalis.ai, or your own domain. For visitors, shoppers, search engines and AI agents: pages, posts, the shop, forms, consent, personalization, experiments, live offers, recommendations, and the files machines read.
THE PLATFORM
One admin for the whole digital experience.
Praxis is a digital experience platform built on EmDash and hosted for you on Cloudflare. EmDash's core runs unmodified at its centre. Around it we built nine rooms: a governed AI copilot, a visual designer, migration, the tools every site needs, first-party analytics, experimentation and personalization, commerce, privacy, and your account and billing. Every room has its own screens. The copilot can work each of them for you, and it stops for your approval before it publishes, deletes or changes a setting.
Already a customer? Sign in. Every figure on this page is as of October 2026.
What it does
This page is a map of the product, drawn from the admin itself. Open a room and its screens unfold in the order a site's team sees them. Every line leads to the page that explains it.
The admin, room by room.
The rail your team sees, in its own order and its own words.
EmDash's own screens
Dashboard, your content and media
EmDash's home screen with your site's figures, titled Praxis. Then one list per collection, Pages, Posts and any you add, the publication Calendar, and the Media library. On Praxis, "Add New" opens the Composer.
Comments, Menus, Redirects, Widgets, Sections, Bylines
The pieces around your content: the comment queue, menus, redirect rules with a log of missing pages, widget areas, a library of reusable sections, and author records.
Content Types, Byline Schema, Users
Your content model and the relations between types; the fields an author record carries; the site's users, with roles managed in your Praxis account.
Plugins, Registry, Import, Settings
EmDash's plugin manager and registry, its own WordPress import wizard, and Settings: General, Social, SEO, Security, Allowed email domains, API tokens, Email, Backups, Media usage and Site transfer.
Praxis's nine rooms
Copilot (always on)
Its own room, and a dock on every screen of the admin, EmDash's included: press ⌘J. Conversations · Activity · Options. Ask in plain words; it works through the same governed tools as your screens and stops at a card before it publishes, deletes or changes a setting.
Composer
The visual designer, working on the page your visitors see. The page chooser · New page · the canvas · Settings, Columns, Appearance and Structure · Scripts & events · Access · Track · "Editing for" an audience or a variation · Publish.
Migration
WordPress in, as native pages and sections. Import a live WordPress site · Import a WordPress export · Migration jobs · Review · Before and After · Inspect, with its Workflow, Cutover, Job controls, Honesty report, Scan and Native site tabs. Our engineers run every migration with you.
Site
Site setup · Navigation · Catalogs · Taxonomies · SEO · Forms · Readiness. Everything a site needs around its pages: a start from a template, the menus, the ways your content is grouped, search and AI readiness, and native forms with an inbox.
Insights
Analytics, with its Overview, Reports, Alerts, Funnels, Sources, Campaigns and Measures · Events & Capture, with its Catalog, Query parameters, Automatic capture, Needs review and Capture health · Goals · Explore, with Visitors, Content / Products, Audiences and Events · Connections.
Optimization
Experiments · Personalization, with Targeted content, Slots, Performance, Measurement and Engine · Audiences · Catalog, with Items, Values, Audiences and Suggested tags · Links · Campaigns.
Commerce
Orders · Products · Packages · Membership · Documents · Customer identity. A native store, paid into your own Stripe account.
Privacy & Data
Consent, with its "Consent policy" and "Head & CSP" tabs · Visitor Data · Exports.
Account & billing (always on)
Inside each site: "Billing" and "Support". The account itself lives at account.amadalis.ai, with its Sites, Overview, Domains, Team, AI, Security and Activity tabs.
31 rooms and screens in all: 27 inside the five grouped rooms, plus the Copilot, the Composer, Migration, and Account & billing.
Five surfaces
One product, five places to meet it.
The site admin.
At /_emdash/admin on each site. For your team: EmDash's own screens, then Praxis's nine rooms.
The copilot.
Its own room, and a dock on every admin screen. More than 370 governed tools a site's team can call on, with approval cards and undo, as of October 2026.
Your account.
At account.amadalis.ai. For account owners and their teams: sites, domains, team, AI settings, security, activity, and billing through Stripe. For agencies, every client's sites under one account.
How we run it.
Our operators' console, ours alone and never linked from this site: site health every hour, backups twice a day, incidents the system opens itself, support access under your grant or with a stated reason, every entry in a hash-linked audit trail, and a Security log of your own.
One more door is public: the migration engine at migrate.amadalis.ai, where you can explore what each way in reaches. Our engineers run every migration with you.
Depth in every room
Depth, not checkboxes.
Every room holds more than its name suggests. One fact from each, then the page that explains it.
Build · The governed copilot.
Ask for a page in a sentence. The copilot builds a draft written for what you asked, through typed tools, and stops at a card before it publishes, deletes or changes a setting. About 190 of its tools pause for a person's approval, as of October 2026.
Build · The Composer.
The canvas is the page your server renders, not a copy of it. Click a section and type. You and the copilot write through one governed path, with one history and one undo.
Build · Site.
Twenty-nine site templates, words written from your own facts, a menu builder with a live preview of your real header, an SEO workspace that drafts with AI behind your approval, and native forms with an inbox.
Measure · Analytics.
Every number is computed from your site's own database, every time, with no sampling. A visitor count can open into the people behind it, and a goal defined today also counts last month.
Optimize · Experimentation.
A plan locked before the first visitor. Holm and Benjamini-Hochberg corrections, Wilson and Newcombe intervals, a guard on the split, and three more readings of the same visitors: Bayesian, O'Brien-Fleming sequential for two-version tests, and CUPED.
Optimize · Personalization.
Each audience sees its own version of a section, or the page in a different order, decided on the server before the page is sent. A holdback proves the lift, and for visitors who allow personalization and have a visitor id, every decision records why.
Optimize · The affinity engine.
A score for each visitor against the interests you choose. Each interest fades the longer they stay away, by default halving in about five days. Explainable arithmetic, set up with our engineers.
Sell · Commerce.
Products, cart, checkout on Stripe's own page, orders and shopper accounts, paid into your own Stripe account.
Protect · Privacy and data.
Consent follows the visitor's jurisdiction: opt-in by default in the 32 countries the map names, in every country it does not name, and wherever the location is unknown; opt-out in the United States; and Global Privacy Control honoured on the server.
Move · Migration.
Our engineers move WordPress sites with our own engines into native pages and sections you can edit, and show you what moved and what did not before you switch.
Counted from the product, as of October 2026, and counted again on the day this page is published. The copilot's figure counts only the tools a site's team can use; 63 more are held by our own operators.
370+governed copilot tools a site's team can call on
40section types, and 12 elements inside layouts
72themes in 10 families, each in light and dark
29site templates: 28 kinds of business and a blank start
39built-in events, plus nine kinds of automatic capture
32countries named opt-in by default; every country not named, and every unknown location, is opt-in too
From a screen or in a sentence
Every capability, from a screen or in a sentence.
- Every room has its own screens. The copilot reaches the same capabilities through typed, governed tools, with your role's permissions. There is no second, looser route for the AI.
- When you edit in the Composer, your gestures travel the same governed path as the copilot's requests. A person and the copilot share one history and one undo.
- A few changes with a wide reach are made by asking the copilot: the site's consent policy, its bot and AI-crawler policy, and how it counts people. Their screens show them read-only, so every change to them passes through an approval card.
- Ask the copilot what it can do, and it answers from the tools actually registered for your site and your role, never from memory.
Rooms you switch on and off
Turn on what you use.
- Each site's rooms are switches: 29 of the 31, every one except the Copilot and Account & billing, as of October 2026. On your account's Sites tab, each reads "On", "Off" or "Not in plan", and "Turn off" asks you to confirm.
- Two switches decide each feature: what your plan includes and what you choose for the site. Both must be on, and a change reaches the site within a minute. Coming soon.
- A room you switch off runs nothing, and the copilot can no longer reach into it. Coming soon. Only the account's owner and its Admins can switch, and every switch is recorded.
- Hosting with the CMS and the Composer is complete on its own. Experimentation, personalization, the affinity engine, advanced analytics and commerce are features you turn on when you want them, each on its own. Coming soon.
What happens between a click and a page.
-
The address picks the site.
The request arrives on Cloudflare's network, and its hostname picks your site and your site's own database. An unknown or suspended address is refused.
-
Consent comes first.
The visitor's region sets the rules. A Global Privacy Control signal outranks the visitor's own record, which outranks the regional default.
-
The page is decided on the server.
The visitor's experiment version, any section swapped or reordered for their audience, a ticket for a live offer, and recommendations ranked for them. Members-only sections are removed from the page itself.
-
It leaves with its record.
The consent runtime, your consent-gated tags, the measurement beacon, the notice, and a record of every decision and why.
-
Nothing fails loudly.
If any step fails, the visitor simply gets your ordinary page.
Governed by design.
Approval where it matters.
Before the copilot publishes, deletes, changes a setting, your structure, your team, your consent rules or what you collect, runs an export, erases a visitor or acts on your store, a card says what will happen and waits for your click.
A gate in the platform, not in the prompt.
A tool that could publish, delete or change settings cannot even be registered without its gate. The only yes is a person's click, checked by the platform.
Undo, for real.
Most changes come back with an "Undo" you can press, or ask for in words. Before you approve, the card tells you whether the change can be undone. One-click undo on every change. Coming soon.
Everything on the record.
"Activity" lists every proposal, approval, change and undo in plain sentences, and exports to CSV or JSON.
A tamper-evident trail.
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.
Secrets stay out of the chat.
No copilot tool takes payment keys, passwords, two-factor codes or single sign-on settings. They open in your browser instead.
Common questions
What is Praxis?
A website and digital experience platform from Amadalis, built on EmDash and hosted for you on Cloudflare. One admin brings together a governed AI copilot, a visual designer, first-party analytics, experimentation, personalization, the affinity engine, consent and commerce, and our engineers move existing sites onto it.
Who is Amadalis?
Amadalis is the company, and Praxis is our platform. We are engineers and architects who have spent decades on personalization, websites, digital experience platforms, testing and recommendation engines.
Is Praxis an EmDash product, or a Cloudflare product?
Neither. Praxis is its own product, built on EmDash and running on Cloudflare.
Do I need the whole platform to host a site?
No. Hosting with the CMS and the Composer is complete on its own, and each part of the experience layer is a feature you turn on when you want it. Coming soon.
Can the AI change my live site on its own?
It cannot publish, delete or change a setting on its own: each of those stops at an approval card and waits for you, and the platform enforces that pause, with no setting to turn it off. An edit to a live experiment's version waits for your approval too.
Which parts are proven, and which are new?
Some parts are proven on production: building and publishing with the copilot, the Composer, site setup, the consent notice, analytics and the store were all seen working there in our production walks. The newest parts, such as the affinity engine, prove themselves on real visitors, and that is why the Lighthouse program exists.
Where does my data live?
Each site's content and events live in a database of its own, never in tables shared with other customers. Uploaded files are kept in Cloudflare's object storage.
How do I sign up?
Accounts open through the Lighthouse program. Apply, and if it is a fit, we email you an invitation.
Can you move my existing site?
Yes. Our engineers move it with our own migration engines, and any site is welcome, priced by its scope.
Can my developers and my own AI agents work with it?
Your developers can add events, scripts and consent-aware tags, and take your data out. AI agents can read your published content.