AtlasCMS is a hosted service for many brands at once, with a free plan available and paid plans for teams. An API keeps the content, revisions and roles. Any Nuxt front end reads it through a read token.
Connect one brand in a few lines. The client reads the public API with a read token.
import { createAtlasClient } from '@atlas/client'const atlas = createAtlasClient({ baseUrl: 'https://api.atlascms.id', token: process.env.ATLAS_READ_TOKEN!,})const page = await atlas.getPage({ path: '/' })One installation, many brands. Each request is scoped to its brand, and a foreign record is a 404.
// Every manage request names its brand.const headers = { 'Authorization': `Bearer ${token}`, 'X-Brand-Id': brandId,}await fetch(`${api}/v1/manage/entries`, { headers })Every save writes a revision. Publish promotes the revision you pin, and a page that moved on answers 409.
POST /v1/manage/entries/{entry}/publishX-Brand-Id: {brand}{ "revision_id": "01m4..."}Editors request a review. Publishers approve it. Only then does a change reach the live site.
GET /v1/manage/reviewsX-Brand-Id: {brand}# editors request, publishers approveEntries keep their translations as a group. Ask for a locale and get the translated entry back.
const posts = await atlas.getEntries({ type: 'post', locale: 'id', limit: 10,})A publish fires a webhook signed with HMAC-SHA256, so the receiver can verify where it came from.
// X-Atlas-Signature: sha256=<hmac>const expected = createHmac('sha256', secret) .update(`${timestamp}.${body}`) .digest('hex')AI writes a draft revision. It never publishes on its own, so a person still approves every change.
POST /v1/manage/ai/entries/{entry}/writeX-Brand-Id: {brand}# returns a draft revision, never a live pageAtlasCMS is for the people who run the brands and the people who run the sites.
Run every brand you own from one API, with each brand kept apart.
Run client sites from the same API, with a role per brand for the people who work on each one.
Who can reach a brand, what each role may change, and a record of every live change.
Requests are scoped to a brand, and a foreign record answers 404.
Each role changes only what it is allowed to.
Live changes write an audit row.
A free plan to try the platform, and a paid plan for teams that run more brands together.
Start here
For teams
A change moves through the API first. Your front end only reacts once a revision is published.
01 · AtlasCMS API
An editor saves a revision. Drafts are never served by the public read API.
02 · AtlasCMS API
Editors request a review. A publisher approves the revision that goes live.
03 · Your front end
The publish fires a signed webhook. Your server verifies the signature first.
04 · Your front end
Your front end refetches the entry with its ETag and rebuilds the page.
05 · AtlasCMS API
The pinned revision is served on the public read API.
01
Only a publish moves content to the public read API. AI writes drafts only.
02
A publish pins a revision. If the page moved on, the API answers 409 revision_changed.
03
Each webhook carries an HMAC-SHA256 signature, so your server can check it came from AtlasCMS.
Capabilities already in the AtlasCMS API and admin, not a roadmap. See everything on the features page.
Run several brands from one installation, with entries, media and settings scoped to the brand they belong to.
Every entry keeps its full revision history, and publishing or scheduling promotes the revision you choose.
Editors, publishers and admins act only at the stage their role allows, so a change is reviewed before it goes live.
Compose a page from blocks, and keep content types and translations next to the entries they describe.