Security
Most website compromises start with software somebody forgot to update, or a login page somebody found. This platform has neither, because the pages a visitor sees are files rather than a program answering questions.
Platform
One system, running 7 things at once.
Each of these runs on every change and on a schedule. Every one of them produces something you can hand to somebody who asks.
Accessibility
Accessibility is a state a site holds rather than a project it completed. A site that passed an audit in March and has published forty pages since has an audit, and a current obligation it knows nothing about.
Privacy
The common privacy failure is not malice. It is a policy written once, a tag added later, and nobody connecting the two. Then somebody complains, and the document is the evidence against you.
Performance
Pages are files on a content network close to the visitor, so a campaign that multiplies your traffic changes nothing about how the site behaves. There is no server doing work per request that could fall behind.
Publishing
Clients who edit their own site fall into two groups: the ones who learned the system and resent it, and the ones who never logged in again. This replaces the system with a conversation.
Evidence
Anybody can say a website is accessible, fast and monitored. The question a lawyer, funder, insurer or enterprise customer actually asks is what you can show them, and the answer is usually nothing.
Architecture
Static output on a content delivery network, no application server or database in the request path, tenant isolation enforced below the application, and change management through a gate. Copy any of it into the questionnaire.