Edit your website's content. Keep your code.

Atlas CMS documentation

Edit your website's content. Keep your code.

Everything you need to understand Atlas CMS, decide whether it fits your website, connect it and move your content safely.

Search the docsCtrl K

QuickstartIs Atlas right for you?What's new

Next.js

// app/[[...slug]]/page.tsx: runs on your server
const page = await atlas(`/pages?route=${route}`);

if (!page) return builtInPage(route); // fallback
return page.document.regions.main
  .filter((section) => !section.hidden)
  .map(renderSection);

cURL

curl https://delivery.atlas.example/v1/delivery/environments/$ENV/pages?route=/about \
  -H "Authorization: PublishedConsumer $ATLAS_DELIVERY_TOKEN"

Webhook

app/api/atlas/webhook/route.ts

const ok = verifySignature(rawBody, request.headers);
if (!ok) return new Response(null, { status: 401 });

revalidatePath(payload.route); // refresh only what changed

What Atlas CMS means

A content system for websites you already own

A CMS (content management system) is where your team changes the words, images, pages and translations of a website without asking a developer. Atlas is a headless CMS: it stores and publishes the content, and your own website decides how that content looks.

Your website keeps its code, design, hosting and deployments. It reads published content from Atlas over HTTPS with a read-only token, and falls back to its built-in content if Atlas is unreachable.

Read the full explanation

• Atlas holds

  Pages, collections, header and footer, media, translations, SEO fields, drafts, revisions and approvals.

• Your website keeps

  Its code, components, design, hosting, deploy pipeline and anything that runs logic, such as checkout or logins.

• Atlas never does

  Run code on your site, change your design, deploy anything or publish to Production without a person's approval.

Choose your path

Start from your role

Content owners, decision makers and developers need different answers. Each path links to the pages that matter for you.

Business and content teams

Understand what Atlas changes for editors, what stays the same, and whether your current website can move.

• What is Atlas
• Quickstart
• Work with leads

Developers

Connect your Next.js website, model your components in a site contract and keep pages fast with webhooks.

• Connect a Next.js website
• Search and AI answers
• Leads API

Your journey

From evaluation to go-live

Follow the steps in order, or jump to what you need.

1. 1Evaluate

   Is Atlas right for you?Capability statusSecurityWhat's new

2. 2Set up and connect

   QuickstartConnect a Next.js websiteSite contractWebsite helper and palettes

3. 3Build and migrate

   Migration checklistPreview, publish and roll backFontsAI agents (MCP)

4. 4Go live and grow

   Go liveForms and leadsSearch and AI answersPerformance

Reference architectures

How teams set it up

Recommended set-ups, not customer stories.

Multi-brand groupOne site per brandCentral approvalRegulated companySign-offAudit logAgencyOne org per clientReusable componentsSingle websiteSmall teamLow effort

Honest about what is ready

Every capability is marked Available, Beta, Preview, Planned or Not supported on one page.

See capability status