Recent changes
Wednesday November 04 2026
-
Composer packages and source on GitHub Updated Markdown page
How Exponential's code reaches a public body (GitHub repositories and Composer packages on Packagist), why published versions never change, how to keep your own copy of every source you depend on, and how to check what…
-
Contributing back as a public body Updated Markdown page
Why and how a public body gives code, translations, documentation and bug reports back to the Exponential project: what is worth sharing, the steps for publishing an extension, contributing fixes to the kernel, and the…
-
Data location Updated Markdown page
Where an Exponential installation keeps data (database, storage files, caches, logs, audit records, backups, mail, search index) so a public body can state its data location, and which optional features send data…
-
Database choice Updated Markdown page
The six databases Exponential supports, in the project's official order (SQLite 3, PostgreSQL, MongoDB, MariaDB, Oracle, MySQL), and what matters to a public body when choosing one: licensing, existing skills…
-
Digital sovereignty at a glance Updated Markdown page
What digital sovereignty means for a public body choosing a content management system, and how Exponential measures up on each point (license, source, hosting, data location, external services, formats, databases…
-
The documentation license (GFDL) Updated Markdown page
The Exponential documentation, this help included, is free documentation under the GNU FDL 1.3 or later. What that lets a public body do with it (copy into internal manuals, translate into official languages, adapt for…
-
Exit planning Updated Markdown page
How to plan, document and test an exit: moving an Exponential site to another provider or host, or migrating away from Exponential, with what to collect, who to involve, and a test that proves the plan works.
-
Exporting content and packages Updated Markdown page
The ways to take content out of an Exponential installation, from a full backup to class and content packages and per-class exports, with what each carries and which one to use for an exit, a copy for another body, or…
-
Government cloud and hosting models Updated Markdown page
Which hosting models Exponential is documented for (shared, VPS, dedicated, containers, Kubernetes, platform as a service, managed) with the project's own support tiers, and the questions a public body asks before…
-
Keeping the skills in house Updated Markdown page
Which Exponential skills a public body should hold itself so it can direct and change providers, how to build them with the free documentation and training material, and how to keep them when people move on.
-
No required external services Updated Markdown page
Exponential serves pages and runs its administration without any outside service: no license server and no third-party scripts or fonts in the admin. This page lists what does reach the internet, and only when you use…
-
Open formats and data portability Updated Markdown page
In which formats Exponential stores and exports content, settings and files, which of them are open and documented, and how to keep your own content in formats another system can read.
-
The open source license (GPL) Updated Markdown page
Under which license Exponential comes (GNU GPL version 2 or any later version), what the license lets a public body do, what it asks when copies are passed on, and where to check it in the product and the repository.
-
Open source procurement Updated Markdown page
How a public body buys services around free software like Exponential when there is no license to buy: what to procure (hosting, building, support, training), requirements that keep you independent, how to evaluate…
-
Security updates and independence Updated Markdown page
How a public body keeps an Exponential installation secure without depending on one vendor: where security fixes come from, how to learn about releases, how to apply updates with the upgrade check and ezupdate, and what…
-
Self-hosting on premise Updated Markdown page
What a public body needs to run Exponential on its own servers: the requirements, the install paths, serving with Velocity or a traditional web server, the database, the regular operations, and the skills to plan for.
-
Sovereignty checklist Updated Markdown page
One checklist for a public body that wants to stay in control of its Exponential platform: license and code, hosting and data location, external services, formats and exports, skills and providers, updates and exit…
-
The Exponential Foundation and 7x Updated Markdown page
Who stands behind Exponential, in the words of the sources: the Exponential Foundation (a nonprofit that operates the project) and 7x (the company that leads development), what each publishes about itself, and what the…
-
Third-party services to review Updated Markdown page
A review routine for every optional service that sends data outside the organization (analytics, CAPTCHA, maps, social sign-in, AI providers, embeds, CDNs), with what Exponential ships for each and the decisions a…
-
What the GPL means for a public body Updated Markdown page
The practical questions a public body settles about the GPL: running a website, agencies that build for you, sharing code with other public bodies, publishing your own extensions, combining with proprietary code, and…