---
title: Deployment Overview
description: "Hosting options for your documentation \u2014 Jamdesk subdomain, custom domain with SSL, or /docs subpath behind your existing site using a reverse proxy."
---

> **For AI agents:** the complete documentation index is at [llms.txt](/docs/llms.txt). Append `.md` to any page URL for its markdown version.

Jamdesk deploys your docs automatically to a `*.jamdesk.app` subdomain. When you are ready to go live on your own domain, you can choose a custom subdomain (like `docs.example.com`) or host at a `/docs` subpath on your main site.

## Deployment Options

| Option | Best For | Setup Complexity |
|--------|----------|------------------|
| **Jamdesk subdomain** (`your-project.jamdesk.app`) | Fastest launch, zero DNS work | Low |
| **Custom subdomain** (`docs.example.com`) | Production docs with your brand | Medium |
| **Subpath hosting** (`example.com/docs`) | Keep docs on the main domain | High |

## Default Hosting (No Setup)

Every project ships live on a Jamdesk subdomain as soon as you connect a repo. This is the simplest option for internal docs, previews, or early launches.

## Custom Domain (Subdomain)

Use your own subdomain (for example, `docs.example.com`) for a branded, public-facing URL. You will add DNS records and verify ownership in the Jamdesk dashboard.

<Note>
DNS verification and SSL are handled automatically once the records are in place. See [Custom Domains](/deploy/custom-domains) for setup.
</Note>

## Subpath Hosting (/docs)

Host docs at `example.com/docs` by proxying traffic to Jamdesk. This is ideal when you want docs to live under your main marketing domain.

<Info>
Subpath hosting requires a proxy or CDN layer to forward requests and set the `X-Jamdesk-Forwarded-Host` header. See [Subpath Hosting](/deploy/subpath-hosting).
</Info>

### Example Proxy Snippet (nginx)

```nginx nginx.conf
location /docs {
    proxy_pass https://YOUR_SLUG.jamdesk.app;
    proxy_set_header X-Jamdesk-Forwarded-Host $host;
}
```

For a full configuration with SSL, headers, and provider-specific guidance, see the [Subpath Hosting](/deploy/subpath-hosting) guide.

## Provider Guides

Choose your infrastructure to implement subpath hosting:

<Columns cols={2}>
  <Card title="Cloudflare" icon="cloud" href="/deploy/cloudflare">
    Use Cloudflare Workers to proxy /docs traffic
  </Card>
  <Card title="AWS" icon="aws" href="/deploy/aws">
    Configure CloudFront with Route 53
  </Card>
  <Card title="Vercel" icon="triangle" href="/deploy/vercel">
    Add rewrites or edge middleware
  </Card>
  <Card title="Reverse Proxy" icon="server" href="/deploy/reverse-proxy">
    nginx, Apache, or other proxy servers
  </Card>
</Columns>

## What's Next?

<Columns cols={2}>
  <Card title="Build & Deploy Lifecycle" icon="rotate" href="/deploy/lifecycle">
    How builds are triggered and deployed
  </Card>
  <Card title="Subpath Hosting" icon="folder-tree" href="/deploy/subpath-hosting">
    Host docs at /docs on your main domain
  </Card>
  <Card title="Custom Domains" icon="globe" href="/deploy/custom-domains">
    Set up docs.yourdomain.com
  </Card>
  <Card title="DNS Troubleshooting" icon="server" href="/help/troubleshooting/dns-issues">
    Fix DNS propagation and verification issues
  </Card>
</Columns>
