Skip to main content

Standalone publish

The default. Every experience you publish in Flex gets its own hosted URL, and Ceros serves it as a complete, pre-rendered HTML page.

https://{accountSlug}.ceros.site/{experienceSlug}/{pageSlug}

For example:

https://acme.ceros.site/spring-launch/
https://acme.ceros.site/spring-launch/pricing

Omit the page slug and you get the experience's first page.

There is no integration code. Publish, copy the URL, and share it.

What the browser gets​

A fully rendered HTML document, served from Ceros' CDN. The markup for the experience is already in the response — the browser doesn't have to run any JavaScript to see it. Scripts then load to hydrate the interactive components, start animations, and report analytics.

Because the HTML is pre-rendered and cached at the edge, repeat visits are served straight from the CDN.

Vanity domains​

You can map a domain you own onto your Flex host, so experiences are served from your brand instead of *.ceros.site:

https://look.acme.com/spring-launch/

This is account-level configuration — talk to your Ceros contact to set it up. It swaps the hostname only; slugs, paths, and page URLs are unchanged, and the experience keeps working exactly as before.

note

A vanity domain changes the URL your visitors see, but the experience's manifest (used by Flex Inline and Flex SSR) is always served from the canonical {accountSlug}.ceros.site host. That's deliberate — see Finding the manifest URL.

Multi-page experiences​

Each page of a multi-page experience has its own URL and its own <head> metadata, so every page is independently shareable and indexable. Links between pages are ordinary navigations: clicking through loads the next page's document.

This differs from Flex Inline and Flex SSR, where page changes are swapped in place without a reload. If you're writing scripts against the experience, that distinction matters — see the SDK's delivery modes page.

What you get​

  • Custom head and body HTML you attached to the experience in Flex is rendered for you — analytics snippets, meta tags, fonts, third-party embeds.
  • SEO and social metadata (title, description, canonical, OpenGraph, Twitter cards) come from the experience's page settings.
  • Analytics and error monitoring run inside the page.
  • oEmbed — the URL is oEmbed-discoverable, so platforms that support oEmbed can unfurl it automatically.

When to use it​

  • You don't need the experience inside a page you own.
  • You want the strongest SEO story with zero work: this is the canonical URL that every other delivery mode points back to.
  • You're sharing via short links, email, or social posts.

When to reach for something else​