Skip to content
Delivery API
Before you plan around a feature, check the capability status.

OverviewStart here

What is Atlas

What Atlas CMS is, what "headless" means, what Atlas does for your team and what stays in your hands.

Atlas CMS is a content management system for companies that already have a website. Your team uses Atlas to change the words, images, pages and translations of that website. Your developers keep the website’s code, design, hosting and deployments exactly where they are today.

A CMS (content management system) is the place where non-developers edit a website: they change a headline, add a news article or replace a photo without touching code.

Traditional CMS products such as WordPress do two jobs at once. They store the content and they render the website, using themes and plugins that run inside the CMS.

Atlas is a headless CMS. It does only the first job. It stores the content, keeps its history and publishes it. Your own website, built by your developers, reads the published content and decides how it looks. The “head” (the visible website) is yours; Atlas is the content layer behind it.

Traditional CMS Atlas (headless)
The CMS renders and often hosts the website Your website renders itself and stays where it is hosted
Design comes from a theme inside the CMS Design comes from your own components
Plugins and custom code run inside the CMS No code runs from the CMS; features live in your website’s code
Editors can paste HTML and scripts Editors fill typed fields your developers defined
One installation per website One organization manages many websites, each isolated
  1. Your developers describe the website’s building blocks (hero, feature grid, product card, FAQ) in a site contract.
  2. Editors create and change drafts in Atlas Studio, using only those building blocks.
  3. They preview drafts inside the real website design, then publish.
  4. Your website reads the published content from the Delivery API over HTTPS, from its server, with a read-only token.
  5. Atlas sends a signed webhook, and your website refreshes only the pages that changed.

If Atlas is ever unreachable, your website serves its built-in content, so it stays up.

  • Atlas Studio, where your team edits pages, collections (news, products, team members), the header and footer, media and translations.
  • A site contract that lists your components and their typed fields, so editors cannot break the design or inject code.
  • A Delivery API your website calls from its server to read published pages, entries, globals, redirects and SEO data.
  • Development and Production environments, so content is prepared and checked before it reaches the live site.
  • Roles and approvals: editors draft, reviewers publish, and Production releases need a person’s approval.
  • Revisions and rollback: every publish is kept, so a mistake can be undone.
  • Forms, a website chatbot and page-view counts on your Development and live website, with a leads inbox, CSV export, a Leads API and CRM push.
  • Design tools: fonts with licence evidence, an animation studio, a website-planning helper with logo palettes, and design quality scans.
  • Search and performance: ready meta tags and structured data, sitemap.xml, robots.txt and llms.txt, and Core Web Vitals.
  • An MCP endpoint so an AI coding agent can draft content and propose changes, but never publish.
  • Your code and design. Atlas never ships components, styles or scripts to your website.
  • Your hosting and deployments. Atlas has no access to your repository, servers or deploy pipeline.
  • Logic and integrations. Checkout, member logins, search, analytics and tracking stay in your website’s code and services.
  • Your decision to go live. Production is off until a site admin switches it on after an approved release.
  • Not a website builder or host. Atlas does not build, host or deploy websites.
  • Not a plugin platform. There are no plugins, custom scripts or HTML blocks. This is deliberate: it keeps the content layer safe.
  • Not a drop-in replacement for WordPress themes. You render Atlas content with your own components. See Is Atlas right for you?.
Person What they do
Content editor Updates the home page hero, adds three news articles, translates a page into Arabic, previews each draft and submits it
Reviewer Checks the drafts in the real design and publishes them in Development
Site admin Approves the week’s Production release after Atlas confirms its checks pass
Developer Adds one new component to the contract and deploys the website once; no content work
  • Companies with a Next.js website that want editors to change content without a developer for every edit.
  • Groups running several brand websites that want one place to manage them, with each site isolated from the others.
  • Agencies that build websites for clients and want to hand over editing safely.