Hosting and deployment — deco developer docs

In build — This is being built now, or is available behind an org flag. What's described here may change before it ships broadly.

A storefront runtime and the Studio application are separate deployments. Blocks runs with your site's framework; Studio supplies the workspace and Site Editor used to operate it.

Fresh and the former deco.cx admin are retired. Use released Blocks 7.x for the website runtime and Studio Site Editor for current content work.

Deploy a Blocks storefront

Choose the guide for your current framework:

TanStack Start on Cloudflare Workers: Production guide and Worker configuration.
Next.js: Next.js integration.
Existing Fresh sites: retain the Fresh runtime documentation while planning your migration.

Use a deployment preview to review code changes before production. Content publication is a separate workflow; follow Releases and publishing for the current Site Editor.

Hosting controls in Studio

The hosting management surface in Studio is still rolling out behind a feature flag. An existing storefront runtime can be in production while its new management panel is unavailable. Do not assume every organization has the same hosting controls.

Keep application deployment, content publishing, and DNS configuration explicit in your operational workflow. The archived custom domain and apex domain guides describe the former admin; they are historical references, not instructions for the new Studio panel.

Run Studio yourself

Hosting Studio is independent of hosting your storefront. Use Studio self-hosting for the platform, and the framework guides above for your site's runtime.

For the transition from the former admin, consult Legacy admin migration. For hosting controls not yet documented, ask in Discord.