---
title: Publish with Thally managed hosting
description: Publish documentation, review pull-request previews, restore a previous version, and connect a custom domain.
url: https://pr-7-a9c4e9fe1b6c.thally.app/guides/managed-hosting
---

# Publish with Thally managed hosting

Publish documentation, review pull-request previews, restore a previous version, and connect a custom domain.

Managed hosting publishes reviewed Git changes without requiring you to run the
hosting infrastructure. Thally validates a change before it becomes live, so a
failed publish leaves the current site online.

## What triggers a publish

- A push to the configured production branch creates a production candidate.
- Opening or updating a documentation pull request creates or refreshes an
  isolated preview.
- Merging a Track documentation pull request follows the same production path.
- Changing a supported setting or applying a Thally update publishes the
  result.
- **Redeploy site** republishes the current version without changing it.

The **Deployments** page shows the live production release, the latest preview,
open preview count, commit details, status, and searchable history.

## How a production change becomes live

#### Thally selects the Git revision

    The Deployments page shows the commit being published, so you can confirm
    that it matches the change you approved.

#### Thally builds and validates the site

    Content, navigation, links, and the production site are checked before the
    change can publish.

#### The checked version becomes live

    If every check passes, Thally publishes the new version. If a check fails,
    the existing live version stays in place and the deployment shows the
    failure.

## Faster content updates

Changes limited to pages, navigation, or snippets can publish faster than a
full application change. Thally still validates the result before it becomes
live. When a change needs a full build, Thally chooses that path automatically.

## Pull-request previews

Each open documentation pull request receives a preview address for its latest
commit. Preview changes stay separate from production and cannot make
themselves live. Closing or merging the pull request retires its preview.

## Roll back safely

Owners and editors can select a previous successful version from deployment
history. A rollback restores that version without rewriting Git history.

After a rollback, Thally pauses automatic production publishing so a later
change cannot immediately overwrite your choice. Use an explicit publish to
resume automatic updates after you resolve the problem.

## Add a custom domain

Open **Settings → Domains**, add the hostname, and copy the DNS records Thally
shows into your DNS provider. Thally provisions the certificate and connects
the hostname to your site.

Keep the managed address available while the custom domain is pending. Wait
until the Domains page reports the custom hostname as verified, then open it
in a private browser session.

## Update Thally

When a compatible update is available, **Settings → Updates** shows **Update
site**. Review and apply the change from there. Thally leaves your pages,
navigation, branding, and other authored files unchanged. If a framework file
also has local edits, Thally identifies it for local review instead of
overwriting it.

For a self-hosted project, preview the same update locally:

```bash
npx thally starter update
npx thally starter update --apply
```

The first command previews the change. The second applies it.

## Verify a publish

1. Confirm the deployment is **Healthy** or the preview is **Ready**.
2. Check that the displayed commit matches the revision you expected.
3. Open the live or preview address and test a representative page.
4. Check `/llms.txt`, `/api/docs-index`, and `/AGENTS.md`.
5. If the release failed, open its details before redeploying or changing
   source files.