Multi-brand tenancy
One installation runs many brands. Every request is scoped to its brand, and a foreign record answers 404.
One API for many brands: content, review, translations, AI drafts, forms and delivery, all on the same revision history.
One installation runs many brands. Every request is scoped to its brand, and a foreign record answers 404.
Each brand keeps its own settings, theme and media storage.
Every save writes an append-only revision. Nothing is overwritten.
Publish the revision you pin, or schedule it for later.
Roll an entry back to an earlier revision when a change goes wrong.
Define content types, then compose pages from blocks.
Editors request a review, publishers approve or send it back.
Editor, publisher and admin roles decide who can change what.
Entries keep their translations together as one group.
Ask the public API for a locale and get the translated entry.
AI writes a draft, translates it, or suggests SEO fields.
AI drafts image alt text for a person to check.
Manual AI actions write drafts only. Autopost can publish, but only when an admin turns it on for a brand; it is off by default and audited.
Forms post to a public endpoint, and each submission becomes a lead.
Leads can be forwarded to a CRM from the brand integrations.
A read token returns published content only, through the public API.
Conditional requests answer 304 when content has not changed.
A preview token reads drafts, and those responses are never cached.
The sitemap-urls endpoint lists every public URL for search engines.
Every entry keeps its SEO fields in the revision, so each published version carries its own title and description.
The manage API reports SEO warnings for an entry before it is published.
Public redirects let moved URLs keep their search ranking.
A public IndexNow key lets search engines learn about changed URLs quickly.
Each webhook is signed with HMAC-SHA256 in X-Atlas-Signature.
Uploads go through signed URLs, with folders and per-brand storage.
An MCP server (stdio) lets an AI client read the content model and entries of a brand, drafts included.
Agent tools create and change drafts only. There is no tool to publish, schedule, unpublish, upload or delete.
A brand admin mints an agent token with a read scope and, optionally, draft writes. The token is shown once and is never printed by the server.