---
"@type": BlogPosting
"@id": "https://ctxr.app/en/loam-cms"
"@source": "https://ctxr.app/data/blogposting/loam-cms.json"
"@stamp": "2026-10-23T12:33:44+00:00"
author: {"@id":"https://ctxr.app/#cris"}
datePublished: "2026-10-23"
description: LOAM is the engine behind CTXR. Here is how it works, in plain language, and why it fits so well with CTXR.
identifier: loam-cms
image:
  card: /assets/images/news-loam-cms-en.png
  header: /assets/images/news-loam-cms-en.png
inLanguage: en
keywords:  # 8
  - LOAM
  - CTXR
  - CMS
  - Schema.org
  - AI-assistent
  - privacy by design
  - AVG
  - website
name: Why LOAM and CTXR work so well together
shortTitle: How LOAM, the engine behind CTXR, works
url: "https://ctxr.app/en/loam-cms"
---

# Why LOAM and CTXR work so well together

[Nederlands](https://ctxr.app/data/blogposting/loam-cms.md) • [English](https://ctxr.app/en/data/blogposting/loam-cms.md)

## Keeping your website up to date should not be a hassle

Many entrepreneurs and makers know the problem. You want to change an opening time, replace a photo or publish a new article. But you are not always sure where to go, and you do not want to break anything.

At CTXR we work with LOAM. In this article we explain what it is and why it fits so well with CTXR.

## What is LOAM?

LOAM is the engine behind CTXR. It makes sure your site works, without you having to see any of it.

The big difference with many other websites: LOAM has no database and no plugins. Your content lives in ordinary, neat files. Each file describes what is on a page: this is an article, this is an address, this is an opening time.

That sounds technical, but the benefit is simple. There are fewer parts that can break or be vulnerable, and it is clearer what is on your site.

## How LOAM works

LOAM is an engine that builds pages from ordinary files. This is how it works:

- **No admin panel.** There is no admin login and no database. You work through your AI assistant or through /edit in the browser. Both update the files of your site directly.
- **One file per page.** Every page, product and team member is a small, structured file based on Schema.org. Search engines and AI answer engines read that directly.
- **Moving is copying.** A site is a folder. Copy it to a server with PHP and the site runs there. You do not need an export or a migration.
- **Updates do not touch your content.** The engine lives in its own folder. An update of the engine does not overwrite your content.
- **Draft first, then live.** You review the whole site before you publish. Every earlier version is kept.

Read more about the engine at [helloloam.dev](https://helloloam.dev/about) and [helloloam.dev/principles/no-dashboards](https://helloloam.dev/principles/no-dashboards).

## Five reasons why LOAM and CTXR work so well together

- **You see changes as a draft first.** You adjust something and review it first, the way it will look live. Only when you are happy do you publish it, once. Not sure? Then you throw the draft away and nothing has changed.
- **Your site is easy to find, also for AI.** Every page is built from structured data based on Schema.org. Search engines and AI assistants therefore understand better what you offer.
- **One site, several languages.** CTXR sites can be in Dutch, English, German and French. Visitors can also have the text read aloud.
- **Suited to places on a map.** CTXR comes from the world of locations: routes, places and lists on an interactive map. That makes it strong for municipalities, tourism organisations and local businesses.
- **You choose how you work.** Via /edit you manage your content in the browser. Prefer plain language? Then you describe your change to your own AI assistant. It makes the change and puts it on as a draft, so you can review it first.

## Fast, safe and private

Visitors get a fast site that works directly in the browser. They do not have to download anything and no app store is needed. Content keeps working offline once it has been saved.

Privacy comes first. CTXR is built with privacy by design, and with standard settings no tracking has to be switched on. Accounts and data are handled in line with the GDPR, and the hosting is in Europe.

Access runs through one controlled point, with roles for each user. Every change is also logged, so you can always see what has changed.