Is Atlas right for you?
A quick, honest check of whether your website and team are a good fit for Atlas today.
Answer these before you plan a move. If most answers fall in the right-hand column, Atlas is probably not the right tool for you yet, and we would rather tell you now.
Your website
Section titled “Your website”| Question | Good fit | Not a fit today |
|---|---|---|
| What is the site built with? | Next.js (App Router), the framework Atlas guides and tests | A site with no server code at all, or one built entirely inside a hosted builder (Wix, Squarespace, Webflow) |
| Can it fetch content from server code? | Yes (server components, route handlers, a Node or Cloudflare Workers runtime) | Only from the browser. The delivery token must never reach browsers |
| Is the design made of reusable components? | Yes, sections such as hero, feature grid, testimonial | Every page is hand-written, one-off markup |
| Does your current CMS run code inside content (plugins, shortcodes, custom HTML or script blocks)? | No, or only a little that can become components | Heavily, and you need editors to keep adding scripts or HTML |
| Do you host and deploy the site yourself (or through an agency)? | Yes. Atlas never deploys your code | You expect the CMS to host and deploy the website |
Other frameworks (Remix, Astro, Nuxt, SvelteKit, plain Node) can call the same HTTPS Delivery API, but Atlas does not test them or provide guides for them. Plan extra developer time.
Your content and team
Section titled “Your content and team”| Question | Good fit | Plan for it |
|---|---|---|
| Who edits? | Marketing or content people who should not need a developer | If only developers edit, a Git-based workflow may be enough |
| How many languages? | One or more; right-to-left (Arabic) is supported in delivery | Check each language’s fallback rules with your developers |
| Do you need approvals? | Yes. Production releases need an approver | Decide early who approves |
| Forms, chat and analytics | Built for Development and the live website | In final review before release. CRM push and the Leads API cover Development leads only today. See capability status |
| Contracts, data residency, SSO | — | Some enterprise terms are still open decisions. Ask us before you sign; see FAQ |
Typical effort
Section titled “Typical effort”These are planning ranges, not promises. They depend most on how component-based your site already is.
- Connect one page in Development: a developer, about a day.
- Model the whole site in the contract and render every page type from Atlas: days to a few weeks.
- Move existing content and images: depends on volume. An AI coding agent connected over MCP can draft most of it for a person to check and publish.
Next: the migration checklist.