Basics
Files, not a database
Data, theme, assets and guide are plain folders. Git keeps the history; a diff is the review.
Portable by design
A site is one folder: copy it, clone it or move it to another host. The engine sits beside it as a container.
Schema as data
Content is Schema.org JSON, one entity per file. The schema is the list of what a thing can carry.
Security bolted in
A content-security policy with a nonce per request, every file judged at the door, and nothing executable in a public folder.
Mechanics
Backups as a snapshot
Every fifteen minutes the site commits itself to its own git mirror. Restoring is a checkout.
Draft and live lifecycle
Every change is staged as a draft, previewed and published only when approved. Unpublishing is reversible.
Fine-grained permissions
Every key carries its own rights per folder: read, write and delete for data, theme, assets and guide.
Speed by caching
Pages render per request and stay cached until the files beneath them change. No build step.
Gives any site
AI compatibility at its core
llms.txt, /data.json and /data.md derive from the live data, so an agent reads the site as easily as a person.
MCP with a trust model
Bring any agent through the MCP: a key per actor, rights per key, and a journal of every change.
PWA app by default
A manifest, a service worker and an offline page, generated from the site's own data.
SEO friendly from the start
Canonicals, hreflang, the sitemap and JSON-LD come from the same entities that render the page.
Gives you
Creative freedom
Templates are plain PHP and CSS. No page builder decides what your site can look like.
No dashboards to learn
Tell your own agent what you want, in plain language. There is no admin panel in between.
No update stress
Releases are signed and tested. An update swaps whole parts of the engine and never touches your content.
Trust and privacy
Nothing about your visitors, little about anyone else, and everything yours to take with you.