> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gradial.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Hosting and Delivery

> How ACI stages immutable releases for CloudFront, Vercel, and local development.

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

| Target | Best fit | Release output |
| - | - | - |
| **AWS CloudFront** | Static sites delivered through AWS | Complete HTML and assets, with request-time selection among compiled variants when personalization is enabled |
| **Vercel** | Next.js applications that need supported SSR delivery | Static HTML or a compiled page graph selected before the application renders it |
| **Local** | Development and release smoke tests | The same release model on a local filesystem and server |

<Info>
  Access: Must be enabled for your organization. Contact your Gradial team to get access.
</Info>

## 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.

```mermaid theme={null}
flowchart LR
    A["Approved live content"] --> B["Compile release"]
    B --> C["Hosting adapter"]
    C --> D["Staged preview"]
    D --> E["Activate"]
    E --> F["Customer traffic"]
```

## Static and SSR delivery

<Tabs>
  <Tab title="Static">
    ACI produces complete HTML for each route and eligible variant. The hosting adapter deploys those artifacts and the routing metadata required to select them.
  </Tab>

  <Tab title="Next.js SSR">
    For supported Next.js configurations, ACI produces a normalized page graph for each eligible variant. The delivery layer selects the exact graph first, then the application renders it. Your page code does not implement audience resolution or content fallback.
  </Tab>
</Tabs>

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](/aci/architecture/publishing-and-releases) for the complete workflow.

***

*Next: [Data Ownership and Portability →](/aci/platform/customer-owned-data)*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.