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

Trust

FAQ

Answers to the questions companies ask most before moving their website to Atlas.

Our website has a lot of customization in its current CMS. Can it move?

Section titled “Our website has a lot of customization in its current CMS. Can it move?”

Usually, yes, if the customization is in content structure (custom fields, post types, page-builder blocks, menus, translations). Those map to Atlas components, collections and globals. Customization that runs code inside the CMS (plugins, shortcodes, HTML or script blocks, checkout or member areas) does not move into Atlas; it moves into your website’s code. Work through the migration checklist and the feature mapping.

No. You keep your design and components. Your developers change where each page gets its content from, one page type at a time, with the old content as a fallback.

No. Atlas holds the content. Your website stays where it is hosted today.

Your website keeps serving. It caches Atlas responses and falls back to its built-in content if Atlas cannot be reached. Building that fallback is part of the connection guide.

We do not use Next.js. Can we still use Atlas?

Section titled “We do not use Next.js. Can we still use Atlas?”

The Delivery API is plain HTTPS and JSON, so any framework that renders on a server can call it. Atlas only guides and tests Next.js today. See Is Atlas right for you?.

They can only fill the fields your developers defined, within the rules of each page type. They cannot paste HTML or scripts, add fields or change layout rules. Nothing reaches Production without an approved release.

No. AI agents can draft content and propose changes in Development. Only people with the right role can publish or approve releases.

Are forms and the chatbot ready for our live website?

Section titled “Are forms and the chatbot ready for our live website?”

Yes, they are built for the live website and in final review before release. They answer once Production is on and a signed release is live. See Forms and leads and capability status.

The hosting location has not been decided yet. If you have residency requirements (for example UAE-only or EU-only), tell us before you sign.

Can we use our own single sign-on (Azure AD, Okta, Google Workspace)?

Section titled “Can we use our own single sign-on (Azure AD, Okta, Google Workspace)?”

Not today. People sign in through Atlas’s single sign-on service, by invitation.

Not yet. We will offer an uptime commitment once the hosted service has been measured.

Pricing is not published yet. Plans differ in the number of sites, people, storage, languages and AI credits. Contact us for a quote.

Connecting one page takes about a day. A full site takes days to a few weeks, depending mostly on how component-based it already is and how much content there is. See Is Atlas right for you?.

Email security@orbisai.ae. See Security.