A website, and a folder behind it
To a visitor, a loam site is a website like any other: pages, images, a contact form, fast to load, found by search engines. Behind it there is no admin panel, no database and no build step. There is a folder.
Your content is small structured files, one per thing on your site — a page, a team member, a product — each in Schema.org, the vocabulary search engines and AI assistants already understand. When someone opens a page, loam renders it from those files right then. Publish a change and the site has changed.
The engine sits in a folder of its own, the same for every loam site. It knows nothing about your site, and your site nothing about its insides. That is why an update never touches your content, and why your content is yours to take with you.
You change it by asking
You say what you want in your own words. Your agent finds the right file, makes the change and stages it as a draft. You get a preview of the whole site as it would look, and you decide: publish or drop. Before anything goes live the site checks itself, and every change leaves a line in its journal — who did it, what was touched, and what you asked.
What comes for free
| Readable for machines | A sitemap, a feed, a map for AI assistants and a searchable index of everything — from the same files as the pages, always in step. |
|---|---|
| An app | Installable on a phone or laptop, and working offline, with nothing to build. |
| A complete history | Every change recorded and every earlier version kept, mirrored every fifteen minutes. |
| Quiet | No tracking, no accounts, no cookies for visitors. |
Three ways to be involved
- Visitor. Reads the site, installs it as an app, sends a form — without an account or a trace that identifies them.
- Editor. Changes content through an agent, with a key and the rights it carries. A copywriter stages drafts; someone else publishes them.
- Owner. Decides who gets keys, what the site is called and which languages it speaks. It needs no technical skill: the same agent as any editor, only the key differs.
Every language, honestly
Each page carries its address per language — /diensten in Dutch, /services in English — and the language links, the sitemaps and the switch follow by themselves. A missing translation is simply missing: no page, no menu entry, no sitemap line. A visitor sees either a translation or honestly the default, and you see at a glance what you forgot.
The shop window, not the till
A loam site can be the face of a shop: product pages, collections, the whole catalogue as structured data search engines and assistants can read. The cart, the checkout, payments and orders stay with the platform built for them — the site hands the transaction over. Visual and data, yes. Transactional, no.
Coming from Shopify, WordPress or a static-site generator? The concepts carry over: a template is a shell, a product is an entity, a menu is a list you keep. Only the file types change.