Hosting and Delivery

ACI separates content authoring and release management from the infrastructure that serves your site. A hosting adapter stages each immutable release, exposes a preview, and activates the reviewed release on your delivery platform.

​

Supported delivery targets

​

One release contract

The delivery target changes the final output format, not the workflow:

1. ACI compiles the approved content and linked code version.
2. The adapter stages a complete, immutable release.
3. Your team reviews the release at its preview URL.
4. Activation makes that release current.
5. Rollback selects a previously staged release.

​

Static and SSR delivery

Both modes use the same component contracts, content validation, preview, activation, and rollback lifecycle.

​

Personalization boundary

Personalization and first-party collection require a Gradial edge binding for the selected hosting target. The binding serves the ACI browser collector, applies the active release’s decision rules, and selects a compiled artifact before the response is returned. Do not add audience-selection logic to application components. That would create a second decision path that can disagree with preview and release validation.

​

Operational responsibilities

Your deployment configuration determines the cloud account, domain, certificates, and provider-level controls used by the adapter. Gradial manages the ACI release workflow and the integration required to stage and activate artifacts. During onboarding, confirm:

• the target and delivery mode;
• the production and preview domains;
• the code build connected to the site;
• the permissions required by the adapter; and
• whether personalization and collection are enabled.

See Publishing and Releases for the complete workflow.

---

Next: Data Ownership and Portability →