One site, one install

A CTXR site is one folder on one host with one domain. Two sites are two installs. There is no shared root, no tenant layer, no platform that several sites sit inside.

The choice

Multi-site platforms suit whoever runs them: one engine, one update, many customers. The customer pays with shared fate — a breach, an outage or a bad update touches everyone — and a permanent dependency on the platform.

An earlier engine we built was such a platform: sites as subdomains under one root, with accounts spanning them. Every hard problem it had — isolation, permissions crossing tenants, configuration drifting per space — came from the sharing. CTXR removed the sharing. Each site is hermetic: its own files, keys, history and plan. The engine is copied into each install rather than served from a centre.

What it buys

Isolation by construction. Nothing in one site can reach another, because there is no path between them. Not by policy — by the absence of a connection.

Ownership that means something. A folder with a domain is a complete site: it can be moved, handed to another party, or kept running long after any relationship with Braaf has ended. See Your content is yours.

Simplicity everywhere. Keys, drafts, plans, the journal, the machine views — none has to ask “which site?”. That is a large part of why the engine is small enough to audit.

Accountability that lines up with the law. One organisation, one site, one controller, one clear answer to where its data is. See Privacy and GDPR.

What it costs

Content that belongs on two sites is published on one and read by the other through its machine views — an auditable read, not a shared record. A person who works on several sites holds a key per site. And the engine is updated per install; CTXR works on making the update a non-event instead.

What “several sites” means then

Several installs that happen to share an engine — the way several houses share an architect. The architect can improve the plans; each house is still its own house.