How ATLAS keeps brands apart

Tenant isolation, append only revisions and ETag backed delivery: the three ideas that let one ATLAS install serve many brands safely.

Serving content for many independent brands often forces a choice between separate CMS installs per brand or a fragile custom tenancy layer. ATLAS builds the isolation into the platform instead.

Every query is scoped to a brand

Each request to the manage and delivery APIs runs inside an explicit brand scope. A brand owned record outside that scope does not exist as far as the request is concerned: a foreign id answers 404, and code that forgets to set a brand fails closed instead of reading everything.

Revisions are append only

Edits never overwrite live content. Every save is a new revision, so editors can iterate, ask for a review and preview a draft with a short lived token before a publisher puts it live. Rolling back is choosing an older revision.

Fast delivery with ETags

Public responses carry an ETag tied to the brand's content version. A site asking again for an unchanged page gets a 304 straight from cache, and publishing bumps the version and sends a signed purge webhook so the next request is fresh.

The security docs go deeper into roles, tokens and outbound calls.

//Keep reading

More from the blog

All posts →

//Run every brand from one place.

Start with one brand for free. Bring your team when you are ready.

$ npm install @atlas/client @atlas/nuxt

Free for one brandNo credit cardUpgrade anytime