What must a valid host do?

A valid host must serve the exported files as normal static assets, preserve the folder structure after upload, and allow the browser to fetch manifest.json, step data, and assets normally.

Can the bundle be hosted on a different origin from the page that embeds it?

Yes. The bundle can be hosted on a different origin as long as the host still allows the browser to fetch the exported files normally.

Host Exported Demo Bundles

Serve exported bundles as normal static files, preserve the folder structure, and avoid rewrites that interfere with asset requests.

Use this page once the bundle has been exported and you are ready to host it reliably.

What a valid host must do

Any static host is fine as long as it:

serves the exported files as normal static assets
preserves the folder structure after upload
allows the browser to fetch manifest.json, step data, and assets normally

What not to do

Do not:

flatten the export
rename bundle files arbitrarily
route bundle asset requests to your app shell
point baseUrl at a page URL instead of the bundle root

If the host returns HTML for asset requests, the player will not be able to load the demo correctly.

Cross-origin hosting

The bundle can be hosted on a different origin from the page that embeds it.

If you do that, the host must still allow the browser to fetch the exported files normally.

Deployment checklist

Before debugging the player, confirm all of the following:

manifest.json is reachable at your chosen baseUrl
the steps/ directory is being served unchanged
the assets/ directory is being served unchanged
the host is not rewriting bundle requests to HTML

If localized content is present, also confirm the i18n/ directory is being served correctly.

When something partially loads

If the player renders but the demo does not start, check manifest.json first.

If the page renders but steps or visuals are missing, verify that the exported steps/ and assets/ files are being served unchanged.