---
title: Hosting and deploys | Stainless
---

You can host your documentation site on Stainless, or with any hosting provider that supports static sites.

## Choosing a provider

We recommend you host your site on Stainless, which offers a few advantages:

- Automatic builds and deploys when your APIs or SDKs change
- AI search indexing powered by [Algolia](https://www.algolia.com)
- Optimized performance for SEO and GEO
- Pre-configured asset caching behind a global CDN
- A generous free tier, including free custom domains with automatic SSL

## Host with Stainless

When you set up your site through the Stainless dashboard, your site is automatically deployed on Stainless infrastructure. When you’re ready to go to production, add a custom domain.

### Preview builds

When you push a branch to your docs repository and create a pull request, Stainless automatically builds a preview of your site. This allows you and your team to review documentation changes before merging.

#### View the build status

After you push changes, a **Stainless Docs Build** check appears in your pull request. Click **Details** to open the deployment details in the Stainless dashboard.

![GitHub pull request checks showing the Stainless Docs Build check marked as complete alongside other CI checks.](/docs/_astro/github-pr-checks.D_N9w8Hv_lwi1y.webp)

#### Access the preview URL

The deployment details page displays the build status, source branch, commit SHA, and a preview URL. The preview URL is a unique link to your documentation site built from the pull request branch.

![The Stainless dashboard deployment details page showing a complete build with status, environment set to Preview, source branch, and preview URL.](/docs/_astro/deployment-details-collapsed.CB1-lMA4_2nbtor.webp)

Share this preview URL with reviewers so they can see your proposed documentation changes in context.

#### View build logs

To troubleshoot build issues or verify the build process, expand any build step to view its logs. The build steps include cloning the repository, installing dependencies, building the site, and uploading the result.

![The Stainless dashboard deployment details page with the Build site step expanded, showing detailed build logs including page generation output.](/docs/_astro/deployment-details-expanded.CCW-_e9R_ZtpAWO.webp)

## Host elsewhere

If Stainless hosting doesn’t meet your needs, or if you prefer to host your site yourself, your site can be hosted anywhere that supports static sites.

First, generate a static build of your site:

Terminal window

```
pnpm build
```

When you run this build command, your static site will be generated in the `dist` directory. If you have a deployment pipeline, you should add this build command to it so your site is regenerated every time you deploy.

You can preview the resulting static site locally by running the following command:

Terminal window

```
pnpm preview
```

The static site inside your `dist` directory can be hosted anywhere that supports static site hosting, such as [GitHub Pages](https://docs.github.com/en/pages), [Vercel](https://vercel.com), [Cloudflare Pages](https://pages.cloudflare.com), [Netlify](https://www.netlify.com), and many other web hosts.

### Site search

By default, your static site will use [Pagefind](https://pagefind.app/) for basic site search.

If you have an Algolia account, you can enable advanced search functionality by passing the following environment variables into the `build` command:

| Environment variable        | Description                                      |
| --------------------------- | ------------------------------------------------ |
| `PUBLIC_ALGOLIA_APP_ID`     | Your Algolia app ID                              |
| `PUBLIC_ALGOLIA_INDEX`      | The name of the index to use for search indexing |
| `PUBLIC_ALGOLIA_SEARCH_KEY` | Your Algolia search API key                      |
| `PRIVATE_ALGOLIA_WRITE_KEY` | Your Algolia API key                             |

### Configuring cache headers

When you host with Stainless, we automatically set the correct cache headers for each file. When you host your site elsewhere, you need to set these yourself to ensure that your site is performant.

Assets in the `_astro` directory are versioned, and therefore can be cached indefinitely. We recommend the following cache headers for these assets:

```
Cache-Control: public, max-age=604800, immutable
```

Other files in the `dist` directory, including HTML files, should be cached for a shorter period of time, depending on how often you expect them to change.