Text version of https://packages.exponential.earth/faq/coming-from-another-stack. Site index for agents: https://packages.exponential.earth/llms.txt.

Frequently asked questions

Coming from another stack to Exponential

  • 45 stacks compared
  • 6,547 extension points
  • 5 database engines
  • PHP 7.4 to 8.5
  • 0 license fees
  • 0 vendor lock-in

Who stops having these problems

The problems below are not only a developer's concern. Here is what changes for everyone who touches the site.

Visitors

  • Fast pages: static, HTTP, view and template block caches answer before PHP renders anything.
  • The same site in every language you publish, with per-language URLs.
  • Accounts protected by two-factor sign-in and security headers on every page.

Editors

  • Forms built from your own content classes, not one big text box.
  • Drafts, versions you can compare and restore, translations side by side.
  • Exponential Layouts: drag blocks into zones, preview, publish when ready.
  • Timed publishing and unpublishing, workflows and approval.

Developers

  • 6,547 extension points: datatypes, modules, operators, events, commands, overrides.
  • Templates in the native template language, Twig or Smarty.
  • 211 console commands with one output contract; REST and GraphQL APIs.
  • Composer packages with immutable releases and a changelog for every change.

System administrators

  • Apache with PHP-FPM, nginx, or the Velocity application server; no .htaccess needed.
  • One-command deploys, and upgrades with backup, dry run and rollback.
  • PHP 7.4 to 8.5, Linux or Windows, single server to cluster.

Database administrators

  • MySQL/MariaDB, PostgreSQL, SQLite, Oracle or MongoDB.
  • Schema upgrades in recorded steps, each with a dry run.
  • Standard backups of your own database; no vendor cloud in between.

Site owners

  • GNU GPL version 2 or later: no license fees, any number of sites.
  • Your content and code, on your servers or any host you choose.
  • A foundation and a maintaining company, with in-place upgrades that protect what you built.

A source for true freedom

Every stack on this page limits what you may do with your own product: how many people, languages, sites or API calls you get, which host you run on, who may support you, and when you have to upgrade. Exponential removes those limits. It is free software under the GNU GPL v2 or later, and the freedoms it gives you are the ones the industry needs to build, brand and sell real products.

Finished features, not a construction kit

Exponential ships the features common projects need, ready to use: the 629 features in the catalog below, 3,153 changelog entries in 6.0.15 alone and 6,547 extension points for whatever comes next. You configure and use them instead of designing, building, testing and maintaining them, so projects finish in hours or days, not months, or never.

No vendor lock-in

Your content sits in your own database, on servers you choose, in a format the source code documents. Leave whenever you like, take everything with you, and nobody has to agree.

Multisite and in-site editing, out of the box

One installation runs many sites, languages, portals and brands side by side, each a siteaccess with its own address, design and settings. Editors work on the live site itself: the website sidebar edits the current page, creates, moves and publishes pages, without a detour through the administration.

White-label by design

Give each site and each portal its own name, logo and colors; rebuild the whole look in a design extension without touching the core; ship your own product on Exponential. Only the GPL copyright and license notices stay, as the license requires.

Resell and build products

Agencies and partners may sell solutions, hosted services and appliances built on Exponential. You pass on the same freedoms you received; nothing else is owed.

No editions, keys or tiers

One complete product. No community edition with features held back, no license key, no activation, no revenue reporting, no per-seat, per-language, per-site or per-API-call limits.

Any host, any database, any PHP

Run on your own hardware, any hosting company or any cloud; on MySQL or MariaDB, PostgreSQL, SQLite, Oracle or MongoDB; on PHP 7.4 to 8.5.

Any vendor can support you

The source, the history and 8,817 pages of English documentation are public. Your own team, any PHP agency or 7x can maintain the site; no partner program decides who is allowed to.

Any PHP developer, productive in hours

Plain PHP, readable templates and settings files, and a documented kernel: a PHP developer becomes productive after a few hours of practice, with the guides, the documentation and AI agents, or without them. Hiring is easy, because no rare specialist is required.

Every language, in the core

156 interface translation catalogs ship with the kernel, and content translation is built into every content class. No paid translation plugin, no locale count in a price plan.

Upgrade on your schedule

Stable 6.x releases, upgrade scripts for every step, and an Exponential family that keeps older lines running. You decide when to move, not a vendor's end-of-life calendar.

Total cost of ownership: zero to marginal

The price of a CMS is not its download. It is everything you keep paying for as long as the site lives: licenses and renewals, plan tiers, forced upgrades, paid extended support, translations, hosting you cannot choose, and the cost of leaving. With Exponential almost all of those lines are zero. What is left is marginal: your hosting and your own time.

Cost you carry for the life of the site What the other stacks document With Exponential
Building the features the product lacks Months of custom development before the product does what the project needs: a separate website for every headless CMS, CMS features hand-written on every framework, plugins and modules glued together on Drupal, Joomla and WordPress Zero to marginal. The common features ship finished; you configure them, and build only what is truly unique to you.
Licenses, editions and renewals Paid editions and yearly renewals for updates (Craft CMS, October CMS, Statamic Pro, Magnolia DX Core, Sylius Plus, Laravel Nova, Adobe ColdFusion subscriptions, WPML) Zero. GPL v2 or later, one complete edition, updates for everyone.
Plan tiers: seats, locales, API calls Locales, users, roles, history and API requests counted per plan (Contentful, Storyblok, Prismic, Hygraph, Strapi, Sanity, Webflow, Directus Cloud) Zero. The software counts nothing; only your own server sets the limits.
Forced upgrades on the vendor's calendar Fixed end-of-life dates and yearly majors (Drupal, Joomla, Symfony, Laravel, Liferay, Shopware, Ibexa DXP), and cloud updates applied for you (AEM as a Cloud Service) Marginal. Stable releases, documented upgrade scripts, and older family lines kept on current PHP.
Paid extended support to stay secure Security fixes after end of life only for paying customers (TYPO3 ELTS, Drupal 7 vendors, Magnolia, Sitecore, Adobe Commerce) Zero. Fixes are public in the repository, and anyone may backport them.
Support and maintenance Support tied to the vendor or its certified partners Zero to marginal. Stable features and 8,817 pages of documentation mean most teams need no support contract; when you want one, any vendor can provide it.
Translations Paid plugins and add-ons, community packs that lag behind releases, few officially supported interface languages (WordPress with WPML or Polylang, Sitecore, Liferay, Ibexa DXP) Zero. 156 interface catalogs and content translation in the core.
Hosting choice SaaS only, or a vendor cloud with its own limits on modules, cron and repositories (Shopify, Webflow, Contentful, Acquia Cloud Next, Adobe Commerce as a Cloud Service) Marginal. Any host, five database engines, PHP 7.4 to 8.5.
Learning and hiring Proprietary platforms and frameworks that need certified or specialist developers (Sitecore, AEM, Optimizely, Liferay, Adobe Commerce) Marginal. Any PHP developer becomes productive after hours of practice, with or without guides and AI agents.
Leaving again Proprietary schemas, slow migration APIs and rebuilds of display code (Prismic Migration API, Ibexa 5 table renames, the eZ Platform rewrite) Zero lock-in. Your data in your database, exportable as packages, documented by the open source.

Licenses, tiers, renewals and lock-in: zero. Hosting and your own team's time: marginal, and under your control.

Fred Brooks, The Mythical Man-Month (1975): "Adding manpower to a late software project makes it later." The feature you never have to build is the one that cannot make your project late.

The examples come from the sourced points in the comparison cards below; each one links to its source.

Security by design: three portals, not one

Most stacks put the public site, the editing screens and the administration behind one host name and one login page. Exponential separates them. Each portal is its own siteaccess on its own address, with its own features, its own settings and its own protection.

www.example.com

Public site

  • Pages, search, accounts for visitors.
  • No editing screens and no administration in it at all.
  • Can be cached, or published as a static copy.

edit.example.com

Editor portal

  • Only content features: write, translate, schedule, lay out pages, review.
  • No setup, settings or system tools to distract editors or to be misused.
  • Behind its own password prompt before the login form.

admin.internal

Administration portal

  • Setup, roles, classes, caches, upgrades.
  • Does not have to be on the public internet at all: an internal host name, a VPN or an IP allow list.
  • When it is public, a password prompt in front of it, then the Exponential login.

7x Security Recommendation #1

Put a web server password in front of the editor and administration portals

Protect each editing and administration host with HTTP basic authentication in the web server (an htpasswd file, in the virtual host, not in .htaccess), and keep the administration off the public internet where you can. Every request is then refused before it reaches the CMS: two logins stand between the internet and the administration.

  • Bots never see a login form. Password guessing, credential stuffing and login scanners stop at the web server.
  • Flaws in admin code cannot be reached. A vulnerability in an editing or administration page needs a request that gets through; without the first password, none does.
  • Nothing to fingerprint. Scanners cannot tell which CMS, version or extensions run behind the prompt.
  • The public site stays fast and open. It has no editing or administration code to protect.

Done in production, the editing and administration code has zero exposure to the public internet: there is nothing of it left for an attacker to target, and this one measure blocks almost every attack aimed at a CMS's administration. It is how this site runs.

Why other stacks cannot simply do the same

  • WordPress serves its administration from the public host (/wp-admin, /wp-login.php). Many front-end features call /wp-admin/admin-ajax.php from public pages, so the administration cannot just be closed off or moved to a host the public never reaches.
  • Drupal and Joomla answer their login and administration paths on the same host as the site (/user/login, /admin, /administrator); separating them takes a second setup and careful configuration.
  • Framework and custom builds usually mount their admin panel inside the same application and host name, with every feature in one place for every user.
  • SaaS platforms keep the administration on the vendor's own login, on the public internet, for every customer.
  • Exponential separates the portals from the first installation on: different host names, different features, different protection.

What you get in Exponential 6.0.15

Exponential 6.0.15 alone has 3,153 changelog entries, and the product it builds on has grown for more than two decades. Below are 629 of them, area by area, each one checked against the changelog or the documentation.

Ready to build in seconds 39 features

An Exponential 6.0.15 site arrives with an installer, content classes, demo or clean content, page layouts and templates for every class and view, and the admin has wizards that write working extensions for you.

  • Install in one command ./console exp:install --apply installs the multisite package on SQLite in eng-US and prints the site and admin addresses and logins.
  • No database server needed SQLite 3 is the default database, so a complete site runs from one file. PostgreSQL, MongoDB, MariaDB, Oracle and MySQL are options.
  • Repeatable installs from one file The Kickstarter takes all setup answers from kickstart.ini, has a dry run, and installs the same site again with one command.
  • Shared-hosting friendly setup wizard The wizard needs privileges on your own database only and shows a failed connection as an ordinary message.
  • Packages pull in what they need A site package installs every package it requires first, so one choice brings its classes and content.
  • Default multisite package sevenx_multisite sets up two websites plus the administration, editor and Admin UI siteaccesses, with page layouts.
  • 33 general content classes sevenx_classes installs article, folder, image, product and 29 more classes.
  • 31 site classes and 291 demo objects The demo content package brings 31 ng content classes and 291 content objects for both sites.
  • Clean variant sevenx_multisite_clean installs the same sites with only structure, forms and legal pages (35 objects). Layout links to missing content are cleaned up for you.
  • Simple site packages sevenx_site and sevenx_site_clean install the simpler Website Interface with or without demo content.
  • 21 ready layouts The installer seeds 21 published layouts with zones, blocks and rules for the two sites.
  • CJW multisite package The cjw_multisite package and its demo content package, with class additions, layouts and a starter import, ship in the package store.
  • Translation siteaccesses created for you Each extra language chosen in the setup becomes its own siteaccess.
  • Admin UI siteaccess included A new installation gets the adminui siteaccess automatically when exp_adminui is present.
  • Every class renders in every view The generic node view dispatchers and the _with_intro fallback in sevenx_themes_media 1.5.96 mean a new class needs no template or override rule. On 2026-11-11, 1,010 of 1,010 class and view combinations rendered on five siteaccesses.
  • Every block, view type and item view renders All 404 of 404 block, view type and item view cases rendered without a template error, including the list_numbered and title default aliases.
  • Give a class its own look by adding one file Adding content/views/view/class.tpl is all a class needs. No override.ini rule is required.
  • 46 block types with templates Exponential Layouts ships 46 block definitions with standard templates for each, plus 15 site layout type templates.
  • Twelve ready content queries Blocks fill themselves from children, subtree, siblings, latest, random, relations, reverse relations, tags, search or topics.
  • One-command layouts site installer expsite_installer finds and activates the layout and site extensions, installs schema, data and binaries, regenerates autoloads and clears caches. A quick setup mode skips the data import.
  • Media demo data pack expsite_data_media applies the media demo content and its image storage on top of an existing site, without overwriting existing rows.
  • RAD catalogue of extension points Setup > RAD lists 68 extension points in seven groups, 64 of them with a code-writing tool.
  • Wizards that write working extensions The wizards generate design, template operator, handler, settings, content class, datatype, workflow event, module and kernel override extensions. Every file is shown before anything is written.
  • Module over existing tables The module wizard writes a module with views on top of existing database tables.
  • Content classes as code The content extension wizard writes a content class as a script instead of clicking it together.
  • Safe generation Wizards never overwrite an existing extension, write nothing outside the extension folder, and generated templates escape what they print.
  • Extension surface survey The survey reads what the installation exposes: settings naming classes, module views, template operators, events, overrides and replaced kernel classes.
  • Health check The health check reports settings naming missing classes, missing directories, empty design extensions, views without scripts and missing datatypes, with how to fix each.
  • New services appear by themselves A new expservices service shows up in the catalogue and in Setup > RAD with no further step.
  • Package wizard A step wizard exports content classes, content subtrees, extensions or site styles as packages, with a review step before writing.
  • Package manager on the command line ezpm creates, exports, imports and installs packages from the shell, shows progress and can export a whole content tree.
  • AI-written drafts Exponential Intelligence can write several articles under a folder from one plain-language request, as drafts for review.
  • Admin pages assembled from layouts The administration's own pages are built from admin layouts with a 3-column default, ready on install.
  • Ready-to-run starters exponential-starter, exponential-platform-nexus-starter, exponential-platform-legacy-starter and exponential-platform-dxp-starter are ready-to-run distributions with their own release tags.
  • SQLite-tuned Nexus starter The CJW Exponential Platform Nexus Starter is a ready-to-run copy tuned for SQLite, installed with git clone.
  • Platform Nexus site in minutes Nexus gives a site with demo content, the Exponential Layouts page builder, a Twig front end, an administration, a REST API and a GraphQL API after one Composer run and one install command.
  • Platform on SQLite The Exponential Platform installers can install into a single SQLite file, so a running administration is available minutes after composer install.
  • Documented DXP skeleton The DXP skeleton is created with composer create-project and comes with a guide from an empty folder to a running administration on MySQL, PostgreSQL or SQLite.
  • Portal front ends ready to point at a site The four portal designs only need content root node ids in expportal.ini to show news, shop, forums and media.
Administration portal 61 features

Exponential 6.0.15 ships a rebuilt administration with the admin4 design in light and dark, a Setup tab whose system tools work entirely in the browser, and permission-aware menus throughout.

  • admin4 design with light, dark and system modes A complete administration design in the look of the setup wizard. The header switch steps through light, dark and system, and system mode follows the operating system even while the page is open. The choice is saved with the user's account.
  • Self-contained admin4 admin4 holds every template the admin siteaccess used to take from admin3, admin2 and admin, so it runs with none of them present. A design test fails if any template is missing.
  • admin4l, an admin page assembled from layouts In admin4l, Exponential Layouts assembles the header, sidebars, main area and footer as zones of an admin layout filled with blocks. The stock layouts look exactly like admin4.
  • Responsive admin3 design admin3 is the classic admin with a sidebar that collapses, menus that work by touch and content forms that stack on phones and tablets. Every module, permission and template name stays the same as in admin.
  • Admin UI look as its own siteaccess The exp_adminui extension gives the administration the Netgen Admin UI look on its own adminui siteaccess, beside the stock admin4. Views the Admin UI never had, such as audit and cronjobs, get its frame and colors.
  • Per-user design switch Users with the uiswitch/design policy pick their administration design from the right toolbar: Admin 4 (layouts), Admin 4, Admin 3, and the older AdminUI and Classic designs, which are labeled as older. The choice applies to that user on that siteaccess only.
  • Interface language for each user A signed-in user chooses the language of the administration from the Interface box in the right toolbar, without changing siteaccess or content. The list offers every language the kernel has a locale for and shows how complete each translation is.
  • Right-to-left administration When the interface language is written right to left, such as Hebrew, Arabic, Persian or Urdu, the page sets dir=rtl, the side columns swap places and directional icons flip. Left-to-right pages stay unchanged.
  • Dashboard with key figures and a publishing chart The dashboard shows a greeting with quick actions, key-figure tiles (content items, items published in the last 7 days with a trend against the 6 days before, drafts, pending items) and a 14-day publishing chart. Show the numbers turns the chart into a table.
  • Administrator dashboard blocks Administrators also see blocks about the system, updates, security events and migrations (pending, failed, orphaned, last run). A static publishing block lists each target's stale pages, and audit events appear as a timeline.
  • Links follow permissions The dashboard, top menu and left menus show a link only to users who can open the address behind it. Access is checked against URL aliases, policy limitations, siteaccess rules and the node itself.
  • Setup overview tiles The Setup tab opens an overview of every Setup function as an icon tile, grouped into Content model, Site and URLs, Workflows, Users and messages, System, AI and Updates. A function the user may not open gets no tile.
  • Mega menus for Setup, Users and Dashboard (opt-in) Opt-in mega menus open a card under a tab with grouped links, icons and descriptions. They follow the WAI-ARIA disclosure navigation pattern for keyboard use.
  • Header search suggestions while typing The header search suggests content, pages of PDF documents, user accounts, content classes and the administration's own pages in groups as the user types. Each group shows only what the user may see, and the list ends with View all results.
  • Search page with a filter bar content/search works with a filter bar beside the results, active filters shown as chips, a sort order and a result table. The former advanced search is part of this page.
  • Content finder Setup > Content finder finds the object behind an object, node, attribute or version id, a remote id, a URL alias, a page URL or the path of a file under var/. It lists every version, location and trash entry, with confirmed actions to trash, restore, purge or remove a version.
  • System information with health checks Setup > System information leads with the server that answered, then health checks with what to do about each, and overview cards for PHP, OPcache and APCu, database, storage, caches, cronjobs, mail and locale. Copy report as text produces a masked report for support requests.
  • Siteaccess map in System information A Siteaccesses section lists every siteaccess with its kind, designs, locale, languages and an Open link. A resolution map shows the match rules in order and the rule that chose the current request.
  • Setup > Caches catalogue Every cache is listed by group with what it holds, its directory, size and file count, and when it was last cleared and by whom (from the audit trail). You can clear selected caches, a group, a tag or everything, each after an in-place confirmation.
  • Server caches on the same page The HTTP cache, query cache, SQL profile, Velocity response cache, OPcache and APCu appear as rows on Setup > Caches, with their purge and reset buttons.
  • Fast cache clears that move directories aside A cache clear renames the cache directory out of the way in one step and deletes it from there. A clear returns quickly even with hundreds of thousands of files, and files generated meanwhile are never caught by the delete.
  • INI settings page with override chains settings/view shows every setting with its effective value, the file it comes from, its default and its whole override chain. You can search across all INI files of a siteaccess, filter to changed settings and compare a file between two siteaccesses.
  • Not in effect yet detection The settings page compares the files on disk with the values the serving process runs with and lists settings still waiting for an INI cache clear. Saving clears the INI cache and says whether Velocity needs a restart.
  • Secrets masked on settings pages Values of settings named like a password, token, key, pwd or dsn are masked on the view and edit pages and never written back into a form. One shared secret rule covers the settings pages, the audit log and the system report.
  • Configuration managed by the deployment With ManagedByDeployment enabled on a siteaccess, the INI editor, the menu editors and the template editor stop writing files on the server, so configuration comes only from version control.
  • Upgrade check Setup > Upgrade check compares every file with the release checksum list and the database with the shipped schema, table by table, with the SQL to fix each difference. Results download as CSV, text or SQL.
  • Extensions page with review before apply Setup > Extensions shows each extension as a card with version, license, dependencies and real loading position. Reordering by drag and drop or arrows goes through Review changes, which lists risks before anything is written.
  • Extension downloads Any extension can be downloaded from its info card as tar.gz, zip, tar.bz2 or ezpkg. An extension that holds a secret value is not packed, and the page says which files and settings stopped it.
  • RAD tools and extension point survey Setup > RAD offers a catalogue of extension points and wizards that list every file they would write before writing an extension. The Extension point survey counts every registration, and a health check reports settings that name something that cannot load.
  • Cronjobs console Setup > Cronjobs runs a cronjob part or a single script from the browser and follows its output live, with Stop running job. Each part's shell command can be copied for a terminal.
  • Pause cronjob parts Pause, or Pause all parts, holds cronjob parts back without editing the crontab, whoever starts them. The console shows who paused what, since when and why, and the Setup tile counts paused parts.
  • Log viewer Setup > Log files lists kernel, site, extension and rotated logs with size and growth rate. A file can be followed live, searched by text or regular expression, level, time and error reference, and opened by permalink.
  • Privacy-first log reading The log viewer masks e-mail and IP addresses, passwords, tokens, session ids and cookies by default and is read-only unless actions are switched on. Every view and action is audited.
  • Separate 404 and security logs Not-found answers go to 404.log and probes or attacks to security.log with their category, so error.log keeps only real faults.
  • Audit tab and console The Audit tab offers a dashboard, a console, event details, charts, alerts and exports of a tamper-evident, hash-chained record of sign-ins, content changes, settings writes, cache clears and deploys. Exports are CSV, JSON lines or JSON, streamed or run in the background.
  • Audit alert rules Alert rules watch for brute-force sign-ins, an administrator role being granted, settings written out of hours, mass deletes, the audit being switched off and a broken chain.
  • Secret store Setup > Secrets keeps the passwords and keys that tools need, encrypted with XChaCha20-Poly1305 under a key that is not in the database. A value is written once and never shown again, and keys can be rotated.
  • Verify it's you settings page Setup > Verify it's you switches which action groups require reconfirmation (account, users, system, export, delete, content), for every siteaccess or one, and picks the user groups of the content group.
  • Data tables and connections Setup > Data tables lists every persistent class with its table, fields and keys, compares each with the database, browses rows and manages named connections to SQLite, MySQL/MariaDB, PostgreSQL, Oracle, SQL Server or MongoDB.
  • Maintenance mode button Setup > Maintenance takes the public site offline with a friendly page and a 503 status with Retry-After, and brings it back with one button or one command.
  • Preload Sites Setup > Preload Sites crawls a site in the background to warm its caches, shows progress live and ends with a broken-link report.
  • Notification status page Under Setup, the notification status page shows pending events, digest items, subscriptions, recent runs and problems. Run now and a dry-run preview run as background jobs.
  • Packages pages Setup > Packages shows every repository with figures, a card per package with its dependencies, and confirmed removal that explains exactly what goes. Uploads are checked against path traversal before anything is written.
  • URL map import and export screens content/urlimport imports a URL map uploaded or pasted (CSV, JSON, xlsx, ods, Apache or nginx rules). A row-by-row preview with state filters comes before a dry run, and the whole import can be taken back.
  • Template editor for overrides Design > Template Editor creates, orders by priority, changes and removes template override rules and edits the template files, without touching INI files.
  • Class editor move to top or bottom Each class attribute has move to top and move to bottom buttons beside its arrows. The row moves at once and is put back with a message if the server does not store the move.
  • Content checks contentcheck lists unreferenced assets below a node, broken relations to deleted, trashed, hidden or unpublished content, and storage files that no content uses. Unreferenced assets can be moved to the trash after a confirmation.
  • Migrations in the administration Setup > Migrations lists migrations and their runs, starts a run or rollback in the background and shows each run's log. Remotes and staged deploys can be managed from the same page.
  • Static publishing from Setup Setup > Static publishing publishes a static copy of a site to GitHub Pages or another git host. A wizard sets up the target, the build runs in the background, changes are checked before Publish, and every publish is kept so you can go back.
  • Environment badge admin4 and admin4l can name the environment (development, test, staging, production) in a colored pill in the header, on the sign-in page and before the page title, so a live site is not mistaken for a test copy.
  • Installation name in page titles The installation name appears in front of the page title on every installation that is not production, so staging and production tabs are easy to tell apart.
  • Site menu in the header The globe button lists the installation's other sites the user may log in to, with their addresses.
  • Paged lists with configurable page sizes Every long list in the administration is paged, with sizes set per module/view in admininterface.ini [PaginationSettings], so installations with thousands of roles or locations still draw their pages.
  • Hidden admin tabs HiddenTabs[] in menu.ini and admininterface.ini removes a tab from the top menu or the node view on one siteaccess, including tabs that extensions add.
  • Resizable left column The left menu has Small, Medium and Large presets plus a drag handle (mouse, touch, pen or arrow keys). The width is saved with the account.
  • Content tree from the top node The content structure tree starts at the virtual top node, so Users, Media, Setup and Design are reachable from it.
  • WCAG-minded accessibility in admin4 admin4 has keyboard-operable WAI-ARIA tabs, menus and tree, a skip link, named form fields, focus indicators, contrast checks, support for forced colors and reduced motion, and 24 px minimum targets.
  • Content Security Policy for the administration The administration runs without inline scripts, inline handlers or inline styles, and its Content Security Policy can be enforced, with reports written to a log of their own.
  • Clear form-expired page A form refused for a missing or wrong form token shows a plain-language page saying that nothing was saved and how to resend, instead of a 500 error.
  • Repair from the browser When the Composer libraries are missing, a one-time repair key lets an administrator repair the installation from any page, watching three steps with progress and log output.
  • Demo mode banner With EXP_DEMO_MODE=1, every administration page carries a Demo mode banner, and administrator passwords cannot be changed or reset.
Editor portal 45 features

New installations include a separate Editor siteaccess and a ready-made Editor role, so writers get the content tools they need while site administration stays out of their way.

  • Separate Editor siteaccess The setup wizard installs three siteaccesses: site, admin and editor. The Editor gets its own address, by default edit.yourdomain.com, a path such as /editor, or a port.
  • Content tabs only The Editor shows only Dashboard, Content structure, Media, Users, Store, Tags and Newsletter. It has no developer toolbar and no Layouts node tab.
  • Administration modules closed off In the Editor, setup, class, role, section, state, workflow, trigger, package, rss, audit, oauthadmin, git_manager and the layouts editor modules answer 404, so site administration stays in the admin.
  • Editor design with fallbacks The editor design falls back to admin4l, then admin4, admin3, admin2 and admin. Templates are added only where the Editor must look different.
  • Editor role in plain words An account in the Editors group gets four roles: Editor, Member, Member management and Editor account requests. The help explains each permission in plain words.
  • Everyday editing permissions Editors can create, edit, translate and publish, manage locations, hide and reveal, trash and restore, compare and read old versions, and see reverse relations. All of this is limited to the Content and Media trees.
  • What stays with administrators Emptying the trash for everyone, languages, URL aliases, content jobs, setup, classes, roles, sections, workflows, object states, the layouts editor and updates stay with administrators. Editors who open these get Access denied.
  • Keeping the Editor role complete addeditorpolicies.php lists what the Editor role lacks and warns about permissions it should not have, adding them only with --apply.
  • Editor dashboard The Editor opens on a dashboard with a greeting, buttons for Content structure and the Media library, the editor's own figures and the latest content.
  • Edit form with field bar and required marks The edit form has a field bar with one jump button per field, a red asterisk on required fields, and an error summary at the top that links to each failed field.
  • Automatic draft saving While an editor works, the edit form saves the draft by itself every few minutes, so a closed tab costs little.
  • Edit conflict page When drafts already exist, Possible edit conflict lists them with creator and time. The editor can continue an own draft or start a New draft that opens directly.
  • Rich text editor choice Rich text fields can use TinyMCE 8 or Tiptap, switchable under the field without losing what was typed. TinyMCE 8 writes the same stored XML as TinyMCE 3.
  • Writing assistant Where Exponential Intelligence is switched on, text fields offer Write, Rewrite, Translate, Suggest and Improve. Nothing changes until the editor accepts a suggestion.
  • Image editor in the browser Edit image crops, rotates, flips and resizes, adjusts brightness and contrast, applies filters, pixelates or blurs regions and adds watermarks, with undo and redo. SVG images get a drawing toolbar.
  • Reuse an existing image An image field offers Choose an existing image: browse the tree or search by name, and the file is copied into the field as if it had been uploaded.
  • SVG images sanitized on upload Image fields accept SVG and SVGZ files. An allow-list sanitizer strips scripts, event attributes and external references before the file is stored.
  • Upload many files at once The Upload button in the node view and Upload files on the dashboard open the multi-upload page. It shows the target location's path, has a location picker and quick buttons for Websites and Media.
  • Preview at device widths The version preview shows a draft at iPhone, iPad, Desktop or Large Desktop size, with a landscape switch. The chosen device is remembered for the user.
  • Preview in other view modes content/versionview can render a draft in configured view modes such as print, so approvers see how it will look printed or exported.
  • Versions page with compare Manage versions shows figures, filters by status, translation and creator, and a card per version. A two-picker panel or a per-card Compare button shows inline and block differences, and Make a new draft restores an older version.
  • Safe version access The versions page compares, copies and links only versions whose content the user may read. A disabled action explains why.
  • My drafts My drafts shows figures, search, filters by translation, class and age, and Remove old drafts. It can remove only the user's own drafts.
  • My pending items My pending items lists the user's pending versions and those waiting for the user's approval, with the approval state, approvers and workflow.
  • Publish without notification Where it is enabled, an editor can publish a typo fix with Publish without notification, so subscribers are not e-mailed about it.
  • Preview links for outside reviewers A signed, expiring and revocable link shows one draft version in one language to someone without an account. It stops working once the draft is published or discarded.
  • Review hold A page can be held for review as an object state. Until a reviewer releases it, role policies refuse editing and publishing, while visitors keep seeing the published page.
  • Recent content moderation Dashboard > Recent content lists the newest created and modified objects with status, held state, publication and scheduled date. Moderators act on a selection: hold, release, hide, reveal, trash, delete, assign section or state.
  • Large operations as background jobs Removing, copying, moving, hiding or assigning sections across big subtrees can run as a resumable content job. From 50 nodes the job is offered first.
  • Reverse relation check Before removing or hiding content, the confirmation lists the objects that embed, link to or relate to it. Removal can be set to warn or to block.
  • Sub-items table options Each user can choose, reorder and save columns from 129 registered columns plus every class attribute, apply presets, set the page size and export the visible columns as CSV.
  • Drag-and-drop ordering of sub items Where a node sorts by priority, rows of the sub-items table can be dragged with mouse, touch, pen or keyboard, and the order is saved as priorities.
  • Bulk actions on sub items Selected items can be edited in one form, removed, moved, copied with their subtrees, hidden, unhidden or given another location.
  • Translation state badges Language badges show by shape whether a language is the main language, a translation, missing, or outdated against the main language. The state is also in the accessible name.
  • Visibility and account status marks Shape-coded marks show visible, hidden and hidden-by-parent nodes, and disabled or locked accounts, in the node view, sub items, tree and browse list.
  • Section assignment scopes When assigning a section, the editor chooses the whole subtree, only the branches that inherited the old section, or the object alone.
  • Trash shows who and where The trash shows who trashed each item, from which interface, and whether the original parent still exists. It can be filtered by user, class and date range.
  • Bookmark folders Bookmarks are organized in folders of any depth, available in the sidebar, the browse dialog and the online editor. My bookmarks supports search, five sort orders and drag-and-drop arranging.
  • Bookmarks of system pages Bookmark this page saves any module view, including a search, with its parameters and a name. A bookmarked page the user can no longer open is greyed out with the reason.
  • Member management by editors Editors create, edit, enable, disable, move and remove accounts inside the Members group. Accounts of administrators and other editors stay out of reach, and every action is recorded.
  • Requesting a colleague's account Editors can create a new editor account, which waits unpublished until an administrator approves it.
  • Built-in help center The Help button opens the help page for the current view. The help dashboard has search and topics for each audience, and the exphelp/read policy controls who may read it.
  • Keyboard shortcuts Press / or Ctrl+/ to jump to search, use the arrow keys through suggestions and Esc to close menus. The tree, tabs, sub items and left column width all work from the keyboard.
  • Phone-friendly menu On a phone, the admin4 menu opens as a panel that fits the screen, with the search first and the tabs as a grid of 44 px tiles.
  • Two-step sign-in by default New installations require two-step sign-in for the Editors and Administrator users groups, with TOTP as the default method and 10 recovery codes.
User and in-page editing tools 49 features

Signed-in people manage their account, security, e-mail and bookmarks on their own pages, and editors work on the live site through the website sidebar.

  • My account My account shows login, e-mail, groups, roles and last sign-in, with cards for Profile, Password, Account settings, Two-step sign-in, API keys, Bookmarks, Notifications and E-mail preferences.
  • Profile links on the public site On the public site, the User profile page links to e-mail preferences, two-step sign-in, drafts, pending items and notification settings.
  • Self-service password change user/password on the admin and the public site shows requirements and checks them live, generates strong passwords, and confirms the change by e-mail.
  • Two-step sign-in setup page user2fa/setup turns on an authenticator app by QR code or key, or e-mail codes. Nothing changes until a correct code is entered.
  • Passkeys page My account > Passkeys adds, names, renames and removes passkeys for signing in without a password.
  • Your devices page Users see where they are signed in, sign out one session or all others, and choose whether to get New sign-in mails.
  • Security activity page Users review their own security events, confirm or flag them, and secure the account in one step.
  • Account pages follow the site's light or dark mode Your devices and Security activity follow a site design's own light and dark switch.
  • E-mail preferences page One page, also reachable without login by a personal link, turns each optional kind of e-mail on or off, sets frequency, stops all optional mail and shows the history of choices.
  • Off until you opt in Optional e-mail stays off until the person turns it on. Newsletters, offers and new e-mail addresses use double opt-in.
  • One-click unsubscribe Every optional mail ends with why it was sent and an Unsubscribe link that works in one click, including the mail program's own unsubscribe button through RFC 8058 headers.
  • Download your e-mail data Choices and every change to them can be downloaded as JSON or CSV.
  • My notification settings An overview of followed items with path, class and last change, a choice of at once, daily, weekly or monthly digests, and confirmed adding and removing.
  • Unified HTML mail layout Every mail is HTML with a plain-text part in one shared layout with a single clear button and its address as text below it.
  • Bookmarks everywhere Bookmark folders and system-page bookmarks are available in the Bookmarks box, My bookmarks, the browse dialog and the online editor's Bookmarks tab.
  • Choose your rich text engine Each user can switch between TinyMCE 3 and TinyMCE 8 on /ezoe/engine or through a user preference, without changing site settings.
  • Registration with optional e-mail choices Sign Up lets visitors tick only the optional e-mail they want, and the result page names the account's state and the next steps.
  • Website sidebar (expwt) A slim tab at the edge of the site's own pages opens a panel for editing the current page, creating pages, moving them and managing the account, without going to the administration. It replaces the ezwt toolbar.
  • Dock to any edge The sidebar docks to the left, right, top or bottom edge by drag or keyboard, resizes, and remembers place, size and mode on the server across devices.
  • Sidebar keyboard shortcuts Alt+Shift shortcuts open the sidebar, save the draft, toggle on-page editing, show a cheat sheet and jump to panels 1 to 9. Users can rebind the letters with conflict checks.
  • Page panel Edit the page's fields as a draft, save, preview, open the full editor, publish now or at a date, take down at a date, or discard.
  • Edit on the page Click a title or text on the live page and type. The panel's form follows, and hovering a field in the panel outlines it on the page.
  • Publish at and take down at Scheduling uses the kernel's own Wait until date workflow and hide dates, so the sidebar adds no separate scheduler.
  • Calendar panel A month view of scheduled publications, take-downs and layout variants for the page, its subtree or the whole site. Moving an item reschedules it, and each move is audited.
  • Focal point and crop Set an image's focal point and crop box on the image and preview every image alias live before saving to the draft.
  • Device preview side by side The draft or published page appears in frames for phones, a tablet, a desktop and 1920 wide at 200% zoom, plus up to four custom widths, each frame in light or dark.
  • Two editors on one page The first editor holds a soft lock that others may take over. Changes merge field by field, and the second editor chooses per field when both changed the same one.
  • Nothing typed is lost The sidebar autosaves to the draft every few seconds and keeps a local browser copy for two weeks, offering Restore after a crash or lost connection.
  • Create panel Create a new page below or beside the current one from the classes you may create there.
  • Structure panel Hide, reveal, move, add a location, move to the trash, and sort child pages by dragging or with buttons.
  • Comments moderated in place The page's comments appear below its fields and can be hidden or removed according to the kernel's policies.
  • SEO panel Checks the rendered page's title and description length, heading structure, image alternative texts, canonical address and robots settings, and whether internal links resolve.
  • Accessibility check (WCAG 2.2 AA) On demand, axe-core checks the rendered page in the browser. Findings come ranked by impact and are linked to the field, layout block or template.
  • Sites and URLs panels See the page on other sites and languages of the installation, and manage its addresses, old redirecting addresses, aliases and wildcards.
  • Forms and Newsletter panels See the page's forms with their submission counts, and where cjw_newsletter is active, make a newsletter edition from the page.
  • Export panel Print or save the page as a PDF with a print layout, export its fields as Markdown or Word, and create signed, expiring share links to a draft that can be withdrawn.
  • Insights panel Page views, on-site searches for the page's words and related figures, taken from the kernel's own statistics with no third-party tracking.
  • Inbox panel Approvals waiting for you, with author, last comment, Open the draft, and Approve or Deny with a comment.
  • Migrations and Static publishing panels Read the installation's migration state and see this page's static publishing status per target, with an incremental Publish of just this page.
  • Performance panel For administrators: render time, SQL statements, peak memory, view cache and cache-block use, and time per layout block, without turning on debug output.
  • Review hold in the sidebar The Page panel shows a hold with who placed it, when and why. Reviewers can Hold for review with a reason or Release with a note, and both are audited.
  • Me panel Your account at a glance with links to account, password, passkeys, sessions, security, notifications, drafts and bookmarks, plus sidebar preferences and sign-out.
  • Visitor reading and display settings Visitors who are not signed in can set text size up to 200%, high contrast, reduced motion, a readable font and underlined links for the whole site, stored only on their device.
  • Panels per role Setup > Website sidebar panels chooses, for each siteaccess and role, which panels show and in what order, with a backed-up history and restore.
  • White-label branding per siteaccess Each siteaccess can give the sidebar its own name, logo and accent color. Colors are checked against WCAG 2.2 AA contrast before use.
  • Isolated sidebar styling The sidebar lives in a Shadow DOM with the admin4 look and the user's light or dark mode, so it never clashes with the site's styles.
  • Move over from ezwt exp:wt:migrate-from-ezwt shows a dry run, then moves ezwt's classes, policies and schedule over to expwt.
  • Reviewer page without an account A preview link shows a draft in the site's design with a notice that it is unpublished and when the link expires. It answers 410 once the draft is published or discarded.
  • Edit forms from the site The website sidebar's Page panel edits text, rich text, numbers, check boxes, dates, e-mail addresses and selections directly. Images, files and other datatypes open in the administration's full editor with the configured rich text editor.
Accounts, sign-in and roles 44 features

Exponential 6.0.15 adds passkeys, "Verify it's you" checks, per-device sessions, security activity timelines and a user audit log to its role and policy system.

  • Passkeys (WebAuthn) Users add, name, rename and remove passkeys on My account > Passkeys and sign in with a button or the browser's passkey autofill. The kernel verifies WebAuthn itself.
  • Passkey policy [PasskeySettings] Policy sets passkeys as optional, preferred or required per site, user group or account. The last passkey cannot be removed while the account could not sign in without it.
  • Administrators revoke passkeys With user/passkeys_manage, administrators see and revoke another account's passkeys, each named by its authenticator model. Users get a security mail when a passkey is added, removed or revoked.
  • Verify it's you Before sensitive actions, the user confirms with password, passkey or authenticator code. The confirmation lasts 10 minutes by default and is never weaker than the factors the user has.
  • Verify it's you action groups Groups cover own account security, users and roles, system settings and setup, data exports, deletes (emptying the trash, bulk removal) and, optionally, content publishing.
  • Two-step sign-in An authenticator app (TOTP) or an e-mail one-time code is required after the password. Codes work once, and after five wrong codes the sign-in starts over. Weakening the setup asks for a current code first.
  • Required two-step sign-in for staff New installations set Enforce2FA for Administrator users and Editors with 10 recovery codes, and every login role gets user2fa/setup and user2fa/verify.
  • Passkey as the second step The second sign-in step offers a passkey beside the app code. An account that must have a second step and has a passkey needs no app.
  • Second step on REST, SOAP, WebDAV and remote services Each of these sign-in paths can be opted in. A password alone is then refused for enforced accounts, which use an app password or the current authenticator code instead.
  • Your devices user/sessions lists every signed-in session with browser, system, device type, host, second step used and approximate place. Users sign out one session or all others.
  • New sign-in e-mail A sign-in from a device or country the account has not used lately sends the user an e-mail with links to the security activity.
  • Security activity timeline user/security shows an account's recent security events newest first, filtered by sign-ins, account changes or needs attention, with the last 30 days of sign-ins and failures on top.
  • Was this you and Secure your account For events that need attention, the user answers Yes, it was me or secures the account. Securing signs out every other session, including Remember me sessions, and leads to Change password.
  • Sign-in report Users > Sign-in report shows running sessions, today's sign-ins and failures, a 14-day bar chart and Sign a user out everywhere by id, username or e-mail.
  • Suspicious activity panel The sign-in report lists, for the last 24 hours, networks failing on three or more accounts, locked accounts, repeated failures and accounts signed in from several countries at once.
  • Security alert e-mails Account owners are alerted when two-step sign-in is turned on or off, a recovery code is used, five failed sign-ins happen in a row or the account is locked.
  • Download my sign-in data From the security activity page, a user can download their sessions and security events as JSON after Verify it's you.
  • User audit log Users > User audit log records who did what to each account and group, when and from where, including refused attempts, with before and after values. It never stores passwords and exports to CSV.
  • Check user accounts Users > Check user accounts filters accounts that never signed in, were not seen for N days, or are disabled, locked, orphaned, or share a login or e-mail. Bulk actions tidy them up.
  • Deactivate and move instead of remove An opt-in action disables an account and gathers its locations in a hidden group with no roles. Reactivate and move back restores the account and its remembered locations.
  • Account page overview user/edit shows name, login, e-mail, groups, roles, last sign-in, sign-in count, last password change and account state. Security hints flag issues such as no two-step sign-in or an old password.
  • Change password at next sign-in Administrators tick a box so the user must replace a temporary password after the next sign-in, on every siteaccess. The box is ticked by default for accounts created for others.
  • Modern password change The password form lists requirements and checks them as you type, with a strength meter, show and hide, and Generate a strong password. Typed passwords are never written back into the HTML.
  • Other sessions end after a password change A password change signs out the user's other sessions under every session handler, while the current session stays signed in.
  • Well-known passwords refused Common and well-known passwords, including simple variants and keyboard patterns, are refused on every password form and in the setup wizard.
  • Expiring forgot-password links Password reset links expire after one hour by default (ForgotPasswordKeyLifetime). The page answers the same whether or not an address has an account.
  • Remember me by default Remember me is checked by default and keeps a sign-in for 360 days, so mobile browsers no longer sign users out on their own.
  • Editor account approval Editors create accounts that wait for approval. Every administrator gets a mail with a link to Approve or Deny in the administration, behind Verify it's you, and everything is audited.
  • Section-based staff approval An optional mode puts Administrator users and Editors in a Staff section with the plain approval workflow event for new accounts.
  • Signed links in the registration mail The New user registered mail is HTML with signed View account, Approve and Reject links, each opening a confirmation page in the administration.
  • Unactivated users page Search, sort by age, Activate, Resend activation mail, and Remove all in checked batches. Activation sends the approval mail.
  • Member management role Member management lets editors manage only the Members group. Protected groups are defined in membermanagement.ini and every action is audited.
  • Maximum concurrent logins Account settings can enable or disable an account and limit how many sessions it may have at once.
  • Role list as cards role/list shows each role with its policies and assignments and badges for Full access or Can change roles, with search and sort.
  • Policies as sentences The role page reads each policy as a sentence, for example May read content in section Standard of the classes Article and Folder, and counts the users a role reaches.
  • Policy order in the role editor The role editor shows policy IDs with sortable headings. Policies are reordered by drag, arrow keys, up and down buttons or a position field, all in a draft until Save.
  • No privilege escalation through roles A user who edits roles can grant only what their own access covers. The policy wizard, role editor, copy and assign all refuse broader policies and name them.
  • Permission reads fail closed If reading a policy's limitations fails, the policy grants nothing instead of becoming unlimited.
  • Role assignments a page at a time role/view pages through thousands of user and group assignments with a name filter and flags assignments whose user no longer exists.
  • Fast access for many assignments A user with 600 subtree assignments went from about 48,600 queries to 4 when their access array is built.
  • Personal API keys Users with apikey/create make scoped, expiring REST keys on My account > API access. Each key is shown once and only a salted hash is stored. Administrators review and revoke keys under Setup > oAuth admin > API keys.
  • Role checks in templates Seven template operators such as has_role and has_any_role show or hide page parts by role or permission in one line.
  • User management from the console The exp:user commands list, disable, enable, unlock and move accounts. resetuserpassword.php sets a new password when the admin password is lost.
  • E-mail sign-in accepted Most sites accept the account's e-mail address in the username field, and the password field has a show button.
Exponential Layouts 42 features

Exponential Layouts is a visual page builder for Exponential 6. It stores layouts, zones, blocks, collections and mapping rules in its own tables, picks the layout for each request by rule, and has two admin editors: a server-rendered one and a drag-and-drop single-page app.

  • Visual page builder in the kernel Layouts, zones, blocks, block parameters, collections and mapping rules are stored in dedicated explayouts_* tables, each with a draft and a published status, and rendered on the front end through overridable layout, zone and block templates.
  • 46 block types out of the box The shipped explayouts.ini defines 46 site block definitions. They include text, title, HTML snippet, rich text, image, list, single content, button, card, accordion, tabs, grid, gallery, slider, thumb gallery, grid gallery, sushi bar, zig-zag list, quote, alert, external video, badge, progress bar, map, carousel, Markdown, full view, hero, about, features, lead, logos and two, three and four columns.
  • Reusable content components Hero, Features, About, Logos, Quote and Lead component blocks display editor-managed content components, and a Components screen lists the component blocks and the content they show.
  • Many view types per block Each block definition lists its view types. For example, the list block can render as list, grid, numbered list, zig-zag, accordion or featured grid, and the shipped settings declare 113 view type entries in total.
  • 15 site layout types Layout types include 1 to 4 columns, hero, left or right sidebar, featured, mosaic and layout_1 to layout_6, each with templates under design/standard/templates/explayouts/layouts.
  • Rule-based layout resolving Prioritized mapping rules choose the layout for a request. Rules can target a path, a path prefix, a path regex, a node, a subtree, a content class, a siteaccess or a route, and fall back to a configurable default layout.
  • Time-switched layouts A rule with a time condition switches on and off at its start and end. Until it switches, the page is kept out of shared caches so visitors never see a stale layout.
  • A/B testing by query parameter Query parameter conditions are left uncached, so one address can serve two layouts (for example /page and /page?variant=b).
  • Route targets for module pages A rule can lay out module pages such as content/search or user/* by naming the module view, and a URL alias counts as the content view it stands for.
  • Dynamic collections Blocks can be filled by hand or by a query: children, parent, subtree, siblings, latest, random, manual, relation list, reverse relation list, tags, Exponential content search and topics (12 query types).
  • Relation list queries A block can list the objects in an object relation list field in the editor's order, or the objects that link back to an item ("who links here"), with class filters, sorting and paging.
  • Tag-driven blocks A block can list the content in a subtree that carries given tags. Tags can come from the block, from the current page's fields or from the URL (for tag landing pages), matched with any or all logic. Both ezkeyword and eztags are supported.
  • Drag-and-drop layout editor The single-page editor moves blocks within and between zones, drags block types from the toolbar into a zone and reorders collection items. It works with a mouse, a finger or a pen through Pointer Events, without jQuery UI.
  • Keyboard-accessible editing Blocks, block types and collection items can be picked up, moved with the arrow keys, Home and End, and dropped with the keyboard. Escape puts everything back.
  • Content and Design tabs per block The block sidebar splits each block's parameters into a Content tab and a Design tab, and the editor shows block type and group names in the interface language.
  • Draft, publish and versions Layouts are created as drafts and published when ready. The editor can list draft and published versions and discard a draft.
  • Share links for layouts Share tokens for a layout are created on demand through the JSON API and stored in their own table.
  • Layout preview A layout can be previewed in a public siteaccess from the administration. The siteaccess can be configured, and the preview says so when it uses a different database.
  • Shared layouts and linked zones A zone can be linked to a shared layout, so one header or footer zone can be reused on many layouts.
  • Layouts transfer between sites Layouts, shared layouts and rules can be exported to a versioned ZIP file and imported with a dry-run diff, per-item strategies, remote id mapping and a single transaction. Imports arrive as drafts with their rules disabled.
  • Built-in template editor Layout and block templates can be edited in the admin with syntax highlighting, line numbers, a diff review, a syntax check before saving, revert to original and a Create override action. Every change goes to the audit log, and only the allowed folders can be edited.
  • Two admin interfaces on the same data There are 14 server-rendered screens (dashboard, layouts, shared layouts, rules, blocks, transfer, template editor, preview, components, setup) and a single-page editor. Both work on the same data, so a change in one shows in the other.
  • Layouts tab on every content node The admin node view gets a Layouts tab that shows the layouts and rules that apply to that node.
  • Admin pages built from layouts The administration itself (the admin4l design) is assembled from admin layouts, zones and blocks, resolved by module and view, with a 3-column default. Admin layouts never reach the public site.
  • Debug bar panel The Exp Debug bar has an Exp Layouts tab. It shows the page's layout, the rule that chose it, its zones and blocks with edit links, and the available blocks.
  • JSON API for the editor One dispatcher serves config, layouts, blocks, rules, mappings, transfer, collections, forms, parameters, versions and share resources as JSON.
  • CSRF-protected writes Every POST, PUT, PATCH and DELETE request must carry the form token as an X-CSRF-Token header or a form field.
  • Separate read, edit, export and import policies Opening the editor needs read, every change needs edit, and transfer export and import can be granted separately.
  • Template fetch functions Templates can resolve a layout for the current request, a path or a node, or load one by identifier, including from pagelayout.tpl.
  • Content browser for picking items A server-rendered content browser lets editors browse, search and page through the tree. It can return the picked item to any form, with no JavaScript build step.
  • Class-filtered picker tabs Content, images, files, media and users picker tabs come with predefined class filters.
  • Multi-term subtree search in the picker Every search term must match the node name, class identifier or class name, case-insensitively.
  • Standard block handler set 22 standalone handlers can be swapped in per block through an INI override, with no code change. They cover text, title, Markdown, HTML, image, button, list, single, card, grid, gallery, carousel, accordion, tabs, quote, alert, badge, progress, divider, spacer, map and video.
  • Markdown blocks With league/commonmark installed, the Markdown block renders full Markdown. Hard or soft line breaks are a setting.
  • Privacy-friendly maps The map block uses OpenStreetMap by default, or Google Maps when a key is set. In the standard templates the map loads only after a click.
  • Video embeds The external video block takes a service (YouTube, Vimeo or Dailymotion), a video id and a caption.
  • Service and data API layers A thin service layer (layouts, zones, blocks, collections, rules) and content adapters (loaders, converters, URL generators, validators, the request context) give integrations one stable PHP API.
  • Site API bridge Layouts can work with Site API content and location value objects for loading, conversion, URL generation and block parameter values.
  • Four database engines The schema ships for MySQL and MariaDB, SQLite and PostgreSQL, plus an experimental MongoDB schema description.
  • Console helpers The ext:explayouts:* commands list blocks, layouts, rules and collections, copy and publish layouts, create share tokens and run diagnostics.
  • Translated into many languages The layout extensions were translated into 59 more languages in one release. Chinese, South Asian, African and many European languages are included.
  • Extend without forking New blocks and queries are added in your own extension through handler interfaces, with no core change. Every setting and template can be overridden through the normal cascades.
7x Themes: Media and the default designs 24 features

A new Exponential 6.0.15 site using the default multisite package opens in the media design of 7x Themes: Media, a modern, responsive front end with light, dark and darker modes and Exponential Layouts pages. The simpler sevenx_site packages use the light Simple design.

  • Media design as the default site look The default multisite package gives the Fit & Healthy and Bold Agency websites the media design, with ezwebin, standard and base as fallbacks.
  • Two demo websites in one install Fit & Healthy and Bold Agency (English and German) are installed together. Cross-site links are written for the siteaccess that serves the target.
  • Light, dark, darker or system mode A header switch offers light, dark, darker or the system's mode. The choice is set before the page draws, so there is no flash, and text contrast is 4.5:1 or more.
  • Hand-maintained template set The media design ships about 426 templates for the page layout, content views, layout, zone and block templates, parts, forms, modules and e-mails, plus SASS sources.
  • Every class in every view Generic full, line, listitem, embed and embed-inline views show every content class in the media markup without a template or override rule.
  • Generic full page The full page shows the page header, the first image, the intro, every other field with content, a form for information collectors and paged children of containers.
  • Layout block templates The design ships its own Exponential Layouts block templates for lists, galleries, titles, rich text, HTML snippets, buttons, columns, product highlights and the content components.
  • Item views for blocks Card, standard, listitem, line, overlay, mini, slide, zigzag, accordion, gallery grid, gallery thumb, modal and product card item views are generic for any class.
  • Image focal points The focal point an editor sets on an image decides which part shows in cards, teasers, hero and about components, gallery grids, thumb galleries and slides.
  • Search with suggestions and filters The header search suggests content while typing, and the search page has filters.
  • Styled HTML form mails Contact form mails are HTML with a plain-text part and name the page and form that sent them.
  • E-mail preferences and consent pages The e-mail preference, consent log, categories and suppression pages are drawn in the design as timelines and cards in light, dark and darker, and work right to left.
  • Bookmarks in the site design My bookmarks has folders, search and ordering in the media look.
  • Public newsletter pages Newsletter lists and editions show as public pages with a subscribe link.
  • Editor toolbars that keep their look The site styles leave the TinyMCE 8 and Tiptap toolbars untouched in every color mode.
  • Twig and Smarty template variants Besides .tpl, the alpha tree carries smarty_media and twig_media variants of the design. Pages such as the consent timeline are drawn in all three engines.
  • 54 template operators Operators such as intro, image, enhanced_link, content_tags, ng_query and ng_view_content make rich templates short.
  • Full image alias set The design comes with the image aliases its templates use, from small to billboard.
  • Responsive Simple design The light Simple design has a multi-level dropdown menu, a cart icon, and article, blog, gallery, product and basket templates.
  • Hide the powered-by notice without code An attribute of the page design object hides the footer notice.
  • Visitor design switch A public siteaccess can let visitors switch between designs with one click, remembered in a cookie, with no account needed.
  • Browser-rendered portal designs Four portal designs (jQuery 4, reactive, React and wireframe) render news, shop, forums, media, feeds, search and login in the browser.
  • Pages built with layouts The two demo sites start with 21 published layouts with their zones, blocks and rules.
  • Starter design skeleton 7x Super is an empty design extension that enters the design chain by itself, ready to fill.
Exponential UI 19 features

Exponential UI is the JavaScript API of Exponential 6: jQuery 4, a small Exp namespace and one module for each interactive feature. It replaces YUI 2 and YUI 3 one feature at a time without dropping any feature.

  • One library instead of three It replaces the YUI 2.8, YUI 3.17 and jQuery 3 stack, 47 MB of it end-of-life, with jQuery 4 and a few small modules.
  • jQuery 4 and jQuery UI 1.14 everywhere Activated before ezjscore, it moves ezjsc::jquery and ezjsc::jqueryUI to jQuery 4 and jQuery UI 1.14, and the admin's own code has been moved with them.
  • Native browser features first Modules use native dialog elements, date inputs, Promises, CSS transitions and position sticky wherever the browser can do the job.
  • Promise-based server calls Exp.io.call, form, poll and url call ezjscore server functions. A signed-out session, a refusal, a server error or no answer each comes back as a clear error instead of failing silently.
  • Backward compatibility layer $.ez() keeps working on top of the new server calls, so existing site code does not break.
  • Modal dialogs Exp.dialog provides open, confirm, alert and form dialogs on the native dialog element. They replace the YUI dialogs.
  • Uploads with progress Uploads show a progress bar and a Cancel button per file, take several files at once and accept drop zones. The relation upload and ezmultiupload use them.
  • Data tables Sortable, paged tables support selection, menus, inline editing and table options. They drive the admin's sub-items table and the eztags children table.
  • Date picker A calendar for date and date/time fields in admin, admin2, admin3, ezwebin and ezdemo replaces YUI Calendar.
  • Autosave and draft preview Drafts are saved while editing and can be previewed. ezautosave uses this.
  • Collapsible menus remembered per user Menus and panels collapse, and their state is stored per user. The admin's right menu and edit menu use this.
  • Sticky edit toolbar The toolbar stays in view while scrolling, with a go-to-top link, in admin edit forms.
  • Declarative modules Modules start from data-exp-* attributes through Exp.register and Exp.start. The core also includes events, user preferences, key handling and reduced-motion detection.
  • Safe under a strict Content Security Policy There is no eval and no inline handler. Every POST carries the form token, dialogs do not run the scripts they show, and tables write values as text.
  • No third-party requests by default jQuery 4 is served from the installation. A CDN option comes with subresource integrity hashes.
  • Accessible, translated and themeable Every module is accessible, translated, themeable with CSS custom properties and covered by unit tests in the browser and in PHPUnit.
  • In-admin test runner Opening /expui/test runs every unit test of the API on a real admin page. The README expects 118 passed and 0 failed.
  • Wide language coverage One release added translations into 59 more languages, alongside Chinese, South Asian, African and European translations.
  • Full documentation set A book, a getting started guide, an API reference, a page per module, a YUI conversion guide, security, testing, architecture and roadmap documents ship with the extension.
Exponential Admin UI 19 features

Exponential Admin UI (exp_adminui) is a second look for the Exponential 6 administration, ported from Netgen Admin UI to plain Exponential templates. It runs as its own adminui siteaccess next to the stock admin, on the same content.

  • Two admins side by side The adminui siteaccess runs next to /admin with the same users, roles and content, and needs no Symfony.
  • Set up automatically on new sites Since 6.0.15 the setup wizard, the kickstarter, exp:install and the multisite installer create the adminui siteaccess when the extension is present.
  • Admin UI page frame A dark sidebar holds the main sections and the user menu, with a search header, a light left column with the menu or content tree, a "You are here" path and a footer.
  • Every admin view available The Admin UI's own templates are merged with Exponential's newer views. Audit, cronjobs, maintenance, layouts and newsletter views come from admin4l and admin4 inside the Admin UI frame.
  • Tabbed node views Node views have view, sub-items, translations, locations and relations tabs, with a default tab per class (containers open on sub-items).
  • Resizable details panel The details panel can be resized by drag or with the arrow keys, and the width is saved as a user preference that follows the user to every browser.
  • Header search with suggestions The posted header search suggests content, users, classes and admin pages while typing and leads to the admin search page with filters, chips and sorting.
  • Configurable sidebar plugins Sidebar blocks for legacy tabs, Layouts, Tags, Collected information, Cache, Bookmarks and UI switch can be enabled or hidden, and each is shown only when policy allows.
  • Cache and bookmark dropdowns The sidebar has a clear-cache dropdown and a bookmarks dropdown with bookmark folders.
  • Contextual help With the help system, the header shows a Help menu with search, the help page for the current view and a link to the Help center.
  • Ace code editor for snippets Text fields of chosen classes, such as HTML boxes, are edited in the Ace code editor.
  • Modern widgets Exponential UI widgets and jQuery 4 replace YUI, and the edit forms use the expui date fields and uploads.
  • Exponential branding The interface shows Exponential's logo and names, with the Admin UI blue as accent color.
  • Icon set and online editor skin The extension brings its own icon theme for classes, MIME types and flags, and a matching online editor skin.
  • Collapsible long menus Left menus honor CollapseAfter and show the first links with a More disclosure for the rest.
  • No PHP, no tables It is a design with settings only, with no classes, no modules and no database tables. Templates fall back to admin4l and admin4.
  • Same permissions as the admin It adds no policies of its own. The sidebar shows only what the user's roles allow.
  • German catalogue A German catalogue covers the texts the kernel catalogue does not translate.
  • File-level tests Bundled tests check the help button, inline CSS and script rules, edit conflicts, the map API key and context menus without a kernel or database.
Remote services (expservices) 25 features

expservices turns ezjscore server functions into a library of remote HTTP services covering what the administration does, with discovery, one answer envelope, policies per service and personal API tokens. It also ships client libraries and four browser front-end designs that run on these services in the browser ("client-side remote services").

  • The whole admin as an HTTP API At the time of writing, 1,122 services were counted, covering settings, caches, content, users, the shop, feeds, media, tags, layouts and the audit trail, so remote apps and JavaScript front ends can do what the admin does.
  • Content services 350 content services cover nodes, objects, classes, attributes, versions, translations, relations, locations, trash, sections, states, URL aliases, search and content jobs.
  • Users and access services 195 services cover users, groups, roles, policies, sessions, preferences, notifications, collaboration and account flows.
  • Commerce, community and feed services 255 services cover products, basket and checkout, orders, VAT, currencies, discounts, wish lists, shipping, payments, forms, polls, forums, comments, reviews, RSS imports and exports, and RSS, Atom or JSON Feed output for any subtree.
  • Media and other services 218 services in 14 domains cover images and aliases, files and signed download links, audio and video, tags, layouts, the audit trail (read only), newsletters, sitemaps, statistics, designs, languages, external links and PDF.
  • System and operations services Core domains read settings and cover caches, cronjobs, extensions, packages, workflows, Velocity, the extension point survey and the debug summary.
  • Self-describing catalogue expservices::catalog lists every service with its arguments, access and write flag, so typed clients can be generated from it.
  • One answer envelope Every answer is ok, data and meta, or an error with a code. Lists are paged with total, offset, limit, count and has_more.
  • Personal API tokens Users create tokens for scripts and apps that expire after 1 to 365 days. Only a SHA-256 hash is stored, and the token is sent as a Bearer or X-Exp-Token header with the user's own policies.
  • Optional second factor on login A site can require an authenticator code on the service login for accounts that must use two-step sign-in.
  • Policy per service Each service is public, user-only or tied to a module and function policy. Requests without a login get 401, and requests without the policy get 403.
  • Protected and audited writes A write needs POST, the form token and the policy, and every successful write is recorded in the audit trail.
  • Large operations become jobs Heavy operations are routed to content jobs instead of blocking the request.
  • One declaration, three channels The same service declaration serves HTTP, MCP tools generated from the catalogue and, when a read service opts in, the expai writing assistant.
  • Write your own service in one class A domain is one class that extends expServiceBase. A new service appears in the catalogue and in Setup > RAD without further steps.
  • Shell client A bash and curl client handles login, whoami, the form token, the catalogue, reads, paged reads and writes, with API token support.
  • Python client A standard-library-only Python client works as a module or a command, with session cookies, paging, form-token writes and typed errors.
  • Client examples for native apps The guide has client snippets for Kotlin with OkHttp, Swift, Objective-C, Qt and C++, and GTK with Python. The shell and Python clients and the GTK snippet were tested against a live site.
  • jQuery 4 portal front end The expportal_jquery design is a full corporate portal rendered in the browser: home, news, shop with basket, forums, media gallery, feeds, search, login and profile. It needs no build step.
  • Reactive portal front end The expportal_reactive design has the same features with components, a store, one-way data flow and a small keyed virtual DOM.
  • React portal front end The expportal_react design is a React 18 and React Bootstrap portal with hash routes for news, shop, basket, forums, media, feeds, search, login and profile. Its libraries are vendored, so it works offline without Node.
  • Wireframe viewer The expportal_wireframe design shows each screen as grey blocks annotated with the services that feed them. It has a phone and desktop toggle and marks each service as present or missing.
  • Accessible, responsive portals in light and dark The portals have skip links, landmarks, aria-live announcements and labelled forms, and are built mobile first. They follow the system color scheme, with a toggle remembered in the browser.
  • Graceful service detection The portals read the catalogue at boot and show a clear "service not available" state instead of an error for a missing service.
  • Three database engines for tokens The token table ships for MySQL, PostgreSQL and SQLite.
Exponential Intelligence 30 features

Exponential Intelligence (expai) is an AI writing assistant in the Exponential 6 administration. It writes drafts, never published content, as the signed-in editor with that editor's permissions, and gives administrators control over providers, data residency and cost.

  • Drafts, never surprises The assistant writes only drafts, as the signed-in editor. Publishing always goes through the normal workflow, including approvals.
  • Intelligence tab on every content page Each user has a conversation per node. The assistant asks back when a request is unclear, shows each lookup and draft as a step, and links the drafts it wrote.
  • Send for approval Send for approval runs the regular publish operation as the editor, so an approval workflow holds the version for the approver.
  • AI in the edit form Fill the fields fills the form from a brief. Per-field actions (Write, Rewrite, Shorten, Translate, Suggest), one-click presets for title, summary, meta description and keywords, and an Improve menu work on every text field.
  • Image alt text A vision model suggests alt text for image fields. A Missing alt text report queues suggestions for a whole subtree as drafts.
  • Vector workspace Threads have scope, plan and write modes, a model and lane per thread, background runs, live progress and a command palette (Ctrl or Cmd+K).
  • Staged review of every change Every change is reviewed per field and part before anything is written, and each hunk can be accepted, rejected or edited.
  • Plan mode with cost estimate Bulk work is planned first and shows an estimated cost before it runs.
  • Checkpoints and restore Each turn saves a checkpoint, so an editor can undo what the AI did since a given turn without cleaning up drafts by hand.
  • Parallel runs and steering An approved plan runs its items side by side as child runs. Editors can steer a running turn with a note the model reads at its next step.
  • AI chains Multi-step writing runs through the job queue: write, review, revise, SEO, a human checkpoint, then translate.
  • Translation sync After the source language changes, each translation is classified as unchanged, needing a patch or needing a full retranslation, with cost thresholds.
  • DeepL and LibreTranslate DeepL or a local LibreTranslate can handle full translations, patches or the field action per language pair, under the same data policy and budgets.
  • AI provenance label Every version the assistant wrote carries an Exponential Intelligence label in My drafts, version views, edit forms and approval items.
  • Usage dashboard The dashboard shows estimated cost, tokens, requests and drafts with trends, a chart per day, limits and versions waiting for approval.
  • Any model, including your own Supported providers are Anthropic, any OpenAI-compatible service, a custom provider class, or a local open-weight model managed from the admin.
  • Local models managed from the admin A pinned Ollama on the loopback address can be started, stopped and pulled from the admin through a root-owned helper with an allowlist. The web process never runs a command.
  • Data residency policy Each provider has a region (US, EU or local) and a retention setting, and rules per section and class decide which content may go where. Every request records where it went.
  • Write gate and probe Only models that passed a live tool-calling probe, or are trusted by configuration, may write drafts.
  • Costs you can cap Limits apply per conversation, session, user, day, month, site and provider, with a monthly site budget and job group budgets.
  • Lanes and batch processing Standard, flex, batch and fast lanes are available, and provider batch APIs make bulk work cheaper.
  • Privacy summary for a data protection officer One printable page lists every provider's region, retention, terms date and key source (never the key), plus roles, lanes, limits and outside tools.
  • Master switch and veto hook The assistant can be switched on or off globally or per siteaccess, and rules or an event listener can refuse a request with a reason.
  • Tamper-evident audit channel Actions are written to their own audit channel as hash-chained JSON lines, never with prompts, answers or keys.
  • Fine-grained policies Separate policies cover writing, everyone's logs, settings, model use (limited by provider), model management and MCP tools (limited by server).
  • Tools and MCP The model can call content lookups, drafts, web fetch, web search and project history, and external MCP servers, with an allowlist and an SSRF guard.
  • Service tools A read service declared once in expservices is also an MCP tool and an assistant tool, with the caller's permissions.
  • AI-aware content packages Packages carry AI provenance in their metadata, and drafts in a package written with AI carry the label.
  • Built-in help Every documentation page appears in the admin help center, searchable, with a "?" link on each expai page.
  • Runs everywhere the kernel runs It works on Apache with PHP-FPM and on Exponential Velocity, on MySQL or MariaDB, PostgreSQL, SQLite, Oracle and MongoDB, and in the admin, admin3 and admin4 designs.
7x Database Source Editor (sevenx_dse) 17 features

sevenx_dse embeds AdminNeo, a maintained fork of Adminer, in the Exponential administration behind its login and role policies. Administrators can browse, edit, query, export and import the database without a separate tool or SSH session.

  • Database editor inside the admin A DS Editor link in the Setup menu, and an optional tab with a brush icon, opens the editor in the administration's own page layout.
  • Safety dashboard first A dashboard comes first and shows the database type, name, table counts, how many tables belong to Exponential and the server version, without credentials. A warning must be acknowledged before the editor opens.
  • Browse and edit rows Rows can be filtered, sorted and paged, and rows can be edited, added and deleted.
  • SQL console Any SQL statement runs with syntax highlighting, and the statement is only posted, never put in the address.
  • Schema inspection and design The editor shows columns, indexes, foreign keys, views, triggers and a schema diagram, and can create and alter tables.
  • Export and import Tables or the whole database export as SQL, CSV or TSV straight to a download, and uploaded SQL files can be imported.
  • One-click site database Open the database of this site connects with the login from site.ini, which is never typed in or shown.
  • Many database drivers Drivers ship for MySQL and MariaDB, PostgreSQL, SQLite, MS SQL, Oracle, MongoDB, Elasticsearch, ClickHouse and SimpleDB, where the PHP extension is present.
  • Database chooser Change database lists the site database, the logins remembered in the session (the current one marked Connected now) and a login form for other servers or SQLite files.
  • Fast on large SQLite databases Navigation skips per-table row counts. Counts are cached and marked approximate after a change, so pages open in a fraction of a second.
  • Safe defaults The database password is not pre-filled unless switched on. SQLite files are accepted only inside the site directory, and the change-database link carries a per-session token.
  • Role-based access Access requires the dse policy, which the built-in Administrator role already has.
  • Follows the admin4 look in light and dark The editor styles are scoped to the editor and take their colors from the admin tokens, with no inline CSS.
  • Content Security Policy compatible The embedded view sends its own nonce-based policy, and the outbound version check is switched off so nothing calls GitHub from the browser.
  • Translated Its own texts are translated into 17 languages, and AdminNeo uses the administration's language.
  • Runs on PHP-FPM and Velocity Under Velocity's persistent workers, the view retires its worker after answering so AdminNeo always runs clean.
  • Bookmarkable state The editor state lives in view parameters rather than query strings, and old addresses are redirected.
Kernel and kernel services 47 features

Exponential 6.0.15 has a modernized PHP kernel with a compiled service container, a wide supported PHP range, and extension hooks so you can change behavior without patching core files.

  • Kernel service container Shared kernel objects such as the database and the settings are defined by name in settings/kernelservices.ini, with a class or factory, arguments, a worker, request or prototype scope and tags. Extensions add their own services in kernelservices.ini.append.php, and code fetches them with expKernelServices::get(), has() and tagged().
  • Compiled "Kernel services" cache The container is compiled per siteaccess into var/cache/kernelservices/ by recording the kernel's extension activation passes, and a request uses it only when it starts from exactly the recorded state. The deploy and ezcache.php --clear-tag=ini rebuild it, and [ContainerSettings] Mode=disabled switches it off.
  • Measured faster request start On the test installation with 62 active extensions and 18 siteaccesses, the start of a request up to the module run dropped by 15 to 35% in a PHP-FPM-like setup and by 51 to 72% with Velocity's pool emulated.
  • Worker-scoped settings objects With WorkerScope=auto, eZINI hands out copies of settings objects that are built once per worker and siteaccess. Any change to the override directories, a reset, a save or an INI cache clear drops them.
  • Request-scope reset hooks The kernel's seven per-request resets became the reset hooks of the request scope, kept in the same order. Code can add its own hook with expKernelServiceScope::onRequestReset(), which keeps persistent workers clean between requests.
  • Service console commands exp:services:compile, exp:services:list, exp:services:show and exp:services:check compile, list, inspect and validate the container from the shell.
  • PHP 8.0 to 8.5 supported Exponential officially supports PHP 8.0 to 8.5, including PHP 8.0, the stock PHP of Red Hat Enterprise Linux 9. The CI Quality workflow lints every file with PHP 8.0, runs a production install on it and boot-tests every kernel and extension class.
  • PHP 7.4 usable without support Exponential 6.0.15 installs and runs on PHP 7.4 again for sites that cannot change their server PHP yet, without a support commitment. Velocity, Exponential Layouts and a few PHP 8 extensions are left out there, and the setup check accepts 7.4 with an "unsupported" notice.
  • PHP floor metapackage se7enxweb/exponential-php-floor ships one version each for PHP 7.4, PHP 8.0, PHP 8.1 to 8.3, and PHP 8.4 and later, so Composer installs the extension releases that run on the PHP it uses. The composer.json PHP constraint reaches up to ^8.8.
  • PHP 8.4 and 8.5 deprecation clean-up Fatal errors now go through eZFatalUserError::raise() instead of trigger_error with E_USER_ERROR. Database sessions pass PHP a SessionHandlerInterface object instead of six callbacks, so PHP 8.4 no longer reports a deprecation on every request.
  • expcomponents library forks All 21 Zeta Components are forked as se7enxweb/expcomponents-* under the Apache License 2.0. The forks keep the ezc* classes and APIs and are tested on PHP 7.4 to 8.5.
  • Runnable base classes Kernel commands, cronjob parts and module views are classes (Runnable, Command, CronjobPart, ModuleView). Events fire around every command, cronjob part and view, and shared services cover the trash, sessions and drafts.
  • Access and view cache filters Five ezpEvent filters let extensions take part in content/view/cachekeys, content/download/access, content/edit/access, collaboration/item/access and content/notification/create without patching the kernel. No time is spent on them when no listener is registered.
  • Content limitation handlers for extensions Extensions can add policy limitations and return column conditions that the kernel turns into escaped IN statements. A missing or faulty handler fails closed.
  • Faster access arrays With [RoleSettings] AccessArrayPrefetch, a user's access array is built from all of their roles in three queries. A user with 600 subtree assignments went from 3,550 ms and about 48,600 queries to 244 ms and 4 queries.
  • Cronjob part run filter runcronjobs.php asks the cronjob/part/run filter before each part, so a listener can hold back a part during a release without anyone patching the script.
  • Per-request prepend file The config.php constant EXP_REQUEST_PREPEND_FILE names a file that index.php runs at the start of every request. This gives persistent workers a place for request filters.
  • Environment-specific settings The EXP_ENV constant in config.env.php names a machine's environment. Every settings file can then have a variant such as site.ini.test.append.php next to it.
  • Configuration managed by the deployment [ConfigurationSettings] ManagedByDeployment=enabled locks a siteaccess's configuration to version control. The admin's INI, toolbar, menu and template editors then no longer write files into the release directory.
  • Documented INI load order The documented order now matches how eZINI::overrideDirsByScope() reads it: siteaccess extensions, extension siteaccess directories, the siteaccess, active extensions, then the global override.
  • Per-site logs, INI cache and expiry paths On multi-site installations, UseGlobalLogDir, LogDir, ExpiryDir, INICacheDir, LogVarDir and CacheVarDir give each site its own logs, INI cache and expiry timestamps. Clearing one site's cache no longer expires the caches of every site.
  • File and directory mode limits The config.php constants EZP_DIR_MODE_MAX and EZP_FILE_MODE_MAX cap the mode of every file and directory the installation creates and set the process umask. A test fails on any new native chmod, mkdir or umask call that bypasses the helpers.
  • System card commands ./console exp:expfetch draws a terminal system card of the installation, PHP, engine, database and site, with health hints. exp:info adds an inventory and exp:about adds the project. The facts come from pluggable providers, each with a time budget and optional process isolation, and secrets are always masked.
  • System information report Setup > System information and ./console exp:system:info show the serving engine, health checks and overview cards, in a text and JSON report for support requests. The command exits 1 when a check fails, and paths and secrets are masked.
  • Twig 3 templates in the kernel Designs can hold *.twig templates next to .tpl, with overrides, includes, caching, every template operator and every fetch function. A converter turns a whole design into Twig and back.
  • Smarty 5 templates in the kernel Designs can hold *.stpl Smarty 5 templates that are found, overridden and cached like any template, and a converter ports a .tpl design to Smarty.
  • Resumable content jobs Large remove, copy, move, hide, section, state and location operations run as background jobs. They work in batches with checkpoints and resume where they stopped, even after kill -9.
  • Content jobs survive a busy database A batch that meets a busy SQLite database or a MySQL lock wait or deadlock is rolled back and retried with back-off (BusyRetries, BusyBackoffMax). Failed jobs are resumed by the contentjobs cronjob part.
  • Subtree copy re-points links When a subtree is copied, links and embeds in XML text that point inside the subtree are re-pointed at the copies by real XML parsing, while literal blocks are left untouched.
  • Transfer registry Every import and export tool declares itself as a transfer.tool service, and the registry lists a tool only when its module exists and the user holds its policy. The kernel registers Packages, RSS import and export, Collected information, Audit export and PDF export.
  • One run engine and history for imports and exports expKernelTransferRunner sends each run to the expqueue job queue, the kernel's content jobs or the tool itself. Every run of every tool is recorded in the exp_transfer_run table on every engine.
  • Data table catalog The kernel catalogs every eZPersistentObject class of the kernel and active extensions with its table, fields, keys and relations to content, and compares each table with what its database actually holds.
  • Content finder by visitor address The content finder resolves a page by the address a visitor sees, including PathPrefix siteaccesses, URL alias tails and partial words. Its matching is checked on every database engine.
  • Trash records who and where ezcontentobject_trash records trashed_by and trashed_via in the same transaction as the move. With 100,000 trash rows a page went from 2.7 to 3.2 s down to 0.54 to 0.90 s on SQLite.
  • Trash retention content.ini [TrashSettings] KeepItemsForDays makes the trashpurge cronjob part purge only items older than the given number of days.
  • Renamed nodes keep old addresses as redirects On MySQL, PostgreSQL, SQLite and Oracle, renaming or moving a node turns its old address into a history entry that answers 301 to the new address.
  • Content language fallback setting [RegionalSettings] ContentObjectFallbackLocale (default eng-US) replaces a hard-coded eng-GB fallback for class and attribute names.
  • 219 locales Unicode CLDR 44 data added 89 locales and then 81 more, for 219 in all. They cover South Asian, African, Middle Eastern and right-to-left languages, plus Latin and Klingon.
  • Locales for 22 Indigenous languages of the Americas Content can be written in Navajo, Cherokee, Lakota, Inuktitut, Nahuatl, Guarani, Aymara and 15 more Indigenous languages of the Americas.
  • Right-to-left text direction A locale can declare TextDirection=rtl, and the kernel then exposes text_direction and is_right_to_left to templates. Right-to-left content gets its language tag and dir=rtl in edit forms and rich text editors.
  • Translation fallback chains ./console exp:i18n fallbacks shows each locale's chain and catalog coverage, and exp:i18n check exits 1 on a cycle or a chain that is too long.
  • One kernel log rotation eZDebug and eZLog share one rotation (expLogRotator) by size and count. A file lock makes it safe when Velocity and PHP-FPM write the same logs.
  • Request logs 404 and 410 answers go to var/log/404.log with a reason, masked addresses and masked query values. error.log keeps only the real faults.
  • Log viewer and log management Setup > Log files views, tails, searches, rotates, compresses and prunes logs, masked by default. Download all logs builds one archive with a SHA-256 manifest, and every action is audited.
  • Notification service expNotificationService runs, plans, records and audits notification runs under a lock. Mail the transport refuses stays queued and is retried for RetryHours (default 72).
  • Class id caches follow the database Class and class attribute id lookups remember the database they were read from and read again after eZDB::setInstance(). Scripts that switch databases therefore get correct class filters.
  • View counts for multi-site installations ./console exp:viewcount:update counts page views from the access logs into ezview_counter, and it can count several siteaccesses in one run.
Databases, caches and performance 43 features

Exponential runs on five database engines and layers a role-aware HTTP cache, an SQL query cache, the static cache and the Velocity application server for fast page delivery.

  • Five database engines One installation command installs on SQLite, MySQL, PostgreSQL, MongoDB or Oracle. SQLite is the setup wizard's default.
  • SQLite in one file The eZSQLite3DB driver and the eZSQLiteSchema handler run a complete site from one file on disk, with no database server to install or secure.
  • SQLite writer queue A transaction waits at its start for the writers ahead of it, up to SQLiteTransactionWait seconds (default 25) on the web and SQLiteCLITransactionWait (default 300) for scripts. This replaces "database is locked" failures.
  • SQLite busy timeouts for single writes Writes outside a transaction queue on the writer lock too, for SQLiteBusyTimeout (5000 ms) on the web or SQLiteCLIBusyTimeout (30000 ms) on the command line.
  • SQLite composite keys repaired Upgrade step 6.0.15-sqlite-composite-keys rebuilds, in one transaction, every SQLite table whose key differs from share/db_schema.dba, keeping its rows and indexes.
  • MongoDB content repository The expMongoDB adapter stores the whole content repository in MongoDB by turning the kernel's SQL-shaped calls into find, aggregate, insert, upsert and delete. It comes with a schema handler, index scripts and MySQL conversion helpers.
  • MongoDB gains aggregations and SQL translation In 6.0.15 the MongoDB driver translates LIKE with ESCAPE, LOWER and UPPER comparisons, IN, BETWEEN and range conditions. It reads a missing field as its declared default, and the trash list and summary come from aggregations.
  • MongoDB site packages and migrations Site packages install on MongoDB, and migrations, including YAML steps and GraphQL steps, are tested on a MongoDB 7 service in CI.
  • Oracle 11g and 12.1 support With ezoracle 2.3.7, URL alias lookups work on Oracle before 12.1 again, and the DFS cluster backend lists files with ROWNUM there.
  • Oracle-aware query cache Session-only ALTER SESSION statements no longer make the cache stale, which raised Oracle hits from 2 of 12 to 10 of 12 lookups per request. Session NLS settings are part of the cache key.
  • PostgreSQL and SQLite-aware query cache The query cache reads PostgreSQL and SQLite quoting, dollar quoting, UPDATE ONLY and multi-table TRUNCATE and DROP correctly. It never caches volatile functions such as clock_timestamp() or randomblob().
  • Generic PDO driver expPDODB is a generic database driver over PDO for engines the kernel has no native driver for, such as SQL Server or Oracle without ezoracle.
  • Named database connections expDataConnections defines SQLite, MySQL/MariaDB, PostgreSQL, Oracle, SQL Server and MongoDB connections, local or remote, with a connection test. Persistent classes can read and write on their own connection.
  • Role-aware HTTP cache Whole rendered pages are stored per permission context (anonymous, role context or private) and answered before the kernel starts, so a thousand members share one copy of each page. An X-Exp-Cache header reports HIT, STALE, MISS or BYPASS, and the cache is off by default.
  • HTTP cache with request-shield and tag purges The HTTP cache works with request-shield in front of it. With ContentChangePurges=tags, a content change purges node and object tags the way Ibexa's HTTP cache tags them.
  • Per-page headers on cache hits The httpcache/store/headers filter lets an extension store its own headers with a cached page, so they are sent on cache hits too.
  • SQL query cache eZDBQueryCache answers a SELECT again from memory until a write to one of its tables makes the result stale. It is hooked into the MySQL/MariaDB, PostgreSQL, SQLite and Oracle drivers and is off by default.
  • Query cache storage modes In shared mode, querycache.ini Storage=auto, apcu or file keeps results in APCu or in files, for example for web servers that share var/ over NFS. A cleanup cronjob or a bounded request sweep removes old result files.
  • APCu reserve for the query cache ApcuReserve (default 25 percent) stops the query cache from filling APCu, which protects the HTTP cache, API keys and other users of the same pool.
  • Query cache reporting The debug output reports hits, misses, stores and the estimated database time saved, with string literals masked. The Exp Debug bar shows a hit-rate chip with the saved time as a share of the page time.
  • Parallel static cache refresh The static cache refreshes the pages of a publish once each and in parallel (FetchConcurrency, default 8). In the measured case this took 4975 ms down to about 500 ms.
  • Static cache generator The static cache turns pages into plain files that the web server sends without starting Exponential, crawled the way a visitor would and with progress shown.
  • Cache clears that move directories aside [FileSettings] RenameBeforeDelete moves cache directories aside before deleting them, and the cache_cleanup cronjob part removes the leftovers.
  • Lean view cache for cache_ttl=0 A node view whose template sets cache_ttl to 0 stores only a few bytes of no-cache advice instead of the whole page.
  • View cache profile in the debug bar The Exp Debug bar shows a fingerprint of the user-dependent parts of the view cache key, so you can see which users share view cache files.
  • Redis and Valkey cache hooks Kernel hooks let the sevenx_valkey_cache backend keep the content view cache, the compiled INI cache and template blocks ({valkey-block}) in Redis or Valkey. Entries get TTL expiry, generation locks against cache stampedes and node and subtree purge indexes.
  • LiteSpeed page cache without a plugin A commented block in .htaccess_root lets LiteSpeed and OpenLiteSpeed serve anonymous pages without PHP, while excluding sessions, the administration and dynamic modules.
  • Cache preloader Setup > Preload and bin/php/preload.php warm a site's caches with one crawler, page and depth limits, image checks, dry runs, a run lock and a history of the last 20 runs.
  • Cache catalog and controls Setup > Caches lists every cache by group with its size, tags and last clear, read from the audit trail. exp:cache does the same from the shell, and every clear writes a system.cache.clear audit record.
  • Velocity application server Velocity runs the installation from a pool of long-lived PHP workers with a warm database connection, warm file caches and a warm opcode cache. Since 6.0.15 it is part of Exponential and installed by composer install.
  • Three Velocity engines exp:velocity drives the bundled Qbix server (recommended for every stage), FrankenPHP (a production-ready alternative) or PHP's built-in server for development.
  • HTTP/2 and automatic HTTPS Velocity serves HTTP/2 over TLS and makes its own certificate when none is configured. It serves your own files, PKCS#12 bundles or Let's Encrypt and other ACME certificates, and renews and swaps them without a restart.
  • Velocity response cache Public pages are answered inside the server process before a worker is chosen, at about 0.2 ms of CPU, with 304, ETag, stale-while-revalidate and negative caching.
  • On-the-fly image resizing Velocity serves static files without PHP and resizes images on request with ?w= and ?h=, choosing AVIF or WebP for browsers that accept them and caching the result.
  • Opcode cache fix for persistent workers Velocity keeps regenerated kernel cache files in OPcache. Before the fix OPcache served 2.7% of includes under Velocity against 97% under PHP-FPM (644 ms against 166 ms of CPU), and an optional profile compares engines.
  • Streaming responses and stream caps Velocity streams Server-Sent Events with StreamTimeout, StreamShare and MaxStreams caps, answers 503 with Retry-After beyond them, and retries a GET once when its worker died.
  • WebSockets, SSE and rooms Velocity has built-in WebSocket (socket.io compatible), room and Server-Sent Events models for real-time features next to a site.
  • Velocity dashboard, control panel and Q shell Each server has a live dashboard at /Q/dashboard, a password-protected control panel at /Q/panel and a scriptable drop-down Q shell for workers, cache, sites and certificates.
  • Velocity watchdog and detached restarts Restarts and deploys run stop and start as one detached unit. An optional systemd watchdog (exp:velocity watchdog) starts a server that died unless it was stopped on purpose.
  • Velocity packages, images and binaries Velocity ships as a Composer package, deb and rpm packages, amd64 and arm64 Docker images, static binaries for Linux, macOS and Windows, and a phar.
  • Velocity scheduler A cron inside the server runs handlers at intervals or at set times of day without doubled runs around restarts.
  • Benchmark command ./console exp:benchmark times HTTP pages and kernel operations (boot, view render, INI load, fetches, cache I/O). It reports min, median, p95 and p99, compares servers and saved baselines, and exits 1 on a regression.
  • Migration engine performance checks CI measures 1,000 YAML migrations, a 5,000-row data step and a resumable 5,000-row PHP migration on SQLite, MySQL/MariaDB, PostgreSQL and MongoDB.
Console, upgrades, migrations and deployment 45 features

Exponential runs its operations from a scriptable console with dry runs by default, upgrades that can be verified and rolled back, migrations under version control, and one-command deploys.

  • One-call console upgrade ./console exp:upgrade --apply backs up, then runs the code, libraries, database, scripts and finish stages in order, records each step and stops at the first failure. Without --apply it is a dry run.
  • Upgrade stages as commands Each stage is its own command (exp:upgrade:code, :libraries, :database, :scripts, :finish), next to :status, :steps, :verify and :backup. Machine output follows exp-upgrade/1 with exit codes 0 to 4.
  • Self-detecting upgrade steps 6.0.15 brings 32 steps, including a 21-step database update written from the kernel schema for every engine. Each step inspects the installation, so work already done by hand shows as not-needed.
  • Code and library stages exp:upgrade:code fast-forwards git checkouts and submodules through git_manager. exp:upgrade:libraries runs composer install from the lock file with composer audit before and after, and refuses local changes.
  • Upgrade captions Before writing anything, exp:upgrade takes a caption: a database dump, var/ storage, settings overrides, Composer files, git commits and a SHA-256 of every file. exp:upgrade:captions lists, verifies and prunes them.
  • Verification after upgrade exp:upgrade:verify --after checks for step drift, smoke URLs, the upgrade-smoke test suite, new fatal log lines and the autoloads. --rollback-on-fail restores the pre-upgrade caption automatically.
  • Rollback to any caption exp:upgrade:rollback restores the database, settings, libraries, checkouts or storage part by part from any caption, after first taking a safety caption so the rollback itself can be undone.
  • Production backup guard --no-backup and --no-caption are refused on production systems unless forced explicitly.
  • Upgrade steps for extensions Extensions register their own upgrade steps with upgrade.ini [UpgradeSettings] ExtensionStepList[].
  • Upgrade check Setup > Upgrade check and checkmanifest.php compare files with the shipped manifest and the database with the shipped schema, table by table with SQL, and download the results as CSV, text or SQL.
  • Migrations in the kernel Timestamped migration files under version control are applied in order on every installation. The kernel records each one in exp_migration and exp_migration_run, mirrored to JSON status files.
  • PHP, YAML, SQL and INI migrations Migrations can be PHP classes with plan, up, down and detect methods, YAML step lists, per-engine .sql files with a down part, MongoDB JSON command files or INI files.
  • 34 YAML step types Shipped step types cover content, location, content_version, content_class, user, role, section, language, object_state_group, tag, url_alias, trash, file, image, cache, search, autoload, layouts, http, mail, command, schema, data, sql, settings, graphql and more.
  • YAML conditions, loops and references Steps support if conditions, foreach and bounded while loops, references between steps and an environment id map, all checked against each step type's schema before anything runs.
  • Portable schema steps The schema step creates and drops tables, columns and indexes written once in the .dba format on MySQL/MariaDB, PostgreSQL, SQLite, Oracle and MongoDB, and does nothing when the work is already done.
  • Migration captions and automatic restore Each run takes a pre caption and restores it after a failure. One migration, a run or any caption can also be rolled back by hand.
  • Migration repository push The record of every run is committed, tagged migrations/environment/run-id and pushed, and the migrationpush cronjob part retries failed pushes.
  • Recording changes as migrations exp:migration:record:start captures one user's or every user's changes at the kernel operation level as YAML steps with remote ids instead of numeric ids, and leaves out personal data.
  • Migration commands exp:migration:status, :migrate, :dry-run (with a simulated diff on PostgreSQL and SQLite), :rollback, :resume, :caption, :push, :check and :generate share exp:upgrade's lock and exit codes.
  • Upgrade steps among the migrations exp:upgrade and migrations share one engine: kernel upgrade steps appear as migrations of the source kernel and run under the same lock and caption.
  • Caches and reindex after migrations A run clears only the caches its steps touched and queues or immediately reindexes the objects it changed. The report names the exact exp:velocity deploy --caches command.
  • Staged remote deploys exp:migration:deploy --staged deploys environment by environment with an approval gate before each stage, all or nothing within a stage, and --rollback takes the deploy back on every remote.
  • Setup > Migrations The administration shows migration status and history, runs dry runs and background runs that it follows live, and handles rollbacks, remotes and deploys, with "Verify it's you" before each risky action.
  • Dry run by default Setup, policy, maintenance, mail, notification, crontab, installer and Velocity configuration commands only show what they would change until --apply is given.
  • exp:ini settings editor exp:ini reads and changes INI settings in every scope line by line, keeping comments and order.
  • config.php from the console exp:config:list, get, set and unset edit define() values of config.php as PHP tokens without running the file. Each write is typed, backed up, checked with php -l and has secrets masked.
  • Setup files from the console exp:setup:htaccess, exp:setup:config and exp:setup:status copy the shipped .htaccess and config.php templates into place with diffs, backups and atomic renames.
  • Install in one command ./console exp:install --apply installs a site on any of the five engines with setup and kickstart logs. The Kickstarter installs from kickstart.ini.
  • Maintenance mode bin/php/maintenance.php, exp:maintenance and Setup > Maintenance take the public site offline with a 503 page and an optional message and end time.
  • One-command deploy exp:velocity deploy regenerates autoloads, settings and caches and reloads PHP-FPM and Velocity in one ordered run, stopping at the first failure. It skips needless PHP-FPM reloads and warms URLs in the background.
  • Server control commands exp:webserver, exp:frankenphp and exp:solr start, stop, restart, gracefully reload, configure and inspect the web server engines and an optional Solr server.
  • Cronjob console Setup > Cronjobs runs a cronjob part or a single script from the browser and shows its live output.
  • Pausing cronjob parts Single parts or all parts can be paused with a note during a release. runcronjobs.php skips them however it is started.
  • Installer-written crontab New installations get crontab lines for the queue, imports, notifications and search index, and installcrontab.php --add --apply adds them to existing installations.
  • User management from the console 24 exp:user commands list, create, edit, disable, delete, import, export, bulk-change and approve accounts and manage groups, roles, sessions and second factors. Every change goes through the same kernel paths and audit events as the administration.
  • Log commands ./console exp:logs lists, tails, follows, searches, rotates and prunes logs with masking.
  • Content check commands exp:content-check finds unreferenced objects, broken relations, storage files with wrong permissions and missing files, and can quarantine them.
  • Access check command exp:access:check tells whether a user may read, edit or remove a node or object, and which policy and limitation refused it.
  • Package manager CLI ezpm installs content packages with a lock, delayed indexing, batched commits and progress. It also exports, converts, validates and checks JSON packages and installs content as drafts.
  • Static publishing commands exp:static:targets, build, diff, serve, publish, rollback, push, keys, status and github build a front siteaccess as static files and publish it to git.
  • URL map commands exp:url:import, export, batches and undo move URL aliases, wildcards and redirects in bulk. exp:url:from-sitemap, from-404, suggest and test build and check a map when a site moves.
  • Notification and mail commands exp:notification:status, run, events and subscriptions and exp:mail:status, preferences, suppression, consent and gate manage notifications and the mail gate from the shell.
  • Content job command bin/php/expcontentjob.php lists jobs with heartbeat age and resumes stalled or failed jobs in the background.
  • Repair from the browser A page for missing Composer libraries repairs the installation from the browser with exprepair.php.
  • CI on every supported PHP The Quality workflow lints every file with PHP 7.4 and 8.0 and runs production installs and boot smoke tests. Database tests run against MySQL 8.0, PostgreSQL 15 and MongoDB 7 services.
APIs, integration and delivery 42 features

Exponential exposes its content through REST, GraphQL, SOAP, WebDAV and remote services, publishes to static hosts, and moves packages, URL maps and data between systems.

  • REST API v1 and v2 index_rest.php serves reads at /api/ezp/v1 and writes at v2, with create answering 201 and delete accepting DELETE.
  • REST permission checks Every REST read, create, edit and remove is checked like the content module does it, for OAuth tokens, API keys, basic authentication and anonymous users. Refusals are 403 access_denied with the policy named.
  • Correct REST routing and caching The router answers 405 with an Allow header only when no route takes the method. The REST answer cache keeps one entry per user for GET and HEAD only.
  • Personal API keys Users with apikey/create make named, scoped, expiring expk_ keys that are shown once and stored as salted HMAC-SHA-256 hashes, with a per-key APCu rate limit. Setup lists and revokes every key.
  • CORS for REST rest.ini [CorsSettings] adds an exact-origin allowlist with methods, headers, max age and credentials. Preflights are answered without running the request, and CORS is off by default.
  • OAuth with PKCE and state The authorization code flow supports PKCE (RFC 7636) with S256 and returns state unchanged. Public clients must use PKCE, and codes and refresh tokens are redeemed only by their own client.
  • OAuth token lifetimes and sources Refresh tokens expire after RefreshTokenTTL (30 days by default), tokens are read from the Authorization header, and tokens in the query string are off unless allowed.
  • API under a path An installation served below a path, such as an Apache Alias, answers REST and GraphQL there, and REST links use https behind proxies.
  • GraphQL API from the content model /api/graphql generates a type per content class with node, content, children, currentUser, siteaccess and translations queries. It supports cursor pagination, image variations, rich text as HTML, text, XML or excerpt, and relations.
  • GraphQL limits and introspection control MaxDepth, MaxComplexity and list limits are checked before a query runs. Introspection is for signed-in requests by default, and classes, fields and datatypes can be hidden.
  • GraphQL persisted queries Queries are stored on the server and called by name or SHA-256, Apollo automatic persisted queries are supported, and a persisted-only mode is available. exp:graphql:persist checks and stores .graphql files.
  • GraphQL response cache Persisted query answers are cached per siteaccess, schema, rights and variables, with ETag and 304. Cached GET answers measured a median of 1.1 to 1.7 ms against 93.0 ms uncached.
  • GraphQL rate limits Signed-in users or keys get 600 requests and anonymous IP addresses 120 per 60-second window by default. Over the limit the answer is 429 with Retry-After and X-RateLimit headers.
  • GraphQL batch loading A DataLoader-style batch loader reads owners, parents and relations per level. 50 articles with image, owner and address cost 11 SQL statements instead of 249.
  • GraphQL search, tags and layouts The search query uses the kernel search or Solr with facets. Tags and page builder layouts get their own queries while eztags or explayouts are active, and extensions add schema through SchemaExtensionList[].
  • GraphQL mutations createContent, updateContent, translateContent, publishDraft, deleteContent, moveContent, hideContent, revealContent, addLocation, uploadImage, uploadFromUrl and createPreviewToken check the user's policies and run the kernel's workflows. Every mutation is audited.
  • GraphQL file uploads and preview tokens Files upload through the GraphQL multipart spec with size limits and a virus-scanner hook. Signed preview tokens let viewers read drafts without signing in for a limited time.
  • GraphQL on in one command exp:graphql:enable checks the schema, switches the API on per siteaccess, sets the CORS origin, creates an API key and prints a curl line. Setup > GraphQL has a playground.
  • GraphQL starter kits exp:graphql:starter generates a front end in plain HTML, Next.js, Nuxt 3, Astro or React Native with Expo, with queries per content class checked against the schema.
  • Signed webhooks Content events are POSTed to configured endpoints with an HMAC-SHA-256 signature and a timestamp against replays, retried with back-off and logged. Signing secrets live in the secret store.
  • GraphQL subscriptions /api/graphql/subscribe streams content events over graphql-sse on PHP-FPM and Velocity, and over graphql-transport-ws WebSockets on Velocity. Each event is checked against the subscriber's rights.
  • Migrations through the APIs GraphQL queries and REST routes under /api/migration/v1 read migration status and runs for users with migration/read. Migrations can run GraphQL queries and mutations in process.
  • SOAP entry script The SOAP server is index_soap.php, named like the other front controllers, and soap.php remains as a shim.
  • SOAP over internal TLS eZSOAPClient::setCAFile() trusts an internal certificate authority for HTTPS services. Without curl, HTTPS calls are refused instead of being sent in plain text.
  • WebDAV on PHP 8 WebDAV is served by index_webdav.php on a maintained component fork with working PROPFIND, LOCK and UNLOCK, and checks what each request may do.
  • Remote services expservices offers about 1,100 remote services over ezjscore with personal API tokens. A service flagged ai can also be served as an MCP tool, with the caller's permissions.
  • Static publishing to GitHub Pages A front siteaccess is crawled as the anonymous user, cleaned of debug output, form tokens and sessions, its links rewritten, and written with 404.html, robots.txt, sitemap.xml and a manifest.
  • Publishing builds to git exp:static:publish commits only the build's files, adds tags that are never moved and pushes without force. Sign-in uses a secret-store token, a per-target SSH deploy key or host credentials, and rollback is a new commit.
  • GitHub setup from the console exp:static:github creates the repository, configures GitHub Pages from a branch or Actions with a custom domain and HTTPS, and signs in through the device flow.
  • Dynamic features on static sites Static builds get their own search page and index, information collectors that post to a signed form endpoint on the live site, redirect pages for old addresses, and minify, precompress and fingerprint options.
  • Automatic static republishing Targets can publish after content publishes or on a schedule through the staticpublish cronjob part, then send an e-mail and a signed webhook.
  • JSON package format Packages can be kept as package.json with JsonML documents, a JSON Schema and SHA-256 checksums, and convert to and from XML without loss.
  • Install packages as drafts The install-as-drafts option turns every package object into a draft without publishing, with a conflict report by remote id.
  • Package compare and selective import package/compare browses a package's contents and imports parts of it selectively, with licenses and Semantic Versioning for packages.
  • URL map import and export URL aliases, wildcards and redirects import and export as CSV, JSON, .xlsx, .ods and Apache or nginx rules. Each import is planned row by row, applied in one transaction and can be undone exactly.
  • Query-string and temporary redirects The exp_url_redirect table answers old addresses with queries and 302, 303, 307 or 308 redirects before URL aliases are resolved, also under Velocity.
  • Data synchronization with content expDataSync maps data table columns to content attributes once, on a schedule or live, one way or both ways, with conflict rules and a page of open conflicts.
  • Module table wizard Setup > RAD > Module table generates a data table extension with a persistent class, install SQL for every engine, list, edit and JSON views, policies and fetch functions.
  • Database search and Solr The kernel's own search answers by default, and exp:solr starts, stops and pings an optional local or remote Solr server.
  • Mail transports eZMail sends through sendmail, SMTP or file transports. It adds SendmailEnvelopeSender for msmtp, a site-wide UserAgent, TransportAuthMethod, and SMTP failures that are logged instead of crashing.
  • HTML mail layout Account, preference, order and notification mails are HTML with a plain-text part in one shared layout with a button, a code field, a preheader and dark-mode colors.
  • Signed links and mail in migrations The http, mail and command YAML steps send one signed HTTP request, one e-mail or one allowlisted exp console command per step, and each is audited.
Security and compliance 38 features

Exponential ships secure defaults, from a configurable Content Security Policy and an encrypted secret store to passkeys, a tamper-evident audit trail and consent-aware mail.

  • Content Security Policy modes site.ini [ContentSecurityPolicy] Mode is disabled, report-only, enforce or auto. Auto is report-only on administration siteaccesses, and the shipped policy uses 'self' with object-src 'none'.
  • CSP nonces and extra sources Nonce=enabled adds a per-request nonce, renewed in persistent workers and printed with csp_nonce(). AdditionalSources[] and ReportOnlyDirectives[] add hosts and a stricter companion policy, and rolling back takes one setting.
  • CSP violation reports The csp/report view accepts both report formats and writes var/log/csp.log with size limits, per-client and total rate limits and masked lines.
  • No inline scripts in the administration The administration runs without inline scripts, handlers, styles or javascript: URLs, so it can work under an enforced policy.
  • Security headers on every page Default headers are X-Content-Type-Options nosniff, X-Frame-Options SAMEORIGIN, Referrer-Policy strict-origin-when-cross-origin and a restrictive Permissions-Policy. HSTS is optional and only sent over HTTPS.
  • Trusted proxies only Forwarded headers are believed only from [HTTPHeaderSettings] TrustedProxies[] (IPv4 and IPv6 ranges). A visitor can no longer fake HTTPS, the host or the client IP.
  • Encrypted secret store Secrets are encrypted with XChaCha20-Poly1305 in exp_secret, with the key in EXP_SECRET_KEY or a key file outside the database, plus key rotation. Tools keep only secret names.
  • One secret masking rule expSecretRule masks secrets the same way in exp:ini, the audit log, the settings pages and the system report, including passwords inside DSN addresses.
  • Form tokens compared in constant time ezxFormToken compares tokens with hash_equals() and accepts the X-CSRF-Token header. Expired forms get a dedicated 403 page.
  • SVG sanitizing on upload An allowlist sanitizer strips scripts, event attributes, external references and unsafe CSS, and refuses XXE, billion-laughs and oversized files. SVGs are served with a sandbox CSP.
  • Package archive scanning Package tar archives are scanned header by header with entry and size limits before they are opened. Set-uid and world-writable modes are masked, and package XML loads without network access.
  • Safe URL fetching getDataByURL() fetches only absolute http and https addresses, refuses redirects to file:// or gopher://, and treats error statuses as no data.
  • Dangerous upload extensions refused file.ini FileExtensionBlackList[] refuses php, phps, shtml, cgi, pl, asp, aspx, jsp and htaccess uploads by default.
  • Private settings files Settings saved from the admin are created 0640, keep their owner and are never world-writable. New settings directories are 0755 instead of 0777.
  • Weak password check New passwords are checked against a list of well-known passwords and their variants and keyboard patterns everywhere passwords are set. Forgot-password links expire after one hour by default.
  • Secure random everywhere Generated passwords, reset keys, REST tokens and stored file names come from random_int() and random_bytes() instead of md5 and mt_rand.
  • Passkeys with built-in WebAuthn Users add passkeys on My account and sign in with them. The kernel verifies WebAuthn itself, including ES256, RS256 and Ed25519 signatures.
  • Verify it's you Sensitive actions in five groups ask for re-authentication with a password, passkey or authenticator code, valid for 10 minutes by default.
  • Second factor on other sign-in paths Sites can make REST, SOAP, WebDAV and expservices refuse password-only sign-in for Enforce2FA accounts.
  • OAuth token hardening Disabled or locked users lose REST access immediately, refresh tokens expire, client matching is constant-time, and authorizing a client needs the oauth/authorize policy.
  • Fail-closed permissions A user without content/read, or whose access array cannot be read, gets a condition that matches no node instead of seeing everything.
  • Your devices Every signed-in session is listed with browser, host, second step and an optional local GeoIP place. Users can sign other sessions out.
  • Security activity and alerts A per-account timeline shows sign-ins and changes, with "Was this you?" and "Secure your account". Alert mails go out for 2FA changes, recovery codes, failed sign-in thresholds and lockouts.
  • Sign-in report Users > Sign-in report shows running sessions, failures over 14 days and suspicious activity, and can sign a user out everywhere.
  • Sign-in data export and erasure Users can download their sign-in data as JSON, and removing an account erases its sessions and their details.
  • Tamper-evident audit trail A hash-chained, signed, searchable record of sign-ins, content, settings, cache clears, commerce and deploys is on by default, with alert rules for brute force or mass deletes.
  • Audit sinks and archives Records go to syslog or journald, a signed webhook or e-mail. Archives are compressed in five formats with HMAC-signed manifests, and exp:audit verify detects edits.
  • User audit log expuser_audit keeps every security event about accounts and groups (actor, place, target, result, before and after) and never stores secrets. It has CSV export and retention.
  • Request classifier and security log Probes, path traversals, injections, attack tools and 404 floods are classified into var/log/security.log with INI rule sets and extension hooks.
  • Request rules requestrules.ini can allow, deny, redirect, rewrite or log requests after URL alias translation, for example to hide /content/view/full system URLs.
  • Safe redirects Every redirect target from a form, the session or a URL parameter passes one set of rules in eZRedirectManager, and tracking queries are carried only to targets on the own host.
  • Mail gate and e-mail preferences Optional mail goes only to people who opted in, with one-click unsubscribe per RFC 8058, double opt-in and a checklist covering CAN-SPAM, GDPR, CCPA and CASL.
  • Consent log and suppression list Every consent change is logged with the exact text shown. Suppressions, including hard bounces, are stored as salted hashes, and links are encrypted with AES-256-GCM.
  • Mail header injection protection The mail fork refuses addresses with whitespace or address separators, and sendmail gets -f only for shell-safe addresses.
  • Masked logs by default The log viewer masks e-mail addresses, IP addresses, passwords, tokens and cookies. Unmasking needs setup/unmasklogs, and every read and download is audited.
  • No secrets on the system card exp:expfetch never prints passwords, keys, tokens, database users or DSNs, and a central filter drops or masks them for every provider.
  • Velocity HTTPS safety Velocity never serves a broken or expired certificate and sends HSTS only when HSTSMaxAge is set. It serves only allowed file extensions, so stray .env or .sql files are not downloadable.
  • Supply chain checks Dependabot covers Composer, npm and GitHub Actions, CodeQL scans the JavaScript, and upgrades run composer audit before and after the library stage.

The Exponential family: a path forward from every version

eZ Publish, eZ Platform and Ibexa sites were never meant to become dead ends. 7x keeps a maintained line for every generation of this software, so a site moves forward from the version it runs today, one supported step at a time, instead of being rebuilt.

current maintained archive (available) beta

github.com/se7enxweb/exponential

Exponential 6

The original kernel, continued: the CMS behind this site.

Supported version points

  • 6.0.15 (main) PHP 7.4 to 8.5 current
  • 6.0.14 PHP 8.1 to 8.5 current
  • 6.0.13 PHP 8.1 to 8.5 maintained
  • 6.0.12 PHP 8.1 to 8.5 maintained
  • 6.0.11 PHP 8.1 to 8.5 maintained
  • 6.0.10 PHP 8.1 to 8.5 maintained
  • 6.0.7 to 6.0.9 PHP 7.4 to 8.2 archive

For you if you run

  • eZ Publish 3.x and 4.x sites
  • eZ Publish 5.x legacy sites that never used the Symfony stack
  • Earlier Exponential 6.0 releases

How you move

  1. Back up the database and the var/ storage; exp:upgrade makes its own backup too.
  2. Build the new release beside the old tree with Composer; keep settings, designs and extensions.
  3. Run the database upgrade (exp:upgrade, dry run first): recorded steps, additive for 6.0.
  4. Packages from the 3.x, 4.x and 5.x lines import as they are.
  5. Switch the trees in one step; no downtime, rollback by switching back.
Source and releases on GitHub

github.com/se7enxweb/exponential-platform-legacy

Exponential Platform Legacy

Exponential Platform with Exponential (Legacy) included, now with SQLite.

Supported version points

  • 5.x (v5.0.3.8) PHP 8.3+ current
  • 4.6.x PHP 7.4 to 8.5 maintained
  • 3.x PHP 8.0+ maintained
  • 2.5 (master) PHP 7.1.3 to 8.x maintained
  • 2.0 and 2.2 PHP 7.1+ archive
  • 1.7 to 1.13 PHP 5.6 / 7.0 archive

For you if you run

  • eZ Platform 1.x, 2.x and 3.x sites, with or without the legacy bridge
  • eZ Publish 5 sites that run both kernels
  • Ibexa 3.3 and 4.x projects that want the legacy kernel back

How you move

  1. Pick the branch of your current major version, then move up one major line at a time.
  2. Each line keeps the legacy kernel, so legacy templates and content keep working during the move.
  3. Database: the platform's own migrations plus the Exponential upgrade steps.
  4. Start fresh from the Platform Legacy Starter (EPLSD) when a clean install is easier.
Source and releases on GitHub

github.com/se7enxweb/exponential-platform-nexus

Exponential Platform Nexus

The media site with Exponential Layouts and SQLite, on Platform DXP 5; versioned by 7x in the lines 1.0.0.x to 1.3.0.x.

Supported version points

  • 1.3.0.x (1.3.0.11): DXP 5, Symfony 7.4, Layouts 2, SQLite PHP 8.4 to 8.5 current
  • 1.2.0.x (v1.2.0.5): Platform v4, Symfony 5.4 PHP 8.2 to 8.5 maintained
  • 1.1.0.x (v1.1.0.14): Platform v3 with the legacy kernel, Symfony 5.4 PHP 8.0 to 8.5 maintained
  • 1.0.0.x (1.0.0.11): Platform Legacy, Symfony 3.4, Layouts 1 PHP 7.1 to 8.5 archive

For you if you run

  • Sites on eZ Platform or Ibexa with the Netgen Media Site
  • Projects that want Layouts, the Symfony kernel and the legacy kernel together

How you move

  1. Start from the Nexus Starter (EPNSD) or the branch of your current version.
  2. Layouts, the media site and both kernels come preconfigured; carry over content and designs.
  3. Symfony 3.4, 5.4 and 7.4 lines are covered, so the move can follow your current Symfony version.
Source and releases on GitHub

github.com/se7enxweb/exponential-platform-dxp

Exponential Platform DXP

The freedom-enabled Ibexa DXP OSS, maintained by 7x.

Supported version points

  • 5 (skeleton v2.0.0.5, Ibexa DXP OSS 5.0.6) PHP 8.3+ current
  • 4.6 (skeleton v1.0.0.5) PHP 7.4 to 8.5 maintained
  • 4.0 to 4.5 PHP 7.4 / 8.0 archive
  • 3.3 PHP 7.3 / 8.0 archive

For you if you run

  • Ibexa OSS 3.3, 4.x and 5 projects
  • Ibexa DXP projects leaving a subscription for free software

How you move

  1. Install the skeleton of your major version (4.6 or 5) and point it at your database.
  2. Your Symfony bundles and Twig templates stay; the admin UI, REST, GraphQL and search are included.
  3. Move from 4.6 to 5 when ready; 4.6 stays maintained meanwhile.
Source and releases on GitHub

github.com/se7enxweb/exponential-starter

Starter distributions

Ready-to-run installations of each product, tuned for SQLite.

Supported version points

  • Exponential Starter (ESD) 1.0.0.7 PHP 8.1 to 8.5 current
  • Platform Legacy Starter (EPLSD) 1.0.0.2 PHP 8.3+ current
  • Platform Nexus Starter (EPNSD) 1.0.0.1 PHP 8.4+ current
  • Platform DXP Starter (EPDSD) 1.0.0.0 PHP 8.3+ current

For you if you run

  • New projects and evaluations
  • A clean target to import an old site's content into

How you move

  1. Clone, install, open the site: no database server needed to start.
  2. Import content from the old site with packages and the import tools.
Source and releases on GitHub

github.com/se7enxweb/exponentialbasic

Exponential Basic

The simple CMS for everyone: education, personal sites and more, maintained by 7x.

Supported version points

  • 2.4.0.5 PHP 8.2 to 8.5 current

For you if you run

  • eZ Publish 2.x sites and their data

How you move

  1. Install the current release from the repository; its database runs on MySQL, PostgreSQL or SQLite.
Source and releases on GitHub

You run today, you move to

You run today Move to Start from
eZ Publish 2.x Exponential Basic 2.4.0.5 (current)
eZ Publish 3.x or 4.x Exponential 6 6.0.15, in place
eZ Publish 5.x, legacy site only Exponential 6 6.0.15, in place
eZ Publish 5.x with both kernels Platform Legacy or Platform Nexus Legacy 2.5; Nexus 1.0.0.x
eZ Platform 1.x Platform Legacy or Platform Nexus Legacy: your 1.7 to 1.13 branch, then up; Nexus 1.0.0.x
eZ Platform 2.x Platform Legacy or Platform Nexus Legacy 2.0, 2.2 or 2.5; Nexus 1.0.0.x
eZ Platform 3.x / Ibexa 3.3 Platform Legacy, Platform DXP or Platform Nexus 3.x / 3.3; Nexus 1.1.0.x
Ibexa OSS or DXP 4.x Platform DXP, Platform Legacy or Platform Nexus 4.6 / 4.6.x; Nexus 1.2.0.x
Ibexa OSS or DXP 5 Platform DXP, Platform Legacy or Platform Nexus 5 / 5.x; Nexus 1.3.0.x (current, Layouts and SQLite)
Anything else on this page A starter distribution then import your content

Open source CMS

Coming from WordPress

Posts and plugins, until the site needs structure, roles and languages.

What you deal with on WordPress: how it limits your freedom

  • You build it yourself: Structured content types, typed fields, multilingual content, workflows and fine-grained roles each mean choosing, buying, integrating and keeping compatible another plugin, or writing the feature yourself.
  • The core content model is posts and pages; typed fields come from plugins that store values as rows of post meta.
  • Multilingual sites, workflows and fine-grained permissions depend on third-party plugins.
  • Most published WordPress vulnerabilities are in plugins and themes, so security depends on many separate vendors.
  • Runs on MySQL or MariaDB only.
  • The administration is served from the public host (/wp-admin, /wp-login.php), and public pages call /wp-admin/admin-ajax.php, so it cannot simply be closed off.
  • WPML, a common way to add multilingual content, is a paid plugin sold with one year of updates; without renewal it keeps working but can no longer be updated. source
  • With Polylang, translating a WooCommerce shop needs the separate paid add-on Polylang for WooCommerce. source
  • Plugin and theme translations are done by volunteers on translate.wordpress.org; a language pack is only built once at least 90% of the strings are approved. source
  • Only the latest WordPress version is officially maintained; security fixes reach older branches only when possible. source
  • Plugins removed from the WordPress.org directory for security reasons are not flagged to the sites using them; 1,614 plugins and themes were removed for unpatched issues in 2024. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Content classes with typed fields are the core of Exponential, not an add-on.
  • Translations, versions, drafts, workflows and roles with limitations by subtree, section and class are built in.
  • Runs on MySQL/MariaDB, PostgreSQL, SQLite, Oracle or MongoDB.
  • Separate editor and administration portals on their own host names, each behind a web server password (7x Security Recommendation #1).
  • sevenx_classes installs 33 general content classes, such as article, folder, image and product, so a new site starts with a structured model instead of posts and meta rows.
  • 219 locales from Unicode CLDR 44 ship with the kernel, and ./console exp:i18n check verifies every translation fallback chain.
  • Translation state badges show in the node view whether each language is the main one, a translation, missing or outdated.
  • The role page reads every policy as a sentence, and a user who edits roles can only grant what their own access covers.
  • Review hold keeps a page from being edited or published until a reviewer releases it, while visitors keep seeing the published version.
  • Passkeys, two-step sign-in and Verify it's you are part of the kernel, and new installations require two-step sign-in for Editors and Administrators.
  • The tamper-evident audit trail, the encrypted secret store and the Content Security Policy modes come with the kernel, not from separate vendors.
  • SVG uploads pass an allowlist sanitizer, and FileExtensionBlackList[] refuses php, cgi, jsp and htaccess uploads by default.
  • In the Editor siteaccess, setup, class, role and the other administration modules answer 404, so writers never reach site administration.
  • Exponential Layouts ships 46 block types and 15 site layout types, and prioritized rules choose the layout by path, subtree, class or siteaccess.
  • SQLite is the setup wizard's default, so a complete site runs from one file with no database server to install or secure.
  • ./console exp:upgrade --apply backs up first, runs every stage in order and stops at the first failure, and exp:upgrade:rollback restores any caption.
  • The role-aware HTTP cache stores pages per permission context, so a thousand members share one copy of each page.
  • A GraphQL API is generated from your content classes, with persisted queries, rate limits and mutations that run the kernel's workflows.
  • The website sidebar lets editors type on the live page, schedule publishing and take-down, and run SEO and WCAG 2.2 AA checks in place.
  • content/urlimport imports a URL map from CSV, JSON, xlsx or Apache and nginx rules with a row-by-row preview, and the whole import can be taken back.
Back to the overview

Coming from Drupal

Powerful, but each major line has meant a migration project.

What you deal with on Drupal: how it limits your freedom

  • You build it yourself: A real site means choosing, configuring and patching dozens of contributed modules plus custom modules and a theme, and every major upgrade repeats part of that work.
  • Moving from Drupal 7 to 8 and later was a rebuild and content migration, not an upgrade in place.
  • Drupal 7 reached its end of life in January 2025, leaving many sites to migrate.
  • Modern Drupal brings the full Symfony, Composer and configuration management stack to every project.
  • The login and administration (/user/login, /admin) answer on the same host as the public site.
  • Drupal 10 reaches its end of life on December 9, 2026, so Drupal 10 sites have to move to Drupal 11. source
  • Each major version reaches end of life in early December of the fourth year after its release, so a major upgrade is due on a fixed cycle; Drupal 11 ends in early December 2028. source
  • Security advisories cover only stable releases of contributed projects that opted in; dev, alpha, beta and sandbox projects are not covered. source
  • Interface translations of core and every contributed module come from community language teams on localize.drupal.org, where suggestions wait for approval. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Exponential upgrades sites of its own line in place, back to installations started on the original kernel.
  • One kernel, one settings system, one upgrade command (exp:upgrade) with backup, dry run and rollback.
  • The administration can live on an internal host that the public internet never reaches.
  • Before writing anything, exp:upgrade takes a caption: a database dump, var/ storage, settings overrides, Composer files and a SHA-256 of every file.
  • exp:upgrade:verify --after checks smoke URLs and new fatal log lines, and --rollback-on-fail restores the pre-upgrade caption automatically.
  • The 6.0.15 upgrade brings 32 self-detecting steps, and work already done by hand shows as not-needed.
  • Extensions register their own upgrade steps in upgrade.ini, so add-ons move forward with the same command as the kernel.
  • [ConfigurationSettings] ManagedByDeployment locks a siteaccess's configuration to version control, and the admin editors stop writing files.
  • settings/view shows each setting's effective value, source file and whole override chain, and exp:ini edits any scope keeping comments and order.
  • Timestamped migrations in PHP, YAML, SQL or INI apply in order on every installation, with 34 YAML step types and automatic restore after a failure.
  • The Editor portal gets its own address, by default edit.yourdomain.com, and closes setup, class, role and workflow modules with a 404.
  • Content Security Policy modes run from report-only to enforce, and the administration has no inline scripts, so it works under an enforced policy.
  • PHP 8.0 to 8.5 are supported, and CI lints every file with PHP 8.0 and boot-tests every kernel and extension class.
  • Exponential Layouts brings a drag-and-drop page builder with drafts and publishing, usable by mouse, touch, pen or keyboard.
  • Preview links give outside reviewers a signed, expiring and revocable view of one draft without an account.
  • content/urlimport brings a URL map over from CSV, JSON or nginx rules with a preview first, so old addresses keep answering after a move.
Back to the overview

Coming from Joomla

Major versions that leave extensions and templates behind.

What you deal with on Joomla: how it limits your freedom

  • You build it yourself: Beyond articles and categories, structured content, page layouts and integrations come from third-party extensions or custom components your team builds and maintains.
  • Major upgrades such as 3 to 4 required extensions and templates to be rewritten or replaced.
  • Joomla 3 reached its end of life in August 2023.
  • Structured content beyond articles relies on custom fields or extensions.
  • The administrator application (/administrator) answers on the public host of every Joomla site.
  • Joomla 4 security support ended on October 14, 2025; Joomla 5 active support ended in October 2026, with security fixes until October 12, 2027. source
  • Joomla 6 needs PHP 8.3 and MySQL 8.0.13 or newer; on an older server the upgrade option does not appear at all. source
  • The official Joomla 6 upgrade guide warns that an incompatible extension makes the upgrade unsuccessful, and that Joomla 5 extensions will not be kept compatible through the plugin in Joomla 7. source
  • Fewer accredited language packs exist for current versions: 84 for Joomla 3.x, but 66 for Joomla 6.x. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Exponential keeps its template and extension APIs stable across releases; 6,547 extension points are surveyed in every installation.
  • Structured content classes are core, with any number of fields per class.
  • Editor and administration portals are separate siteaccesses on their own host names.
  • Twig 3 and Smarty 5 templates sit next to .tpl in the same design, with overrides, includes and caching like any template.
  • Five ezpEvent filters let extensions take part in view cache keys and access checks without patching the kernel.
  • Content limitation handlers let extensions add their own policy limitations, and a missing or faulty handler fails closed.
  • Setup > RAD lists 68 extension points, 64 of them with a wizard that shows every file before it writes an extension.
  • Setup > Extensions shows each extension's version, license, dependencies and loading position, and every reorder goes through Review changes.
  • Generic full, line, listitem and embed views render every content class in the media design without a template or override rule.
  • sevenx_classes installs 33 general content classes, and the demo content package adds 31 site classes for both demo websites.
  • exp:upgrade runs its code, libraries, database, scripts and finish stages as separate commands too, with exit codes 0 to 4 for scripts.
  • Passkeys and two-step sign-in protect both portals, and Verify it's you asks again before user, role, setting and delete actions.
  • Each extra language chosen in setup becomes its own siteaccess, and translation badges flag missing or outdated translations.
  • Exponential Layouts fills blocks from 12 query types, including children, subtree, latest, relations, tags and search.
  • Setup > Upgrade check compares every file with the release checksum list and gives the SQL to fix each schema difference.
  • The setup wizard needs privileges on your own database only, so it runs on shared hosting.
Back to the overview

Coming from TYPO3

TypoScript and LTS jumps that need extension rework.

What you deal with on TYPO3: how it limits your freedom

  • You build it yourself: Content elements, page templates and extensions are developed per project in TypoScript, Fluid and Extbase, usually by a specialist agency.
  • Rendering is configured in TypoScript, a configuration language of its own to learn.
  • Moving between LTS versions often requires extensions to be updated or replaced.
  • Each LTS version gets three years of free support; after that, security updates come only through paid Extended Long Term Support (ELTS). source
  • Free community support for TYPO3 12.4 ended on April 30, 2026; staying on it with security updates requires ELTS. source
  • The roadmap describes LTS versions as fully supported for 1.5 years, then receiving only security and critical fixes. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Templates are plain template files with a small, documented language; Twig and Smarty siteaccesses are available too.
  • Releases are immutable and every change is in the changelog, so upgrades are planned, not discovered.
  • Design > Template Editor creates, orders by priority and changes template override rules without touching INI files.
  • Adding content/views/view/class.tpl is all a class needs for its own look; no override.ini rule is required.
  • A converter turns a whole .tpl design into Twig and back, and another ports a .tpl design to Smarty.
  • Setup > Extensions reviews every reorder before it is written, and the RAD health check names settings that point at something that cannot load.
  • exp:upgrade:verify --after runs the upgrade-smoke test suite and can roll back to the pre-upgrade caption on failure.
  • PHP 8.0 to 8.5 are supported, and the PHP floor metapackage lets Composer pick the extension releases that run on your PHP.
  • 219 locales and right-to-left text direction are in the kernel, including locales for 22 Indigenous languages of the Americas.
  • Editors click a title or text on the live page through the website sidebar, type, then publish now or at a date.
  • settings/view shows each setting's effective value, its source file and whole override chain, and compares a file between two siteaccesses.
Back to the overview

Coming from Concrete CMS

In-page editing first, structured content second.

What you deal with on Concrete CMS: how it limits your freedom

  • You build it yourself: Anything beyond the shipped blocks and page types is built as custom packages, blocks and single pages for each project.
  • Built around in-page block editing; complex structured content and large editorial teams need custom work.
  • Major version changes (5.x to 8 and 9) required add-ons and themes to be redone.
  • Security fixes are provided only for version 9; no further security patches will be released for version 8. source
  • Concrete versions below 9 cannot run on newer PHP versions. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Exponential Layouts gives editors a block page builder on top of a structured content repository, not instead of it.
  • The website sidebar edits text on the live page, while content classes, versions and translations stay structured underneath.
  • Large teams get a separate Editor siteaccess with a ready-made Editor role, while setup, classes and roles stay with administrators.
  • Review hold and My pending items show what waits for approval, with the approval state, approvers and workflow.
  • Two editors on one page share a soft lock, and their changes merge field by field.
  • Resumable content jobs move, copy or hide big subtrees in batches and resume where they stopped, even after kill -9.
  • The user audit log and the tamper-evident audit trail record who did what across the whole team.
  • exp:upgrade moves a site forward in place with rollback to any caption, and extensions bring their own upgrade steps.
  • Shared layouts link one header or footer zone into many layouts, and rules pick the layout per subtree or content class.
  • Layouts, shared layouts and rules export to a versioned ZIP and import with a dry-run diff, arriving as drafts.
Back to the overview

Coming from October CMS

A free CMS that moved to a paid license.

What you deal with on October CMS: how it limits your freedom

  • You build it yourself: Most site features come from plugins or are written per project as custom plugins in PHP on Laravel.
  • Since version 3 (2022) October CMS requires a paid license.
  • It is a Laravel application, so its life cycle follows Laravel's.
  • Without license renewal there is no access to the Update Gateway, which is needed for updates and for downloading any version, including earlier ones. source
  • Each website needs its own license; a multisite installation serving unrelated websites needs one license per site. source
  • Content translation came from the separate RainLab.Translate plugin; since v3.1 a core multisite feature supersedes many of its functions. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Exponential is GNU GPL version 2 or later, free for everyone, for good.
  • The kernel's own release line decides its life cycle.
  • Since 6.0.15 the Velocity application server is part of Exponential and installed by composer install.
  • All 21 Zeta Components are forked as expcomponents under the Apache License 2.0 and tested on PHP 7.4 to 8.5.
  • PHP 8.0 to 8.5 are supported, and PHP 7.4 still installs for sites that cannot change their server PHP yet, without a support commitment.
  • The kernel has its own compiled service container in kernelservices.ini, with exp:services commands to compile, list and check it.
  • exp:upgrade with captions, verification and rollback moves sites forward on the kernel's own schedule.
  • New content classes need no view code: generic full, line and embed views render every class in the media design.
  • One install command sets up SQLite by default, with MySQL, PostgreSQL, MongoDB or Oracle as options.
  • Passkeys, two-step sign-in and a hash-chained audit trail are part of the kernel.
Back to the overview

Coming from ProcessWire

Elegant, with a small core team.

What you deal with on ProcessWire: how it limits your freedom

  • You build it yourself: You get an API and fields; templates, output, user features and most site logic are written by hand in PHP for every project.
  • Development rests on a very small core team.
  • A smaller ecosystem of modules and integrators.
  • Multilingual content needs extra core modules installed, and only text, textarea and page title fields have language versions; other field types need separate per-language fields. source
  • Converting an existing field to a multi-language field changes its database columns, so a backup is recommended first. source
  • Admin language packs come from individual community members; the modules directory lists 14 of them. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Exponential has a foundation, a company maintaining it (7x), public repositories and an open review process for pull requests.
  • Exponential 6.0.15 alone has 3,153 changelog entries, on a product that has grown for more than two decades.
  • Setup > RAD wizards write working design, template operator, datatype, workflow event and module extensions, showing every file first.
  • Exponential Layouts ships 46 block types, and 22 standard block handlers can be swapped in per block through an INI override.
  • About 1,100 remote services expose what the administration does, with a self-describing catalogue to generate typed clients from.
  • Shell and Python clients ship with expservices, and four portal front-end designs run on those services in the browser.
  • CI lints every file with PHP 7.4 and 8.0 and runs database tests against MySQL 8.0, PostgreSQL 15 and MongoDB 7.
  • Dependabot, CodeQL and composer audit before and after the library stage watch the supply chain.
  • The built-in help center opens the help page for the current view, with search and topics for each audience.
  • ./console exp:install --apply installs the multisite package with two websites, 291 demo objects and 21 layouts.
Back to the overview

Coming from Craft CMS

Polished, proprietary and licensed per project.

What you deal with on Craft CMS: how it limits your freedom

  • You build it yourself: No front-end templates ship: every page, listing, search and form is hand-built in Twig, and commerce, forms and SEO are separate plugins.
  • Craft is proprietary software; the Pro edition and plugin licenses are paid per project.
  • MySQL and PostgreSQL only.
  • Each major version gets two years of active support, then one year of critical security fixes; Craft 4 security support ended on April 30, 2026. source
  • Team and Pro licenses include one year of updates; after that, updates need a paid annual renewal. source
  • The Solo edition allows one user account and the Team edition up to five accounts and one user group. source
  • Each language is set up as a separate site, and custom fields keep one value across all sites until each field's translation method is changed. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • GPL license, no fees for the software, any number of sites.
  • Five database engines.
  • SQLite runs a complete site from one file, and MongoDB can hold the whole content repository; Oracle 11g and 12.1 work with ezoracle 2.3.7.
  • The SQL query cache is hooked into the MySQL, PostgreSQL, SQLite and Oracle drivers and answers repeat SELECTs from memory.
  • Named database connections let persistent classes read and write on SQLite, MySQL, PostgreSQL, Oracle, SQL Server or MongoDB.
  • On multi-site installations each site can keep its own logs, INI cache and expiry timestamps.
  • The GraphQL API comes with the installation, and exp:graphql:enable switches it on per siteaccess and creates an API key.
  • Passkeys, Verify it's you and the user audit log protect every account without an add-on.
  • All 21 Zeta Components are maintained as expcomponents forks under the Apache License 2.0.
  • Exponential Intelligence works with Anthropic, any OpenAI-compatible service or a local open-weight model managed from the admin.
Back to the overview

Coming from Statamic

Flat files first, paid Pro edition.

What you deal with on Statamic: how it limits your freedom

  • You build it yourself: Page templates, form output and integrations are built per project on Laravel, and many features need the Pro edition.
  • The Pro edition, needed for multi-user and multi-site features, is paid.
  • Content is stored as flat files by default; large sites move to a database driver.
  • Control panel translations are community contributed, and the documentation says they may be incomplete shortly after an update. source
  • Major versions get one year of bug fixes and 18 months of security fixes; Statamic 5 security fixes end in December 2026. source
  • Roles and permissions, revisions, the REST and GraphQL APIs and Git integration are Pro features; the free Core edition allows one admin user. source
  • On a public domain Pro needs a license key, and the control panel checks in with Statamic's validation service about once an hour. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Multi-user, roles and many sites in one installation are free and core.
  • A database-backed repository from the start, with caches in front of it.
  • The default package installs Fit & Healthy and Bold Agency plus admin, editor and Admin UI siteaccesses in one installation.
  • System information maps every siteaccess with its designs and languages and shows which match rule chose the request.
  • The globe button in the admin header lists the installation's other sites a user may log in to.
  • Policies read as sentences, a ready-made Editor role and editor account approval come with the kernel.
  • Content jobs that meet a busy SQLite database or a MySQL lock wait are rolled back and retried with back-off.
  • The SQL query cache and the role-aware HTTP cache sit in front of the database, and Velocity keeps workers and connections warm.
  • Migrations under version control carry changes between environments, and exp:migration:record:start captures edits as YAML steps.
  • MongoDB can store the whole content repository, with a schema handler and index scripts.
Back to the overview

Headless & SaaS

Coming from Contentful

Your content lives in someone else's cloud.

What you deal with on Contentful: how it limits your freedom

  • You build it yourself: Contentful manages content only: the whole website (rendering, routing, search, forms, user accounts, caching and preview) is a separate application your team builds and runs.
  • SaaS only: the content repository runs in the vendor's cloud and cannot be self-hosted.
  • Plans are limited by spaces, records, users and API calls.
  • Headless: preview, page rendering and site search have to be built and hosted separately.
  • The Free plan includes 2 locales and Lite 3; localized workflows and locale-based publishing are Enterprise features. source
  • A content type is limited to 50 fields and an entry to 2 MB. source
  • The Content Management API allows 10 requests per second per space on paid plans and 7 on Free. source
  • The Free plan has two role types, Admin and Editor; Lite has three roles. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Self-hosted on your own servers, or any hosting; your database, your files.
  • Pages, preview, search and the REST API come with the same installation.
  • ./console exp:install --apply installs a site on your own server, on SQLite by default.
  • GraphQL rate limits default to 600 requests per 60 seconds for users and 120 for anonymous addresses, on your own installation.
  • The version preview shows a draft at iPhone, iPad, Desktop or Large Desktop size, with a landscape switch.
  • The kernel's own search answers by default, and exp:solr starts, stops and pings an optional Solr server.
  • The GraphQL schema is generated from your content classes, with persisted queries, cursor pagination and image variations.
  • Signed webhooks POST content events with an HMAC-SHA-256 signature and a timestamp, retried with back-off.
  • exp:graphql:starter generates a Next.js, Nuxt 3, Astro or React Native front end when you want a separate one.
  • Static publishing pushes a static copy of a site to GitHub Pages or another git host, and every publish is kept so you can go back.
  • The package wizard exports content classes and subtrees, which can be kept as package.json with SHA-256 checksums.
Back to the overview

Coming from Strapi

An API without a site, and enterprise features behind a plan.

What you deal with on Strapi: how it limits your freedom

  • You build it yourself: Strapi is an API back end: the whole website (rendering, routing, search, forms, user accounts, caching and preview) is a separate application your team builds and runs.
  • Headless only: every website needs a separate front end project.
  • The move from version 4 to 5 required a migration of projects and plugins.
  • Single sign-on and some governance features are part of paid plans.
  • Content History is only on the Growth and Enterprise plans, and Growth keeps history for 14 days. source
  • Review Workflows require an Enterprise plan. source
  • Custom locales cannot be created, content is managed one locale at a time, and deleting a locale deletes its content for every content type without undo. source
  • The admin panel ships with English strings; other interface languages must be enabled, and missing strings fall back to English. source
  • Strapi 4 security support ended on June 9, 2026. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Exponential renders the site itself and offers the API as well.
  • Roles, policies and audit are part of the free kernel.
  • The media design renders every content class in full, line, listitem and embed views out of the box.
  • The default package installs two demo websites with 21 published layouts, ready to edit.
  • The hash-chained audit trail has alert rules for brute-force sign-ins, an administrator role being granted and mass deletes.
  • Passkeys, enforced two-step sign-in for staff and OAuth with PKCE are part of the kernel.
  • Personal API keys are scoped, expiring, shown once and stored as salted hashes, and Setup lists and revokes every key.
  • exp:upgrade upgrades in place with backups, a dry run by default and rollback, and extensions ship their own upgrade steps.
  • REST API v1 and v2 and a GraphQL API with mutations are served by the same installation that renders the site.
  • Verify it's you asks for a password, passkey or authenticator code before user, role, export and delete actions.
Back to the overview

Coming from Sanity

A hosted content lake with its own query language.

What you deal with on Sanity: how it limits your freedom

  • You build it yourself: The Studio is configured in code and the content is only an API: the whole website and all its features are a separate application your team builds and runs.
  • Content is stored in Sanity's hosted Content Lake.
  • Queries are written in GROQ, a language specific to Sanity.
  • Usage-based plans.
  • Content localization is modeled in your own schema, usually with plugins; the field-level approach requires publishing all languages at the same time. source
  • The Studio's primary official language is American English; other interface languages are plugins from a community-supported repository, bootstrapped with AI. source
  • Document history is kept for 3 days on Free and 90 days on Growth; older transactions are permanently deleted. source
  • Mutations are limited to 25 requests per second per IP, and a query may run for at most one minute. source
  • Datasets are capped at 10,000 documents on Free and 25,000 on Growth. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Standard SQL databases you run and back up yourself.
  • Templates fetch content with a documented, stable fetch API.
  • Setup > Data tables lists every persistent class with its table and compares each with what the database holds.
  • exp:upgrade takes a caption with a database dump and var/ storage before it writes, and exp:upgrade:captions verifies them.
  • Content is queried through GraphQL generated from your content classes, or through the REST API.
  • Twig 3 templates get every template operator and every fetch function, next to .tpl and Smarty 5 templates.
  • sevenx_dse opens the site database in the administration to browse, query, export and import, behind the dse policy.
  • GraphQL batch loading reads 50 articles with image, owner and address in 11 SQL statements instead of 249.
  • GraphQL subscriptions stream content events over graphql-sse, and over WebSockets on Velocity, checked against each subscriber's rights.
  • The SQL query cache keeps results in APCu or files and reports the estimated database time it saved.
Back to the overview

Coming from Storyblok

Visual editing, SaaS only.

What you deal with on Storyblok: how it limits your freedom

  • You build it yourself: Storyblok manages content only: the whole website, its components, search, forms and user accounts are a separate application your team builds and runs.
  • SaaS only, priced by plan and seats.
  • The visual editor needs a front end you build and host.
  • The Starter and Growth plans include 2 locales and Growth Plus 10. source
  • Custom roles, custom workflows, releases and single sign-on are not available below the Premium plan. source
  • Version history is kept for 1 day on Starter and 30 days on Growth and Growth Plus. source
  • The Management API allows 3 requests per second on Starter and 6 on higher plans. source
  • Uncached delivery requests are limited to 50 per second, falling to 6 per second for listings of 75 to 100 entries. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Exponential Layouts is a visual page builder that runs on your own server, no extra front end.
  • The layout editor moves blocks within and between zones by drag and drop, with a mouse, finger, pen or the keyboard.
  • Each block's sidebar splits its parameters into a Content tab and a Design tab.
  • Time-switched layout rules turn on and off at set times, and query parameter conditions serve A/B variants of one address.
  • A layout can be previewed in a public siteaccess straight from the administration.
  • The website sidebar edits text on the live page and shows device previews side by side, each frame in light or dark.
  • Editors can request a colleague's account, which waits unpublished until an administrator approves it.
  • The calendar panel shows scheduled publications, take-downs and layout variants by month, and moving one reschedules it.
  • The media design ships its own block templates for lists, galleries, columns, buttons and content components.
  • Hero, Features, About, Logos, Quote and Lead component blocks display editor-managed content components.
Back to the overview

Coming from Prismic

Slices you cannot take with you.

What you deal with on Prismic: how it limits your freedom

  • You build it yourself: Prismic manages content only: the whole website, its slices, search, forms and user accounts are a separate application your team builds and runs.
  • SaaS only; content modelled as Prismic slices.
  • Rendering is left to your own front end.
  • The number of locales depends on the plan, from 2 on Free to 8 on Platinum; more need Enterprise. source
  • Custom roles, single sign-on and backups and restore are Enterprise features. source
  • The Migration API accepts one request per second per repository, with one page per request, saved as a draft. source
  • User seats are limited per plan, from 1 on Free to 25 on Medium. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Content classes and layouts are exported in packages you own.
  • The package wizard exports content classes, content subtrees, extensions or site styles as packages, with a review step before writing.
  • Packages can be kept as package.json with a JSON Schema and SHA-256 checksums, and convert to and from XML without loss.
  • Layouts, shared layouts and rules export to a versioned ZIP and import elsewhere with remote id mapping.
  • Blocks render through overridable layout, zone and block templates on your own server.
  • The media design ships about 426 templates, with light, dark and darker modes.
  • 46 block types with 113 view type entries let one block render as a list, grid, accordion or zig-zag.
  • One install command sets up a site on SQLite, MySQL, PostgreSQL, Oracle or MongoDB.
  • Static builds include 404.html, robots.txt and sitemap.xml and publish to GitHub Pages or another git host.
  • content/urlimport imports a URL map with a row-by-row preview, so old addresses keep working after a move.
Back to the overview

Coming from Contentstack

Enterprise headless, enterprise contracts.

What you deal with on Contentstack: how it limits your freedom

  • You build it yourself: Contentstack manages content only: the whole website, search, forms, user accounts and caching are a separate application your team builds and runs.
  • Enterprise SaaS only; no self-hosting.
  • The delivery front end is a separate project.
  • The Content Management API allows 10 requests per second per organization for reads and for writes, and bulk actions one per second. source
  • Uncached delivery requests share 100 per second per organization; after publishing many entries, first requests may return 429 errors. source
  • Each language can have only one fallback language, and fallback chains of more than one level are not allowed. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • The same enterprise features (workflows, roles, audit, languages) without a vendor contract.
  • Velocity serves HTTP/2 with automatic HTTPS on your own server and renews ACME certificates without a restart.
  • Velocity ships as deb and rpm packages, amd64 and arm64 Docker images and static binaries.
  • Staged remote deploys move migrations environment by environment, with an approval gate before each stage.
  • Review hold, approvals in My pending items and Publish without notification for typo fixes are built in.
  • Exponential Intelligence sets data residency per provider region and by rules per section and class.
  • Environment badges and installation names in page titles keep staging and production apart.
  • The audit trail exports CSV or JSON lines and sends records to syslog, a signed webhook or e-mail.
  • 219 locales, a right-to-left administration and checked translation fallback chains are in the kernel.
  • The rendered site and the APIs come from one installation, with the media design as the default front end.
Back to the overview

Coming from Hygraph

GraphQL in the cloud, front end not included.

What you deal with on Hygraph: how it limits your freedom

  • You build it yourself: Hygraph is a GraphQL content API: the whole website and every feature on it are a separate application your team builds and runs.
  • SaaS only, built around a hosted GraphQL API.
  • Usage-based plans.
  • Hobby includes 2 locales and Growth 3; up to 80 locales are an Enterprise feature. source
  • Custom roles, single sign-on and audit logs are only on Enterprise. source
  • Hobby keeps no content versions and Growth keeps them for 14 days. source
  • On Hobby, usage over the API call or asset traffic limit is blocked until the next billing period. source
  • Uncached API requests are limited to 5 per second on Hobby and 25 on Growth. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • REST API and GraphQL on your own installation, plus the rendered site.
  • Persisted GraphQL answers are cached per siteaccess, rights and variables with ETag; cached GETs measured 1.1 to 1.7 ms against 93.0 ms.
  • MaxDepth, MaxComplexity and list limits are checked before a GraphQL query runs.
  • GraphQL mutations create, translate, publish, move and hide content under the user's policies, and every mutation is audited.
  • GraphQL uploads follow the multipart spec with a virus-scanner hook, and preview tokens show drafts for a limited time.
  • Tags and page builder layouts get their own GraphQL queries, and extensions add schema through SchemaExtensionList[].
  • exp:graphql:enable switches GraphQL on per siteaccess, sets the CORS origin and prints a curl line; Setup > GraphQL has a playground.
  • exp:benchmark reports min, median, p95 and p99 for pages and kernel operations and exits 1 on a regression.
  • Migrations can run GraphQL queries and mutations in process, and /api/migration/v1 reports their status.
  • GraphQL introspection is for signed-in requests by default, and classes, fields and datatypes can be hidden.
Back to the overview

Coming from Directus

Source available, with a license threshold.

What you deal with on Directus: how it limits your freedom

  • You build it yourself: Directus is a data platform over your SQL database: the website and its features are a separate application your team builds and runs.
  • Since version 10 Directus is under the Business Source License; larger organizations need a commercial license.
  • A data platform: the website itself is a separate project.
  • Content translations are part of your data model: each translated collection needs a languages collection, a junction collection and a translations field. source
  • Data Studio interface translations are community contributions on Crowdin. source
  • The license changed again, to the Monospace Sustainable Core License, which excludes competing use and converts to GPL-3.0 only four years after release. source
  • Directus Cloud Core has a hard limit of 3 seats, 25 collections and 5 flows, and no single sign-on. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • GPL with no revenue threshold.
  • A complete CMS: content, pages, users, search and API.
  • Setup > Data tables browses rows and manages connections to SQLite, MySQL/MariaDB, PostgreSQL, Oracle, SQL Server or MongoDB.
  • expDataSync maps data table columns to content attributes, one way or both ways, with conflict rules.
  • The Module table wizard generates a data table extension with install SQL for every engine, views, policies and fetch functions.
  • sevenx_dse embeds a database editor with an SQL console, schema inspection and export, behind the dse policy.
  • The media design renders two demo websites with search, forms and public newsletter pages.
  • Content classes, versions, translations and workflows sit on top of the data in the same installation.
  • All 21 Zeta Components are maintained as expcomponents forks under the Apache License 2.0.
  • The website sidebar lets editors work on the live site with SEO and WCAG 2.2 AA accessibility checks.
Back to the overview

Coming from Payload CMS

Tied to Next.js and a new owner.

What you deal with on Payload CMS: how it limits your freedom

  • You build it yourself: Payload is a code-first framework: collections, access control and admin are written in TypeScript, and the website is a separate application you build.
  • Payload 3 is built into Next.js, so the CMS follows the Next.js release cycle.
  • Payload was acquired by Figma in 2025; its direction is now set by its new owner.
  • Changing a field to localized or back changes its stored structure, and that field's existing data is lost without a migration. source
  • Publishing status per locale is an experimental feature that must be switched on and tested before production use. source
  • Admin panel languages must each be imported into the config; unsupported languages fall back to English. source
  • Deployment of new projects on Payload Cloud, the vendor's hosting, is paused. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Exponential's direction is set by its foundation, in the open, with a release line going back two decades.
  • The kernel has its own compiled service container in kernelservices.ini, with exp:services commands to inspect it.
  • exp:graphql:starter generates plain HTML, Next.js, Nuxt 3, Astro or React Native front ends, so a framework is a choice, not a dependency.
  • Velocity runs the site from long-lived PHP workers with a warm database connection and a warm opcode cache.
  • PHP 8.0 to 8.5 are supported, and the composer.json PHP constraint reaches up to ^8.8.
  • All 21 Zeta Components are forked as expcomponents under the Apache License 2.0, tested on PHP 7.4 to 8.5.
  • Exponential 6.0.15 alone has 3,153 changelog entries, so every change is on record.
  • Exponential Layouts is a drag-and-drop page builder rendered by the CMS itself.
  • The setup wizard installs site, admin and editor siteaccesses in one go.
  • exp:upgrade upgrades in place with captions, verification and rollback.
Back to the overview

Coming from Webflow

Beautiful sites you can only host with them.

What you deal with on Webflow: how it limits your freedom

  • You build it yourself: Anything beyond its visual builder, CMS collections and simple forms (accounts, real permissions, custom logic) needs third-party services or custom code outside Webflow.
  • Proprietary and hosted only by Webflow.
  • Exports are limited: the CMS logic and dynamic content do not leave the platform as a working site.
  • Localization is a separate paid add-on: Essential allows up to 3 extra locales, Advanced up to 10, and more need Enterprise. source
  • The Data API allows 60 requests per minute on Starter and Basic and 120 on CMS and Business plans. source
  • A site can be published at most once per minute through the API. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • The whole site, code and data, is yours; static copies can be published to any host.
  • Static publishing keeps every publish to GitHub Pages or another git host, and rollback is a new commit.
  • Static builds keep a search page and index, forms that post to the live site, and redirect pages for old addresses.
  • The static cache generator writes pages as plain files that the web server sends without starting Exponential.
  • Any extension downloads from its info card as tar.gz, zip, tar.bz2 or ezpkg.
  • ezpm exports packages from the shell, including a whole content tree.
  • Exponential Layouts gives designers 15 site layout types and 46 block types on your own host.
  • Velocity resizes images on request and serves AVIF or WebP to browsers that accept them.
  • Velocity ships as a Composer package, deb and rpm packages, Docker images and static binaries for Linux, macOS and Windows.
  • The media design's light, dark and darker modes switch before the page draws, with text contrast of 4.5:1 or more.
Back to the overview

Coming from Vercel

A platform to host a front end, not a CMS.

What you deal with on Vercel: how it limits your freedom

  • You build it yourself: Vercel hosts and runs your application; it is not a CMS, so the content model, editing, workflows and every site feature are built or bought elsewhere.
  • Vercel hosts front ends; content still needs a CMS somewhere else.
  • Usage-based billing for bandwidth, functions and builds.
  • Closely tied to Next.js.
  • The free Hobby plan is restricted to non-commercial, personal use. source
  • On Hobby, a feature whose usage limit is exceeded is usually unavailable until 30 days have passed. source
  • Runtime logs are kept for 1 hour on Hobby and 1 day on Pro. source
  • Password protection of deployments is a paid add-on per project on Pro. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • One installation is CMS and website; the Velocity application server serves cached pages from memory.
  • Velocity's response cache answers public pages inside the server process at about 0.2 ms of CPU, with ETag and stale-while-revalidate.
  • Velocity serves HTTP/2 with automatic HTTPS and renews ACME certificates without a restart.
  • Velocity has built-in WebSocket, room and Server-Sent Events models for real-time features next to the site.
  • A commented block in .htaccess_root lets LiteSpeed and OpenLiteSpeed serve anonymous pages without PHP.
  • The static cache refreshes a publish's pages in parallel: 4975 ms down to about 500 ms in the measured case.
  • Templates can be .tpl, Twig 3 or Smarty 5, and GraphQL starters exist for Next.js, Nuxt 3 or Astro when you want them.
  • exp:velocity deploy regenerates autoloads and caches and reloads PHP-FPM and Velocity in one ordered run.
  • The Velocity scheduler runs handlers at intervals or set times without doubled runs around restarts.
  • Each Velocity server has a live dashboard at /Q/dashboard and a password-protected control panel at /Q/panel.
Back to the overview

Enterprise DXP

Coming from Adobe Experience Manager

An enterprise suite that needs enterprise specialists.

What you deal with on Adobe Experience Manager: how it limits your freedom

  • You build it yourself: Components, templates and integrations are built per project in Java, HTL and OSGi, typically by certified specialists over months.
  • Commercial license, sold with Adobe's other products.
  • Built on Java, OSGi and a JCR content repository, which call for specialized developers.
  • The cloud service moved projects to a different deployment model.
  • AEM 6.5 core support ended on August 31, 2026 for Managed Services and is planned to end in February 2027 on premises. source
  • Under AEM 6.5 extended support, critical security fixes are only available on the last service pack, 6.5.26. source
  • AEM 6.5 LTS requires Java 17 or 21 and removes some legacy features and artifacts, so customizations must be assessed before upgrading. source
  • In the cloud service Adobe applies version updates to all environments, and code deployed only to staging is removed by the next update. source
  • Each language needs its own language copy tree, and only members of the project-administrators group can use the language copy features. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • PHP, the most widely hosted web language, with free software and open documentation.
  • Runs on ordinary hosting or your own servers; no forced cloud move.
  • Templates are .tpl, Twig 3 or Smarty 5 files, and Setup > RAD wizards write working extensions.
  • A remote service domain is one PHP class extending expServiceBase, and it appears in the catalogue without further steps.
  • The repository runs on SQL databases or MongoDB, and sevenx_dse lets administrators inspect it in the browser.
  • Review hold, versions with compare and preview links for outside reviewers are built in.
  • Exponential Layouts gives editors drag-and-drop pages with 46 block types.
  • 219 locales, right-to-left support and translation sync in Exponential Intelligence cover multilingual sites.
  • Run it on PHP-FPM, on Velocity with Qbix or FrankenPHP, or publish static copies to a git host.
  • A tamper-evident audit trail, an encrypted secret store and Content Security Policy modes ship with the kernel.
Back to the overview

Coming from Sitecore

License, .NET, and a SaaS rebuild.

What you deal with on Sitecore: how it limits your freedom

  • You build it yourself: Renderings, data templates and integrations are built per project in .NET or as a separate head application, typically by certified partners over months.
  • Commercial license.
  • Historically a .NET and Windows stack.
  • XM Cloud is a different architecture, so moving there means rebuilding the front end.
  • From June 1, 2026, security fixes and incident assistance in Extended Support are no longer included by default but arranged through an account representative. source
  • Sitecore 10.3 mainstream support ended on December 31, 2025, and extended support for 10.0 and 10.1 ends on December 31, 2026. source
  • The XP and XM interface is in English by default; client translations exist only for Danish, German, Japanese and Chinese and must be imported. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Linux, Windows or containers; no license; upgrades in place.
  • Velocity ships static binaries for Linux, macOS and Windows, plus deb and rpm packages and Docker images.
  • The site is rendered by the CMS itself, and GraphQL starters exist if you want a separate front end.
  • exp:upgrade:rollback restores the database, settings, libraries or storage part by part from any caption.
  • Exponential Layouts rules choose layouts by path, subtree, class, siteaccess or route, with time switches and A/B variants.
  • The dashboard shows key-figure tiles and a 14-day publishing chart.
  • Five database engines include Oracle, with Oracle 11g and 12.1 working with ezoracle 2.3.7.
  • The audit trail has alert rules and exports as CSV, JSON lines or JSON.
  • Passkeys, two-step sign-in and a list of every signed-in device are part of the kernel.
  • Staged migration deploys move environment by environment with an approval gate before each stage.
Back to the overview

Coming from Optimizely

Commercial .NET, with platform migrations.

What you deal with on Optimizely: how it limits your freedom

  • You build it yourself: Content types, templates and integrations are written per project in .NET; the website is a custom application on top of the platform.
  • Commercial license.
  • CMS 12 required moving from .NET Framework to modern .NET, a migration for every project.
  • CMS 13 requires .NET 10, and Search & Navigation is not supported there, so moving to Optimizely Graph is mandatory. source
  • No CMS 13 version of the Find package is planned, and third-party add-on owners must update their own packages for CMS 13. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • PHP 7.4 to 8.5 supported side by side, so the language can be upgraded when it suits you.
  • PHP 7.4 still installs without a support commitment, so a server's PHP can be moved when it suits you.
  • The PHP floor metapackage lets Composer install the extension releases that run on the PHP in use.
  • Exponential 6.0.15 cleared the deprecations PHP 8.4 reported on every request.
  • exp:upgrade:libraries runs composer install from the lock file with composer audit before and after.
  • CI lints every file with PHP 7.4 and 8.0 and boot-tests every kernel and extension class.
  • Exponential Layouts serves A/B layout variants by query parameter, kept out of shared caches.
  • Content checks find unreferenced assets, broken relations and storage files that no content uses.
  • Translation sync in Exponential Intelligence marks each translation as unchanged, needing a patch or needing a full retranslation.
  • Setup > Upgrade check compares every file and every table with the release, with the SQL to fix each difference.
Back to the overview

Coming from Acquia

Drupal plus a hosting contract.

What you deal with on Acquia: how it limits your freedom

  • You build it yourself: Acquia hosts Drupal: the site itself is still a Drupal project of modules, custom code and a theme that your team builds and upgrades.
  • Drupal's migrations, plus a commercial platform contract.
  • Drupal 10 reaches end of life on December 9, 2026; each Drupal major version is supported for only 4 to 4.5 years. source
  • Drupal 7 reached end of life on January 5, 2025; continued security coverage is available only as paid extended support from certified vendors. source
  • Acquia lists contributed modules that cannot be used on Cloud Platform sites, among them Backup and Migrate, Boost, CiviCRM, Monolog and Advanced Varnish. source
  • On Cloud Next, cron tasks may not run longer than 3 hours, Git repositories may not exceed 2 GB and HTTP response headers are limited to 8 KB. source
  • Acquia documents that Cloud Next database backups can run up to 12 hours later than the configured schedule. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Exponential runs on any hosting; nothing is tied to one provider.
  • Upgrades run in place: ./console exp:upgrade --apply backs up, runs each stage in order and stops at the first failure. Without --apply it is a dry run.
  • Before writing anything, exp:upgrade takes a caption (database dump, var/ storage, settings, Composer files), and exp:upgrade:rollback restores any part of it.
  • exp:upgrade:verify --after checks smoke URLs, the upgrade-smoke tests and new fatal log lines; with --rollback-on-fail it restores the pre-upgrade caption by itself.
  • Extensions register their own upgrade steps in upgrade.ini, so your custom code moves forward in the same exp:upgrade run as the kernel.
  • Setup > Upgrade check compares every file with the release checksum list and the database with the shipped schema, with the SQL to fix each difference.
  • Run it on Apache with PHP-FPM, on the bundled Velocity application server or on FrankenPHP; exp:velocity drives the engines.
  • Velocity ships as deb and rpm packages, amd64 and arm64 Docker images and static binaries, so the server is yours to run wherever you choose.
  • One installation command installs on SQLite, MySQL, PostgreSQL, MongoDB or Oracle, and SQLite runs a complete site from one file.
  • exp:velocity deploy regenerates autoloads, settings and caches and reloads PHP-FPM and Velocity in one ordered run, stopping at the first failure.
  • Setup > Static publishing can publish a static copy of a site to GitHub Pages or another git host, and a rollback is a new commit.
Back to the overview

Coming from Magnolia

Java DXP with a paid core.

What you deal with on Magnolia: how it limits your freedom

  • You build it yourself: Content apps, templates and light modules are developed per project in Java, YAML and FreeMarker.
  • The DX Core edition is commercial.
  • Java and JCR expertise required.
  • In the Community Edition you can create and use only one site; the Multisite module ships with DX Core. source
  • The Content Translation Support module, which exports and imports content as XLIFF, CSV or Excel for translators, is a DX Core module. source
  • The Personalization module is bundled with DX Core only. source
  • Magnolia makes product updates for previous major versions only for DX Core customers, not for the Community Edition. source
  • Magnolia 6.2 and 6.3 leave active support in September 2026 and reach end of life in September 2027; extended end of life is offered only under paid agreements. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • The complete product is free software.
  • Built on PHP, officially supported from 8.0 to 8.5: no Java runtime and no JCR knowledge needed to run or extend it.
  • The content repository lives in an ordinary database: SQLite, MySQL, PostgreSQL, Oracle or MongoDB, chosen at install time with one command.
  • Exponential Layouts, the visual page builder, is part of the free software with 46 block types and 15 site layout types.
  • Passkeys, two-step sign-in, Verify it's you and a tamper-evident, hash-chained audit trail come in the same free kernel.
  • Content classes are built in the class editor, or written as a script by the content extension wizard in Setup > RAD.
  • Templates can be written in the kernel's .tpl language, in Twig 3 or in Smarty 5, all found, overridden and cached the same way.
  • REST v1 and v2 and a GraphQL API generated from the content classes are included, with persisted queries and rate limits.
  • Setup > RAD lists 68 extension points, 64 of them with a wizard that shows every file it would write before writing an extension.
  • The kernel ships 219 locales, including right-to-left languages, and each extra language chosen in setup becomes its own siteaccess.
  • Exponential Intelligence works with Anthropic, any OpenAI-compatible service or a local open-weight model, with data residency rules per section and class.
Back to the overview

Coming from Liferay

A heavy Java portal.

What you deal with on Liferay: how it limits your freedom

  • You build it yourself: Portlets, client extensions and themes are developed per project in Java and JavaScript, usually by specialist developers.
  • A large Java portal platform; the DXP edition is commercial.
  • Resource-heavy for a content website.
  • Starting with 2026.Q1, Community Edition and DXP merged into one platform, and community users must request and apply a free Activation Key. source
  • Under the 2026 model, non-subscribers get only the first release of each quarterly release. source
  • LTS (Q1) quarterly releases are supported for 3 years; every other quarterly release gets 1 year. source
  • Since 2025.Q3, Liferay DXP is built on Jakarta EE; Liferay calls this a breaking change that requires custom code and some dependencies to be updated. source
  • Only some interface languages are officially supported (95% of keys translated); community languages need only 65% of keys translated and one proofreader. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • A lean content kernel with four cache layers; most pages are answered in tens of milliseconds.
  • A complete site runs from a single SQLite file, with no database server to install or secure.
  • Velocity runs a pool of long-lived PHP workers with warm database connections and opcode cache, and answers cached public pages at about 0.2 ms of CPU.
  • The role-aware HTTP cache stores whole pages per permission context, so a thousand members share one copy of each page.
  • The static cache turns pages into plain files that the web server sends without starting Exponential.
  • With [RoleSettings] AccessArrayPrefetch, a user with 600 subtree assignments went from about 48,600 queries to 4 when the access array is built.
  • The SQL query cache answers a repeated SELECT from memory until a write to one of its tables makes the result stale.
  • ./console exp:benchmark reports min, median, p95 and p99 for pages and kernel operations, compares saved baselines and exits 1 on a regression.
  • There is one edition: Exponential Layouts, GraphQL, passkeys and the audit trail all ship in the same free software.
  • Editors get their own portal with content tabs only, while setup, classes, roles and workflows answer 404 there.
  • Portal designs in jQuery 4, React and a reactive variant render news, shop, forums, media and search in the browser, ready to point at a site.
Back to the overview

Coming from Ibexa DXP

The commercial successor of the kernel we kept free.

What you deal with on Ibexa DXP: how it limits your freedom

  • You build it yourself: Ibexa provides the platform; the site itself (templates, controllers, blocks and integrations) is written per project in Symfony and Twig, and major versions rewrite part of it.
  • Commercial editions with a subscription.
  • A full Symfony application; sites on the old kernel must be migrated, not upgraded.
  • Ibexa DXP 4.6 LTS ends maintenance in February 2027 (end of life February 2029); 5.0 LTS ends both maintenance and life in August 2028. source
  • Only French, German and Spanish back office translations are produced by Ibexa; every other language is translated by the community on Crowdin. source
  • Upgrading to v5.0 requires PHP 8.3 or later and the latest 4.6 release first; the compatibility layer is not supported and the 4.6 GraphQL schema must be deleted. source
  • v5.0 renamed most database tables from ez to ibexa_, changed field type identifiers, moved many classes to new namespaces and dropped the legacy Commerce packages. source
  • The release notes say the next major version, 6.0, will be renamed Cohesivo. source
  • Page Builder and Form Builder are included in the Experience and Commerce editions, not in Headless. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Exponential continues the original kernel, free, with in-place upgrades for those sites.
  • Your path: Exponential Platform DXP 4.6 or 5, free software maintained by 7x.
  • Exponential Platform DXP 5 is skeleton v2.0.0.5, built on Ibexa DXP OSS 5.0.6 for PHP 8.3 and later.
  • Platform DXP 4.6 (skeleton v1.0.0.5) runs on PHP 7.4 to 8.5 and stays maintained while you prepare the move to 5.
  • Install the DXP skeleton of your major version and point it at your database: your Symfony bundles and Twig templates stay.
  • The admin UI, REST, GraphQL and search are included in Platform DXP, free software instead of a subscription.
  • The DXP skeleton is created with composer create-project and documented from an empty folder to a running administration on MySQL, PostgreSQL or SQLite.
  • Want the legacy kernel back? Exponential Platform Legacy 4.6.x and 5.x carry it beside the Symfony stack for Ibexa 3.3 and 4.x projects.
  • The Platform DXP Starter (EPDSD 1.0.0.0) is a ready-to-run distribution tuned for SQLite, for evaluations or as a clean import target.
  • Older lines (3.3 and 4.0 to 4.5) remain available as archived Platform DXP branches to start a move from.
  • On the Exponential 6 kernel, Exponential Layouts, passkeys and the hash-chained audit trail are part of the free software too.
Your upgrade path in the Exponential family → Back to the overview

Frameworks & runtimes

Coming from Laravel

A framework: the CMS is yours to write.

What you deal with on Laravel: how it limits your freedom

  • You build it yourself: Laravel is a framework: the content model, editor screens, versions, translations, permissions, media handling and caching are yours to design, build, test and maintain.
  • A framework, not a CMS: content model, admin, versions, translations and permissions must be built.
  • Every custom admin becomes code your team maintains forever.
  • Admin panels are usually mounted inside the same application and host name as the public site.
  • Each Laravel release gets bug fixes for 18 months and security fixes for 2 years, with a new major version every year. source
  • For Laravel's additional first-party libraries, only the latest major release receives bug fixes. source
  • Built-in localization covers translation strings in PHP or JSON files; the default application skeleton does not even include the lang directory. source
  • With Laravel 12, the Breeze and Jetstream starter kits no longer receive updates. source
  • The Nova admin panel is a separate product that requires a purchased license key for production use. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • All of that already exists and is tested: 211 console commands, 1,304 test classes.
  • Public site, editor portal and administration portal are separated from the first installation.
  • The content model is ready: sevenx_classes installs 33 general content classes, and new classes are made in the class editor or by a RAD wizard.
  • Versions are built in: Manage versions compares any two versions inline, and Make a new draft restores an older one.
  • Translations are built in: 219 locales, language badges for missing or outdated translations, and a siteaccess per extra language from setup.
  • Permissions are built in: policies read as sentences, reads fail closed, and a user can grant only what their own access covers.
  • Setup > RAD wizards write working modules, datatypes, workflow events and template operators, and show every file before writing it.
  • The module table wizard generates a data table extension with a persistent class, install SQL for every engine, views, policies and fetch functions.
  • APIs exist on day one: REST v1 and v2, a GraphQL schema generated from the content classes, and signed webhooks for content events.
  • Exponential Layouts gives editors a drag-and-drop page builder with 46 block types and rule-based layout resolving.
  • Migrations are in the kernel: PHP, YAML, SQL and INI migrations, with a caption before each run and automatic restore after a failure.
  • Passkeys, two-step sign-in for staff by default and a hash-chained audit trail are there before you write a line.
Back to the overview

Coming from Symfony

Excellent components, no content management.

What you deal with on Symfony: how it limits your freedom

  • You build it yourself: Symfony is a set of components: every CMS feature (content model, admin, versions, workflows, content translation, permissions) is built by your team.
  • A framework: the content repository and editor interface are left to you.
  • Major versions bring deprecations to work through in your own code.
  • Admin bundles usually share the application and firewall configuration with the public site.
  • Non-LTS versions have short lives: Symfony 8.0, released November 2025, lost support in July 2026. source
  • Symfony 8 requires PHP 8.4 or higher. source
  • Symfony 6.4 LTS bug fixes end November 2026 and security fixes November 2027. source
  • Symfony's docs say translating content stored in Doctrine entities with translation catalogs is not practical and point to a third-party Translatable extension. source
  • Security fixes for Symfony 5.4 run until February 2029 only because one company sponsors them; Symfony urges users not to delay upgrading. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Content management is the product; your code lives in extensions that survive upgrades.
  • Each portal has its own siteaccess, settings and protection.
  • Twig 3 templates work in the kernel next to .tpl, with overrides, includes, caching, every template operator and every fetch function.
  • The kernel has its own service container in kernelservices.ini, with worker, request and prototype scopes and tags, compiled per siteaccess.
  • exp:services:compile, list, show and check compile, inspect and validate the service container from the shell.
  • Upgrades run as recorded, self-detecting steps (32 in 6.0.15), so work already done by hand shows as not-needed.
  • The editor interface is ready: edit forms with a field bar, automatic draft saving, device previews and a version compare.
  • Exponential Platform Nexus has a 7x line for each Symfony version, all with Exponential Layouts: 1.0.0.x on 3.4, 1.1.0.x and 1.2.0.x on 5.4, and the current 1.3.0.x on 7.4 with Platform DXP 5 and SQLite.
  • Five ezpEvent filters let extensions take part in view cache keys and access checks without patching the kernel.
  • The content repository runs on SQLite, MySQL, PostgreSQL, MongoDB or Oracle, with migrations in PHP, YAML, SQL or INI.
  • Velocity serves the installation from long-lived PHP workers, and request-scope reset hooks keep each worker clean between requests.
  • The GraphQL API is generated from the content classes, with persisted queries, depth and complexity limits and rate limits.
Back to the overview

Coming from Symfony CMF

A CMS toolkit with little activity in recent years.

What you deal with on Symfony CMF: how it limits your freedom

  • You build it yourself: With the CMF archived, every CMS feature you need is now custom code that nobody else maintains.
  • The Symfony CMF bundles have seen little development in recent years.
  • Building a CMS from bundles leaves integration and editing tools to you.
  • The main Symfony CMF repository was archived on September 16, 2021, and is no longer maintained, "due to lack of interest." source
  • The CMF ContentBundle is archived and read-only since September 16, 2021. source
  • The CMF BlockBundle is archived and no longer maintained. source
  • The Sonata PHPCR admin integration bundle is archived and marked abandoned, so CMF has no maintained admin interface. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • A maintained, complete product with a release line and a public changelog.
  • Exponential 6.0.15 alone has 3,153 changelog entries.
  • The release line is public: 6.0.15 and 6.0.14 are current, and 6.0.10 to 6.0.13 are maintained.
  • Editing tools ship ready: an editor portal, a website sidebar for editing on the page and Exponential Layouts for page building.
  • The website sidebar edits titles and text on the live page, autosaves to the draft and keeps a local browser copy for two weeks.
  • The sidebar's calendar panel shows scheduled publications and take-downs, and moving an item reschedules it.
  • Rich text fields use TinyMCE 8 or Tiptap, switchable under the field without losing what was typed.
  • Integration is built in: REST, GraphQL, about 1,100 remote services in expservices and signed webhooks.
  • The Quality workflow lints every file and runs production installs; database tests run against MySQL 8.0, PostgreSQL 15 and MongoDB 7.
  • Dependabot covers Composer, npm and GitHub Actions, CodeQL scans the JavaScript, and upgrades run composer audit before and after.
  • The Help button opens the help page for the current view, and the help dashboard has search and topics for each audience.
Back to the overview

Coming from CodeIgniter

Light framework, everything else is custom.

What you deal with on CodeIgniter: how it limits your freedom

  • You build it yourself: You get routing, database access and helpers; the admin, content model, editor accounts, permissions and workflows are all written by hand.
  • A framework: every content feature is custom code.
  • Version 3 to 4 was a rewrite.
  • CodeIgniter maintains only its latest version. source
  • CodeIgniter 4 now requires PHP 8.2 or newer, and the docs note that PHP 8.2 itself reaches end of life on December 31, 2026. source
  • Not all database drivers were converted for CodeIgniter 4; PDO, ODBC, CUBRID and Firebird drivers are among those not yet converted. source
  • Framework translations are maintained per language by community members; the framework team claims no expertise beyond English. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Content features are built in and extended through documented extension points.
  • Upgrades move a site forward in place with exp:upgrade, which takes a caption first and stops at the first failure.
  • Extensions add their own upgrade steps through upgrade.ini ExtensionStepList[], so your code joins the same upgrade run.
  • Versions, translations, drafts and approvals are kernel features: My pending items lists versions waiting for approval with their approvers.
  • Exponential Layouts, a visual page builder with 46 block types and 12 content query types, ships with it.
  • The Edit image tool crops, rotates, resizes and watermarks images in the browser, with undo and redo.
  • Search is built in: the kernel search by default, an optional Solr server through exp:solr, and suggestions while typing.
  • Accounts come ready: registration, passkeys, two-step sign-in and forgot-password links that expire after one hour by default.
  • On MySQL, PostgreSQL, SQLite and Oracle, renaming or moving a node turns its old address into a 301 redirect to the new one.
  • expDataSync maps the columns of existing data tables to content attributes, once, on a schedule or live, one way or both ways.
  • The module wizard writes a module with views on top of existing database tables.
Back to the overview

Coming from CakePHP

Conventions, but no CMS.

What you deal with on CakePHP: how it limits your freedom

  • You build it yourself: Scaffolding helps, but a CMS (content types, editing screens, versions, translations, permissions) is still a custom application you build and maintain.
  • A framework: admin, permissions and content structure are your work.
  • CakePHP is maintained by volunteers; security fixes for end-of-life versions are backported only when feasible, with no guarantee. source
  • CakePHP 4.x bug fixes ended on September 10, 2025, and support for 4.4 and 4.5 ended on September 9, 2026. source
  • 5.x minor versions are supported only until a later minor version ships; 5.0 ended March 29, 2025, and 5.1 ended July 19, 2026. source
  • Translations of the core messages and country-specific validation ship in the separate Localized plugin, not in the framework. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • An administration interface in five designs, light and dark, ready on day one.
  • Roles are managed in the administration, and each policy reads as a sentence, such as May read content in section Standard of the classes Article and Folder.
  • exp:access:check tells whether a user may read, edit or remove a node or object, and which policy and limitation refused it.
  • Permission reads fail closed: if a policy's limitations cannot be read, the policy grants nothing.
  • 24 exp:user commands list, create, disable, import, export and approve accounts and manage groups, roles, sessions and second factors.
  • The editor portal separates everyday editing from administration: setup, class, role and workflow modules answer 404 there.
  • The sub-items table offers 129 registered columns plus every class attribute, with presets, drag-and-drop ordering and CSV export.
  • Bulk actions edit, move, copy, hide or relocate selected items, and large operations run as resumable background jobs.
  • Setup > Content finder finds the object behind an id, a remote id, a URL alias, a page URL or a file path under var/.
  • Users > Check user accounts finds accounts that never signed in, are locked or orphaned, or share a login or e-mail, with bulk actions to tidy them.
  • Content structure is a tree of locations with sections and object states, and a section can be assigned to a whole subtree in one step.
Back to the overview

Coming from Adobe ColdFusion

A commercial runtime with a shrinking talent pool.

What you deal with on Adobe ColdFusion: how it limits your freedom

  • You build it yourself: ColdFusion is an application server: every content feature is custom CFML code, written and maintained by increasingly scarce specialists.
  • A commercial runtime licensed per server.
  • Fewer developers learn CFML each year.
  • Perpetual licensing is no longer available for any version of Adobe ColdFusion; access, updates and support end when the subscription ends. source
  • ColdFusion 2021 core support ended November 10, 2025; extended support until November 10, 2026 includes no security patches or hot fixes. source
  • ColdFusion 2025 removed YUI-based UI tags such as cftree, cfcalendar and cfmenu, along with the remaining Flash and Flex features. source
  • The JDK 21 move in ColdFusion 2025 removed the cfthread terminate action and ThreadTerminate(); Axis1 was removed for security reasons. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Free software on PHP, with documentation in English and German.
  • Runs on stock PHP, officially supported from 8.0 to 8.5, including PHP 8.0, the stock PHP of Red Hat Enterprise Linux 9.
  • The Velocity application server is part of Exponential since 6.0.15 and is installed by composer install with the rest of the free software.
  • The se7enxweb/exponential-php-floor metapackage lets Composer install the extension releases that run on the PHP in use.
  • ./console exp:install --apply installs a site on any of five database engines with setup and kickstart logs.
  • Templates can be written in the kernel's .tpl language, in Twig 3 or in Smarty 5.
  • Setup > Data tables manages named connections to SQLite, MySQL/MariaDB, PostgreSQL, Oracle, SQL Server or MongoDB.
  • expDataSync maps existing data table columns to content attributes, with conflict rules and a page of open conflicts.
  • The remote services come with tested shell and Python clients, plus client snippets for Kotlin, Swift, Objective-C, Qt and GTK.
  • Setup > RAD wizards write design, module, datatype and workflow event extensions and show every file before writing it.
  • The built-in help center opens the page for the current view and is searchable, with topics for each audience.
Back to the overview

Coming from Perl web stacks

CGI-era sites that few can still maintain.

What you deal with on Perl web stacks: how it limits your freedom

  • You build it yourself: A Perl web site is a custom application on CGI or a framework; every content feature is written and maintained in-house.
  • Many Perl sites are CGI-era custom code with few maintainers left.
  • Modern hosting rarely offers Perl web stacks.
  • Perl's maintainers aim to fix critical issues only in the two most recent stable release series; older series are end of life. source
  • The CGI module was removed from the core Perl distribution in Perl 5.22. source
  • The CGI.pm docs say it is no longer considered good practice for web applications, and its HTML generation functions are no longer maintained. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Runs on every common PHP host, from shared hosting to containers.
  • The setup wizard needs privileges on your own database only, so it works on shared hosting.
  • SQLite is the default database: a complete site runs from one file, with no database server to install.
  • Velocity also ships as amd64 and arm64 Docker images and as static binaries for Linux, macOS and Windows.
  • A commented block in .htaccess_root lets LiteSpeed and OpenLiteSpeed serve anonymous pages without PHP.
  • content/urlimport imports a URL map as CSV, JSON or Apache and nginx rules, with a preview, a dry run and an exact undo.
  • exp:url:from-sitemap and exp:url:from-404 build a URL map of the old site's addresses when a site moves.
  • The exp_url_redirect table answers old addresses, including query strings, with 302, 303, 307 or 308 redirects before URL aliases are resolved.
  • The module wizard writes a module with views on top of existing database tables.
  • Extension points are documented: Setup > RAD lists 68 of them in seven groups, and the extension point survey counts every registration.
  • The Quality workflow lints every file with PHP 7.4 and 8.0 and runs production installs and boot smoke tests.
Back to the overview

Shops & commerce

Coming from Magento Open Source

A heavy shop that makes content an afterthought.

What you deal with on Magento Open Source: how it limits your freedom

  • You build it yourself: Magento is a shop: editorial content, workflows and a content model beyond CMS pages and blocks come from extensions or custom modules.
  • Resource-heavy, with upgrades that need dedicated developers.
  • Magento 1 reached end of life in 2020; moving to 2 was a rebuild.
  • Content pages are secondary to the catalogue.
  • Adobe's lifecycle policy gives versions 2.4.6 and 2.4.7 an extra year of support for Adobe Commerce customers; it does not mention Magento Open Source. source
  • Content staging is available only in Adobe Commerce and not in Magento Open Source. source
  • Store views are the way to offer a store in different locales, so each language becomes its own store view. source
  • Language packs come from a community translation project on Crowdin or from Marketplace extensions. source
  • Adobe does not provide security or quality fixes for dependencies such as PHP and MySQL; keeping them supported is the merchant's job. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Content first, with the shop built into the same kernel (baskets, orders, payment gateways).
  • 255 commerce services cover products, basket and checkout, orders, VAT, currencies, discounts, wish lists, shipping and payments.
  • Products are content: sevenx_classes installs a product class next to article and folder, with the same versions, translations and previews.
  • The media design ships Exponential Layouts block templates for product highlights and a product card item view for any class.
  • The Editor portal has a Store tab beside Content structure and Media, so shop work stays out of the system administration.
  • The tamper-evident audit trail records commerce events alongside sign-ins, content, settings and deploys.
  • Order mails are HTML with a plain-text part, in the same shared layout as account and notification mails.
  • exp:upgrade is a dry run until --apply, takes a caption first and can roll back any part with exp:upgrade:rollback.
  • Velocity answers cached public pages at about 0.2 ms of CPU, and the role-aware HTTP cache shares one copy per permission context.
  • Velocity resizes images on request and serves AVIF or WebP to browsers that accept them, caching the result.
  • Setup > Upgrade check compares every file and every table with what the release shipped, with the SQL to fix each difference.
Back to the overview

Coming from Adobe Commerce

Magento with an enterprise license.

What you deal with on Adobe Commerce: how it limits your freedom

  • You build it yourself: Editorial publishing beyond Page Builder needs AEM or custom work, and on the Cloud Service every customization is an App Builder app you build and run.
  • Commercial license on top of Magento's complexity.
  • Adobe Commerce as a Cloud Service allows out-of-process extensions only (APIs, events, App Builder); in-process PHP modules cannot be installed. source
  • Moving from PaaS to the Cloud Service means rebuilding in-process modules as App Builder apps; the migration service covers core data, not extension tables. source
  • The Cloud Service offers standard email templates only, while PaaS allows full email customization. source
  • On PaaS, upgrades and patches are applied manually: six patch releases and one minor release per year. source
  • Regular support for 2.4.6 ended August 11, 2026, and 2.4.7 regular support ends May 31, 2027. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • No license fees for the software, whatever your revenue.
  • Basket, checkout, orders, VAT, currencies and discounts run beside the content, covered by 255 commerce services in expservices.
  • Wish lists, shipping and payments are services too, each one public, user-only or tied to a module policy.
  • The Simple design ships product and basket templates, a cart icon and a multi-level dropdown menu.
  • The React portal design renders a shop with basket in the browser, with vendored libraries that work offline without Node.
  • Commerce events land in the hash-chained audit trail, with alert rules for brute-force sign-ins and mass deletes.
  • Staff accounts require two-step sign-in by default, and passkeys can be required per site, group or account.
  • Self-hosted on SQLite, MySQL, PostgreSQL, Oracle or MongoDB, with customer and order data in your own database.
  • Upgrades run in place with exp:upgrade, with a caption before each run and a rollback for every part.
  • There is one edition: Exponential Layouts, GraphQL and Exponential Intelligence ship in the same free software as the shop.
Back to the overview

Coming from Shopware

A new major version meant a new shop.

What you deal with on Shopware: how it limits your freedom

  • You build it yourself: Shopware is a shop: rich editorial content, custom content types and workflows come from plugins or custom apps written per project.
  • Shopware 6 was a new system; shops on 5 had to be rebuilt.
  • Some features are reserved for commercial editions.
  • Since March 2025, Community Edition shops with more than 1 million euros of annual GMV must take a paid plan to keep access to the Shopware Account and Store. source
  • All Community Edition users must report their GMV to Shopware, whatever their revenue. source
  • A new major version ships every year; only the last minor of the previous major gets direct patch updates, and other minors get fixes only through a security plugin. source
  • Additional admin and storefront languages come from the Language Pack extension, translated by the community on Crowdin. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Upgrades in place, every feature in the free kernel.
  • 6.0.15 brings 32 upgrade steps that inspect the installation first, so a step already done shows as not-needed.
  • The new release is built beside the old tree and switched in one step, with no downtime and rollback by switching back.
  • Products, basket, checkout, orders, VAT, discounts, shipping and payments are covered by 255 commerce services in the free software.
  • Exponential Layouts builds shop landing pages, and the media design ships block templates for product highlights.
  • A layout rule with a time condition switches a campaign layout on and off at its start and end.
  • Query parameter conditions let one address serve two layouts, for A/B tests such as /page and /page?variant=b.
  • Exponential Intelligence suggests titles, summaries and meta descriptions in the edit form, and nothing changes until the editor accepts.
  • REST and a GraphQL API generated from the content classes serve products and pages to apps and front ends.
  • Extensions show version, license, dependencies and loading position in Setup > Extensions, and reordering goes through Review changes.
Back to the overview

Coming from WooCommerce

A shop plugin inheriting WordPress's limits.

What you deal with on WooCommerce: how it limits your freedom

  • You build it yourself: Each shop feature beyond the basics (subscriptions, bookings, B2B pricing, multilingual) is a separate plugin, often paid, that you integrate and keep compatible.
  • Runs as a WordPress plugin, with WordPress's content model and plugin dependencies.
  • Many shop features are paid extensions.
  • Shop management runs in the WordPress administration on the public host.
  • WooCommerce's own article says WordPress sites are not multilingual by default; a plugin such as WPML or Polylang is typically needed. source
  • Translations come from volunteers on translate.wordpress.org and install automatically only when at least 90% complete; extensions have separate translations. source
  • WooCommerce supports only the current and previous WordPress and WooCommerce release series (L-1); older versions are not tested. source
  • Releases follow a 5-week cycle, so stores and extensions need frequent updates. source
  • WooCommerce decided to require PHP 8.1 or newer from version 11.6, a higher minimum than WordPress's PHP 7.4. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Shop, content and permissions share one kernel and one data model.
  • Order and shop administration stay in the administration portal, which need not be public.
  • Basket, checkout, orders, VAT, currencies, discounts, wish lists, shipping and payments are covered by the commerce services of expservices.
  • The Editor portal has its own address and a Store tab, while setup, roles and workflows answer 404 there.
  • Two-step sign-in is required for administrators and editors on new installations, and passkeys can replace the app code.
  • The hash-chained audit trail records commerce events, sign-ins and settings writes, with alert rules for brute force.
  • The administration runs without inline scripts or styles, so its Content Security Policy can be enforced.
  • Reordering extensions in Setup > Extensions goes through Review changes, which lists the risks before anything is written.
  • Order mails are HTML with a plain-text part in one shared layout with dark-mode colors.
  • Optional mail goes only to people who opted in, with double opt-in, one-click unsubscribe and a consent log with the exact text shown.
  • The role-aware HTTP cache answers whole pages before the kernel starts, stored per anonymous, role or private context.
  • Setup > Upgrade check compares every file with the release checksum list and lists what changed.
Back to the overview

Coming from PrestaShop

Module conflicts at every major upgrade.

What you deal with on PrestaShop: how it limits your freedom

  • You build it yourself: Most shop features beyond the core come as marketplace modules, often paid, or are written per project.
  • Major upgrades (1.6 to 1.7 to 8) broke modules and themes.
  • Support for a PrestaShop minor version generally ends when the next minor version is published. source
  • The 1.7.7, 1.7.8, 8.0 and 8.1 branches are no longer maintained; 8.2 receives security fixes only until PrestaShop 10. source
  • Most languages exist on Crowdin, but not all are available in PrestaShop, because some have a low completion level. source
  • Translations are made by volunteers on Crowdin; shop owners must refresh them manually in the back office to get updates. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Stable extension APIs and immutable releases.
  • Extensions register their own upgrade steps in upgrade.ini, so they move forward in the same exp:upgrade run as the kernel.
  • Before every upgrade a caption is taken, and exp:upgrade:rollback restores the database, settings, libraries or storage part by part.
  • exp:upgrade:verify --after checks smoke URLs and new fatal log lines, and --rollback-on-fail restores the caption automatically.
  • Setup > Extensions shows each extension's version, dependencies and real loading position, and reordering lists risks before anything is written.
  • Designs fall back through a chain, so a theme overrides only the templates it changes and keeps the rest from the designs below it.
  • Five ezpEvent filters and documented extension points let extensions change behavior without patching the kernel.
  • The $.ez() compatibility layer keeps existing site code working on jQuery 4.
  • TinyMCE 8 writes the same stored XML as TinyMCE 3, so existing rich text stays as it is.
  • The RAD health check reports settings that name missing classes, missing directories and views without scripts, with how to fix each.
  • Basket, checkout, orders, VAT, discounts and payments are part of the 255 commerce services in expservices, not a module to keep compatible.
Back to the overview

Coming from Sylius

A commerce framework for developers only.

What you deal with on Sylius: how it limits your freedom

  • You build it yourself: Sylius is an e-commerce framework: the storefront, content pages and many features are developed per project in Symfony.
  • A framework: every shop is a development project.
  • Minor versions have short support windows: Sylius 2.0, released November 2024, reached end of support on February 28, 2026. source
  • Sylius 1.14 LTS receives security fixes only and reaches end of support in December 2026. source
  • RBAC, multi-source inventory, B2B pricing and returns management come with the commercial Sylius Plus edition. source
  • Sylius 2.0 replaced template events with Twig Hooks and removed Payum and Stripe packages, so template and payment customizations must be migrated. source
  • Sylius 2.0 dropped Symfony 5.4 and raised the minimum PHP version to 8.2. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • A working site on install, extended where you need it.
  • ./console exp:install --apply installs the multisite package on SQLite and prints the site and admin addresses and logins.
  • The Kickstarter takes every setup answer from kickstart.ini and installs the same site again with one command.
  • The Simple design ships product and basket templates, article, blog and gallery views and a cart icon.
  • 255 commerce services cover products, basket and checkout, orders, VAT, currencies, discounts, shipping and payments.
  • The four portal designs only need content root node ids in expportal.ini to show news, shop, forums and media.
  • Editors run the store from the Editor portal's Store tab, with no developer toolbar.
  • Two demo websites install with 21 published layouts, so page building starts from working examples.
  • The media design ships Exponential Layouts block templates for product highlights and a product card item view.
  • Product content is reachable through REST and through the GraphQL schema generated from the content classes.
Back to the overview

Coming from Shopify

Rented shop, rented apps, rented data.

What you deal with on Shopify: how it limits your freedom

  • You build it yourself: Anything Shopify does not do needs an app from the App Store, usually on a monthly subscription, or a custom app you build and host yourself.
  • SaaS only: shop, customers and orders live on Shopify.
  • Monthly plans plus app subscriptions; transaction fees unless Shopify Payments is used.
  • Themes are limited to Liquid and what the platform allows.
  • Shopify's Translate & Adapt app auto-translates only 2 languages (8 in select countries); any further languages must be translated manually. source
  • The REST Admin API has been legacy since October 1, 2024; standard stores are limited to 2 requests per second. source
  • Once a store has 500,000 variants, it can create at most 10,000 new variants per day, unless it is on Shopify Plus. source
  • Paginated API results stop at 25,000 objects, including count queries. source
  • Since August 28, 2025, the additional checkout scripts are read-only; non-Plus stores had to upgrade their Thank you and Order status pages by August 26, 2026. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Self-hosted: customer and order data stay in your own database.
  • Templates can be written in .tpl, Twig 3 or Smarty 5, and a class gets its own look by adding one template file.
  • Design > Template Editor creates and orders override rules and edits template files in the administration.
  • Checkout, orders, payments and shipping run in your own installation through the 255 commerce services of expservices.
  • The database editor in Setup (sevenx_dse) exports a table or the whole database as SQL, CSV or TSV straight to a download.
  • Instead of app subscriptions, Setup > RAD wizards write your own extensions and show every file before writing it.
  • Customers can download their sign-in data as JSON, and removing an account erases its sessions and their details.
  • Optional mail goes only to people who opted in, with a checklist covering CAN-SPAM, GDPR, CCPA and CASL.
  • The Insights panel shows page views and on-site searches from the kernel's own statistics, with no third-party tracking.
  • Velocity resizes product images on request and serves AVIF or WebP to browsers that accept them.
  • Pick the database: SQLite, MySQL, PostgreSQL, Oracle or MongoDB, all installed by the same command.
Back to the overview

Our own lineage

Coming from eZ Publish 4

Where Exponential comes from, now on PHP 8.5.

What you deal with on eZ Publish 4: how it limits your freedom

  • You build it yourself: Staying on an unmaintained 4.x release means fixing PHP compatibility by hand in the kernel and in every custom extension.
  • The original vendor ended development of this line.
  • Stock installations stop at PHP versions that hosting no longer offers.
  • eZ Platform did not aim for code compatibility with eZ Publish 4; only content migrates, and 4.x sites had to follow the 5.x migration path. source
  • XmlText fields were replaced by RichText, and eZ Flow page fields by Landing Page fields from the commercial Enterprise Edition. source
  • Custom field types had to be rewritten for eZ Platform or replaced with the Null field type as a placeholder. source
  • The original vendor's own blog says automatic migration of field type code and templates is not feasible. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Exponential is this kernel, continued: sites upgrade in place to PHP 7.4 through 8.5.
  • Your path: Exponential 6 (6.0.7 to 6.0.15), PHP 7.4 to 8.5; old packages import as they are.
  • The database upgrade runs as recorded steps through exp:upgrade, dry run first; for 6.0 they are additive.
  • Build the new release beside the old tree with Composer and keep your settings, designs and extensions.
  • Switch the trees in one step: no downtime, and rollback is switching back.
  • Exponential UI replaces YUI 2.8, YUI 3.17 and jQuery 3 with jQuery 4, and $.ez() keeps existing site code working.
  • TinyMCE 8 writes the same stored XML as TinyMCE 3, so existing rich text needs no conversion.
  • exp:wt:migrate-from-ezwt moves ezwt's classes, policies and schedule to the new website sidebar after a dry run.
  • All 21 Zeta Components are forked as expcomponents, keeping the ezc* classes and APIs, tested on PHP 7.4 to 8.5.
  • With ezoracle 2.3.7, URL alias lookups work again on Oracle before 12.1.
  • admin3 keeps every module, permission and template name of the classic admin, with a sidebar that collapses and forms that stack on phones.
  • ezpm installs content packages with a lock, delayed indexing and batched commits, and can install them as drafts.
Your upgrade path in the Exponential family → Back to the overview

Coming from eZ Publish legacy

Two stacks side by side, now one.

What you deal with on eZ Publish legacy: how it limits your freedom

  • You build it yourself: A legacy-bridge site keeps two systems alive: features are built in Symfony and in the legacy kernel, or bridged between them.
  • Ran the legacy kernel beside a Symfony stack through a bridge, doubling what had to be maintained.
  • Upgrading from eZ Publish Platform 5.4 or 2014.11 had to be done in stages: first v1.7 LTS, then v1.13 LTS and 2.x. source
  • The vendor documents that the Legacy Bridge is less performant and that cache or search index may not update immediately across both systems. source
  • The original vendor's blog states that eZ Platform 3.0 no longer supports the Legacy Bridge and that the whole display layer must be rewritten. source
  • The XmlText, Page and Star Rating field types are not supported in eZ Platform; the eZ Flow script moves data only, and views, layouts and blocks must be rebuilt. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Exponential runs the kernel natively, without the bridge, and adds the modern parts (Layouts, Velocity, APIs) to it.
  • Your path: Exponential 6 for the legacy site alone, or Platform Legacy / Platform Nexus to keep both kernels.
  • Exponential 6 is the path for 5.x legacy sites that never used the Symfony stack.
  • Exponential Platform Legacy keeps the legacy kernel in every line, so legacy templates and content keep working during a move.
  • Platform Legacy 5.x (v5.0.3.8) is current for PHP 8.3 and later, and 4.6.x is maintained for PHP 7.4 to 8.5.
  • Platform Nexus 1.3.0.x (1.3.0.11) puts the media site and Exponential Layouts 2 on Platform DXP 5 with SQLite, for PHP 8.4 and later; 1.1.0.x (v1.1.0.14) keeps the legacy kernel on Platform v3.
  • Platform Legacy now runs on SQLite too, and its database moves with the platform's migrations plus the Exponential upgrade steps.
  • Twig 3 templates work inside the legacy kernel itself, next to .tpl, with overrides and every fetch function.
  • REST v1 and v2 and a GraphQL API generated from the content classes are served by the kernel without a second stack.
  • The Platform Legacy Starter (EPLSD 1.0.0.2) is a clean, SQLite-tuned install when starting fresh is easier.
  • Velocity serves the kernel from long-lived PHP workers, with HTTP/2 and automatic HTTPS.
Your upgrade path in the Exponential family → Back to the overview

Coming from eZ Platform 1 to 3

A rewrite that left legacy sites behind.

What you deal with on eZ Platform 1 to 3: how it limits your freedom

  • You build it yourself: eZ Platform dropped legacy features such as eZ Flow, the page field and star ratings, and left rebuilding them to each project.
  • A new product: legacy content and templates had to be migrated.
  • Versions 1 to 3 are past their end of life.
  • eZ Platform 3.0 moved from Symfony 3 to Symfony 5, changed template path syntax and dropped Assetic support. source
  • Version 3.0 removed the ezprice, ezpage and ezsrrating field types; 3.3.3 dropped EzMigrationBundle in favor of ibexa/migrations. source
  • Ibexa v4 moved everything under the eZ\Publish and EzSystems namespaces to Ibexa; the vendor says most of the upgrade work falls on templates. source
  • Back Office translations were contributed by the community on Crowdin and installed as a separate Composer package for each language. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Exponential keeps legacy sites running and moves them forward instead.
  • Your path: the Platform Legacy branch of your version (1.7 to 2.5, 3.x) or the Platform Nexus line of your Symfony version (1.0.0.x to 1.3.0.x), then up one line at a time.
  • Platform Legacy covers eZ Platform 1.x, 2.x and 3.x sites, with or without the legacy bridge.
  • Platform Legacy 3.x is maintained for PHP 8.0 and later, and 2.5 (master) for PHP 7.1.3 to 8.x.
  • Pick the branch of your current major version and move up one line at a time; each line keeps the legacy kernel.
  • Platform Nexus 1.3.0.x (1.3.0.11) is current, on Platform DXP 5 with Exponential Layouts 2 and SQLite; 1.2.0.x (v1.2.0.5) and 1.1.0.x (v1.1.0.14, with the legacy kernel) are maintained.
  • Nexus lines follow Symfony: 1.0.0.x on 3.4, 1.1.0.x and 1.2.0.x on 5.4, 1.3.0.x on 7.4, so the move can follow your current Symfony version.
  • The starter distributions are clean targets: clone, install and import the old site's content with packages and the import tools.
  • Packages can be kept as JSON and convert to and from XML without loss, and package/compare imports parts of a package selectively.
  • URL maps import as CSV, JSON or Apache and nginx rules, so old addresses keep answering after a move.
  • Packages from the 3.x, 4.x and 5.x lines import into Exponential 6 as they are.
Your upgrade path in the Exponential family → Back to the overview

Coming from Ibexa OSS

Open source edition, enterprise features elsewhere.

What you deal with on Ibexa OSS: how it limits your freedom

  • You build it yourself: Ibexa OSS ships the core only; Page Builder, Form Builder and other editorial features are in the commercial editions, so open source projects build them themselves.
  • The open source edition leaves many features to the commercial editions.
  • Ibexa states that Ibexa OSS comes with no commercial support or maintenance services. source
  • The code is dual-licensed: GPL v2 with no warranty, or the Ibexa Business Use License, which requires a paid Ibexa DXP subscription. source
  • Fast Track releases were maintained only until the next Fast Track release came out. source

With Exponential: your freedom back, no lock-in

  • Ready to use, not to build: the features this project needs ship finished and tested with Exponential, so you configure them and go live in hours or days, not after months of custom development.
  • Every feature of Exponential is in the free software.
  • Your path: Exponential Platform DXP 4.6 or 5 (Ibexa DXP OSS 5.0.6, freedom enabled), or Platform Legacy 4.6.x / 5.x with the legacy kernel.
  • Exponential Platform DXP is the freedom-enabled Ibexa DXP OSS, maintained by 7x, for Ibexa OSS 3.3, 4.x and 5 projects.
  • Install the skeleton of your major version and point it at your database: your Symfony bundles and Twig templates stay.
  • The admin UI, REST, GraphQL and search are included in Platform DXP.
  • Platform DXP 4.6 stays maintained, so the move to 5 can wait until you are ready.
  • Exponential Platform Legacy brings the legacy kernel back for Ibexa 3.3 and 4.x projects.
  • Exponential Layouts, the page builder with 46 block types and rule-based layouts, is part of the free software.
  • Passkeys, Verify it's you, a hash-chained audit trail and an encrypted secret store ship in the Exponential 6 kernel.
  • Exponential Intelligence, the writing assistant, is part of the free software and writes only drafts that go through the normal workflow.
  • The Platform DXP Starter (EPDSD) is a ready-to-run distribution tuned for SQLite, for evaluations or a clean import target.
Your upgrade path in the Exponential family → Back to the overview

How moving over works

  1. Model your content. Recreate your types as Exponential content classes, with the fields they really have.
  2. Import. Bring content in with the import tools and the console, in batches you can repeat and undo.
  3. Keep your URLs. Old addresses are mapped to the new pages with permanent redirects.
  4. Design. Start from a ready theme and Exponential Layouts, or port your templates.
  5. Go live without downtime. Build beside the old site, test on a copy, switch over in one step.

Next: Getting started and hosting your first Exponential website.

Every statement about another product is meant to be a documented fact. If one is out of date, tell us and we correct it. Product names and trademarks belong to their owners.